UNSOLVED

jgrinwis

updated

20 years ago

J

jgrinwis

1 Rookie

•

99 Posts

0

697

April 11th, 2007 07:00

Incorrect reference on volume

Hi,

trying to create a new fs on my NS502 on a clarata_archive pool but failing and server_log showing followig error:

1176299676: ADMIN: 4: Command succeeded: volume disk 97 c16t1l11 disk_id=20 size=706966
1176299676: ADMIN: 4: Command succeeded: volume disk 97 c0t1l11 disk_id=20 size=706966
1176299676: ADMIN: 4: Command succeeded: volume disk 92 c0t1l14 disk_id=15 size=706966
1176299676: ADMIN: 4: Command succeeded: volume disk 92 c16t1l14 disk_id=15 size=706966
1176299676: ADMIN: 4: Command succeeded: volume stripe 193 16 2 97 92
1176299676: STORAGE: 3: reference - User ptr:0xea05e774 origSt:419430400 currSt:419430400 origBlk:440401920 currBlk:440401920
1176299676: STORAGE: 3: 6: Incorrect reference on volume 193
1176299676: STORAGE: 3: Incorrect reference on volume 193
1176299676: STORAGE: 4: ----- Displaying users of volume 193, referencecount=7 -----
1176299676: STORAGE: 4: UserOfVol=193, UserKind=LVOLUME, userPointer=0x4454, start=0, nBlocks=419430400, referenceCount=4
**** Slice Volume 194 : 0xf5437b84 Information: ****
Start Block Offset: 0
Total References:...............0x0004
Total Blocks:...................0x19000000
Bytes Per Block:................0x0200
# Component Volumes:.......0x001
Component Volume List:.....193
1176299676: STORAGE: 4: UserOfVol=193, UserKind=LVOLUME, userPointer=0xea05eb54, start=419430400, nBlocks=440401920, referenceCount=2
**** Slice Volume 196 : 0xb2d26604 Information: ****
Start Block Offset: 419430400
Total References:...............0x0002
Total Blocks:...................0x1a400000
Bytes Per Block:................0x0200
# Component Volumes:.......0x001
Component Volume List:.....193
1176299676: STORAGE: 4: ----- User list complete for volume 193 -----
1176299676: STORAGE: 3: Slice Volume 218 not created: CTOR Stat = 0003.
1176299676: ADMIN: 3: Command failed: volume slice 218 419430400 440401920 193
Logical Volume 219 not found.
1176299676: ADMIN: 3: Command failed: volume delete 219
Logical Volume 218 not found.
1176299676: ADMIN: 3: Command failed: volume delete 218
Volume 193 not deleted (references 7), returned BUSY.
1176299676: ADMIN: 3: Command failed: volume delete 193
Volume 92 not deleted (references 8), returned BUSY.
1176299676: ADMIN: 3: Command failed: volume delete 92
Volume 97 not deleted (references 8), returned BUSY.
1176299676: ADMIN: 3: Command failed: volume delete 97

What might be the problem here.

Regards,
John Grinwis
  • ironman4

    14 Posts

    263

    0

    Posted April 11th, 2007 07:00

    Hello John,

    I looked in our knowledgebase and found a solution that only technical support can see. So I contacted someone in level 2 support. You need to open a call into the support center ASAP.
  • jgrinwis

    1 Rookie

    •

    99 Posts

    263

    0

    Posted April 11th, 2007 08:00

    IronMan,

    case has been opened and we're waiting for a call back.
  • IanSchorr

    117 Posts

    263

    0

    Posted April 11th, 2007 09:00

    Unfortunately this really is the kind of problem that you'd need to talk to Tech Support about (I know you've opened a call). This typically means that the datamover has an incorrect picture of volumes in memory (or, really, references to volumes) and really should never happen. Tech Support would first take a look at the system to determine if everything's okay.

    It's possible that a reboot of the datamover could correct the problem, but it's best not to do that until the system has been health checked. They may also want to force a memory dump so that we can use that (in addition to logs) try to determine how the system got into the state that it is in and how to prevent it from happening again.
  • jgrinwis

    1 Rookie

    •

    99 Posts

    263

    0

    Posted April 27th, 2007 04:00

    We reloaded the box last night and everything fine again.
  • Rainer_EMC

    6 Operator

    •

    8645 Posts

    263

    0

    Posted April 27th, 2007 11:00

    good to know - but it still was a good idea to open a case - better safe than sorry
  • jgrinwis

    1 Rookie

    •

    99 Posts

    263

    0

    Posted May 4th, 2007 00:00

    We had opened a case before we reloaded the box, they came to the same conclusion, incorrect mapping between memory and disk.