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 an
Hello,
This sounds similar to a problem I had a few months ago:
http://bugs.opensolaris.org/bugdatabase/view_bug.do?bug_id=6869512
I don't have a solution, but information from this possibly related
bug may help.
Andrew
___
zfs-discuss mailing list
zfs
On 2009-Nov-18 08:40:41 -0800, Orvar Korvar
wrote:
>There is a new PSARC in b126(?) that allows to rollback to latest functioning
>uber block. Maybe it can help you?
It's in b128 and the feedback I've received suggests it will work.
I've been trying to get the relevant ZFS bits for my b127 syst
On 2009-Nov-19 02:57:31 +0300, Victor Latushkin
wrote:
>> all the cabling, Solaris panic'd before reaching single user.
>
>Do you have crash dump of this panic saved?
Yes. It was provided to Sun Support.
>Option -F is new one added with pool recovery support, so it'll be
>available in build 1
Peter Jeremy 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 unt
There is a new PSARC in b126(?) that allows to rollback to latest functioning
uber block. Maybe it can help you?
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/lis
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
