Yes Tom you are correct. Thank you!! I am comparing two log files, fairly large ~2000 lines, but I only show little here.
What could be different but never should be is the backing device. I should always have 2 twcsapxrqdb1_x1 in each log file but sometimes the OS puts them where it wants to. The problem with my previous code was when I added a new LUN to the VIOS, it would assign where the last vtscsi ID gap existed. Here is a visual of what it currently does using grep -p. Error warning from Test::More. got archive_d1f but expected archive_r1a.
# Failed test 'vios16a-vios16b-map-compare'
# at stgpool_lun_compare.plx line 204.
# Structures begin differing at:
# $got->{0x0000000a}[1] = 'archive_d1f.12dd194548df82b3aa92de
+094112214c'
# $expected->{0x0000000a}[1] = 'archive_r1a.91f0e02e3948dc9f783597
+0a2d79ddaa'
*** LOG 1 ***
# grep -p archive /opt/r2configs/vios16a/2015/11/19/lsmap-all.out
VTD vtscsi12
Status Available
LUN 0x8800000000000000
Backing device archive_d1f.12dd194548df82b3aa92de094112214c
Physloc
Mirrored N/A
VTD vtscsi73
Status Available
LUN 0x8100000000000000
Backing device archive_r1a.91f0e02e3948dc9f7835970a2d79ddaa
Physloc
Mirrored N/A
VTD vtscsi74
Status Available
LUN 0x8200000000000000
Backing device archive_r1b.e812830370e17478eb79d3b7b10b7e9d
Physloc
Mirrored N/A
VTD vtscsi75
Status Available
LUN 0x8300000000000000
Backing device archive_d1a.2e1bd9b5a21aee5120c7b4205e967567
Physloc
Mirrored N/A
VTD vtscsi76
Status Available
LUN 0x8400000000000000
Backing device archive_d1b.e24dedc7fd9a4fddfd2464cce6b20a18
Physloc
Mirrored N/A
VTD vtscsi77
Status Available
LUN 0x8500000000000000
Backing device archive_d1c.cb45fea8aed10491e0df5e9578c9a726
Physloc
Mirrored N/A
VTD vtscsi78
Status Available
LUN 0x8600000000000000
Backing device archive_d1d.b4277aa6b6c4b737084913f78104a90c
Physloc
Mirrored N/A
VTD vtscsi79
Status Available
LUN 0x8700000000000000
Backing device archive_d1e.2a7a12d38d59d5ae415d64d5869b1144
Physloc
Mirrored N/A
*** LOG 2 ***
root@r2nim01(/usr/local/scripts)$
# grep -p archive /opt/r2configs/vios16b/2015/11/19/lsmap-all.out
VTD vtscsi62
Status Available
LUN 0x8100000000000000
Backing device archive_r1a.91f0e02e3948dc9f7835970a2d79ddaa
Physloc
Mirrored N/A
VTD vtscsi66
Status Available
LUN 0x8800000000000000
Backing device archive_d1f.12dd194548df82b3aa92de094112214c
Physloc
Mirrored N/A
VTD vtscsi69
Status Available
LUN 0x8200000000000000
Backing device archive_r1b.e812830370e17478eb79d3b7b10b7e9d
Physloc
Mirrored N/A
VTD vtscsi70
Status Available
LUN 0x8300000000000000
Backing device archive_d1a.2e1bd9b5a21aee5120c7b4205e967567
Physloc
Mirrored N/A
VTD vtscsi71
Status Available
LUN 0x8400000000000000
Backing device archive_d1b.e24dedc7fd9a4fddfd2464cce6b20a18
Physloc
Mirrored N/A
VTD vtscsi72
Status Available
LUN 0x8500000000000000
Backing device archive_d1c.cb45fea8aed10491e0df5e9578c9a726
Physloc
Mirrored N/A
VTD vtscsi73
Status Available
LUN 0x8600000000000000
Backing device archive_d1d.b4277aa6b6c4b737084913f78104a90c
Physloc
Mirrored N/A
VTD vtscsi74
Status Available
LUN 0x8700000000000000
Backing device archive_d1e.2a7a12d38d59d5ae415d64d5869b1144
Physloc
Mirrored N/A
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|