Looks like my main data pool is borked. I''ve got one essentially
current
backup, and one older backup, plus the photos are mostly backed up on
archival optical disks, so this isn''t as disastrous as it might be, but
still, recovering several hundred gigabytes on home equipment is a pain.
Hence I''d prefer to recover the pool if that''s reasonably
possible.
When I boot from hard disk (a recent OpenSolaris 2008.11 installation),
which was set up to mount my data pool (separate from the rpool), the
system goes into a reboot loop.
When I boot from the OpenSolaris 2008.11 LiveCd, it sits around running
perfectly happily until I manually import my data pool (zp1). Then it
goes into what appears to be the same reboot loop.
The only data capture I''ve been able to manage so far is a photo of the
stack traceback on-screen just before it reboots. The previous data
scrolls by faster than I can see it, and the traceback only stays on
screen about 3 seconds (but that''s enough time to snap a photo). So
you
can see that ZFS scrub code plays a significant part in the stack
traceback; hence perhaps my impression that my system instability was
somewhat scrub-related. I''ve attached the photo; I think photo
attachments get through into the lists here, I''ve seen them in the
past.
If it doesn''t, and you need to see, please email me, and I''ll
send it
individually, or post it on a public web space, or something.
And, any ideas on how I can recover this pool? Or any data I might be
able to capture and send back that would help fix whatever is going on,
even if we can''t recover the pool?
--
David Dyer-Bennet, dd-b at dd-b.net; http://dd-b.net/
Snapshots: http://dd-b.net/dd-b/SnapshotAlbum/data/
Photos: http://dd-b.net/photography/gallery/
Dragaera: http://dragaera.info
-------------- next part --------------
A non-text attachment was scrubbed...
Name: P1000697.jpg
Type: image/jpeg
Size: 70328 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20090130/2dea2d21/attachment.jpg>