Tonight I've been moving some of my personal data around on my
desktop system and have hit some on-disk corruption. As you may
know, I'm cursed, and so this had a high probability of ending badly.
I have two SCSI disks and use live upgrade, and I have a partition,
/aux0, where I tend to keep personal stuff. This is on an SB2500
running snv_46.
The upshot is that I have a slice 7 on each of two disks; all of my
data was on one of these slices. So, I turned the other slice into a
zpool, and copied the data from UFS slice to zpool.
Then I tried to attach the UFS slice to the zpool, in order to
form a mirror. The resilver kicked off but eventually ground my
machine to a halt (the last I saw was 77% completed), and I was getting
a ton of these errors:
scsi: WARNING: /[EMAIL PROTECTED],700000/[EMAIL PROTECTED] (glm0):
Resetting scsi bus, got incorrect phase from (1,0)
genunix: NOTICE: glm0: fault detected in device; service still available
genunix: NOTICE: glm0: Resetting scsi bus, got incorrect phase from (1,0)
scsi: WARNING: /[EMAIL PROTECTED],700000/[EMAIL PROTECTED] (glm0):
got SCSI bus reset
genunix: NOTICE: glm0: fault detected in device; service still available
genunix: NOTICE: glm0: got SCSI bus reset
scsi: WARNING: /[EMAIL PROTECTED],700000/[EMAIL PROTECTED]/[EMAIL PROTECTED],0
(sd11):
auto request sense failed (reason=reset)
Eventually I had to drive in to work to reboot the machine, although
the system did not tip over. After a reboot to single user mode, the
same symptoms recurred (since it seems that the resilver kicked off
again... and at a certain stage hit this problem over again).
The only recourse was to reboot to single user mode, rapidly log in, and
detach the problem-causing side of the mirror. This led me to
suggestion #1:
- It'd be nice if auto-resilvering did not kick off until
sometime after we leave single user mode.
So I don't know what might be causing glm to flip out.
Next, I did a scrub of the one slice in my pool and got this:
...
errors: The following persistent errors have been detected:
DATASET OBJECT RANGE
dp_stuff 42073 917504-1048576
dp_stuff 42073 1048576-1179648
This is awesome. I can pinpoint any corruption, which is great.
But... So this may be a stupid question, but it's unclear how to
locate the object in question. I did a find -inum 42073, which
located some help.jar file in a copy of netbeans I have in the
zpool. If that's all I've lost, then hooray!
But I wasn't sure if that was the right thing to do. It'd be great if
the documentation was clearer on this point:
http://docs.sun.com/app/docs/doc/819-5461/6n7ht6qt1?a=view#gbcuz
Just says to try 'rm' on "the file" but does not mention how to
locate it.
I'd appreciate any thoughts on how to resolve the glm bus reset
issue... Thanks!
-dp
--
Daniel Price - Solaris Kernel Engineering - [EMAIL PROTECTED] - blogs.sun.com/dp
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
