On 2009-Nov-18 11:50:44 +1100, I wrote: >I have a zpool on a JBOD SE3320 that I was using for data with Solaris >10 (the root/usr/var filesystems were all UFS). Unfortunately, we had >a bit of a mixup with SCSI cabling and I believe that we created a >SCSI target clash. The system was unloaded and nothing happened until >I ran "zpool status" at which point things broke. After correcting >all the cabling, Solaris panic'd before reaching single user.
I wound up installing OpenSolaris snv_128a on some spare disks and this enabled me to recover the data. Thanks to Tim Haley and Victor Latushkin for their assistance. As a first attempt, 'zpool import -F data' said "Destroy and re-create the pool from a backup source.". 'zpool import -nFX data' initially ran the system out of swap (I hadn't attached any swap and it only has 8GB RAM): WARNING: /etc/svc/volatile: File system full, swap space limit exceeded INIT: Couldn't write persistent state file `/etc/svc/volatile/init.state'. After rebooting and adding some swap (which didn't seem to ever get used), it did work (though it took several hours - unfortunately, I didn't record exactly how long): # zpool import -nFX data Would be able to return data to its state as of Thu Jan 01 10:00:00 1970. Would discard approximately 369 minutes of transactions. # zpool import -FX data Pool data returned to its state as of Thu Jan 01 10:00:00 1970. Discarded approximately 369 minutes of transactions. cannot share 'data/backup': share(1M) failed cannot share 'data/JumpStart': share(1M) failed cannot share 'data/OS_images': share(1M) failed # I notice that the two times aren't consistent but the data appears to be present and a 'zpool scrub' reported no errors. I have reverted back to Solaris 10 and successfully copied all the data off. -- Peter Jeremy
pgpC0sjEufK37.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
