I used a zpool on a usb key today to get some core files off a non-networked Thumper running S10U4 beta. Plugging the stick into my SXCE b61 x86 machine worked fine; I just had to ''zpool import sticky'' and it worked ok. But when we attach the drive to a blade 100 (running s10u3), it sees the pool as corrupt. I thought I''d been too hasty pulling out the stick, but it works ok back in the b61 desktop and Thumper. I''m trying to figure out if this is an endian thing (which I thought ZFS was immune from) - or has the b61 machine upgraded the zpool format? -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
> I used a zpool on a usb key today to get some core files off a non-networked > Thumper running S10U4 beta. > > Plugging the stick into my SXCE b61 x86 machine worked fine; I just had to > ''zpool import sticky'' and it worked ok. > > But when we attach the drive to a blade 100 (running s10u3), it sees the > pool as corrupt. I thought I''d been too hasty pulling out the stick, > but it works ok back in the b61 desktop and Thumper. > > I''m trying to figure out if this is an endian thing (which I thought > ZFS was immune from) - or has the b61 machine upgraded the zpool > format?Most likely the zpool on the usb stick was formatted using a zpool version that s10u3 does not yet support. Check with "zpool version" on the b61 machine which zpool version is supported by b61, any which zpool version is on the usb stick. Repeat on the s10u3 machine. This message posted from opensolaris.org
Shouldn''t S10u3 just see the newer on-disk format and report that fact, rather than complain it is corrupt? Andrew. This message posted from opensolaris.org
> Shouldn''t S10u3 just see the newer on-disk format and > report that fact, rather than complain it is corrupt?Yep, I just tried it, and it refuses to "zpool import" the newer pool, telling me about the incompatible version. So I guess the pool format isn''t the correct explanation for the Dick Davies'' (number9) problem. On a S-x86 box running snv_68, ZFS version 7: # mkfile 256m /home/leo.nobackup/tmp/zpool_test.vdev # zpool create test_pool /home/leo.nobackup/tmp/zpool_test.vdev # zpool export test_pool On a S-sparc box running snv_61, ZFS version 3 (I get the same error on S-x86, running S10U2, ZFS version 2): # zpool import -d /home/leo.nobackup/tmp/ pool: test_pool id: 6231880247307261822 state: FAULTED status: The pool is formatted using an incompatible version. action: The pool cannot be imported. Access the pool on a system running newer software, or recreate the pool from backup. see: http://www.sun.com/msg/ZFS-8000-A5 config: test_pool UNAVAIL newer version /home/leo.nobackup/tmp//zpool_test.vdev ONLINE This message posted from opensolaris.org
It would be really handy if whoever was responsible for the message at: http://www.sun.com/msg/ZFS-8000-A5 could add data about which zpool versions are supported at specific OS/patch releases. The current message doesn''t help the user figure out how to accomplish their implied task, which is to import the pool on a different system. Adding the version number of the pool that couldn''t be imported to the zpool import error message would be nice too.> > Shouldn''t S10u3 just see the newer on-disk format > and > > report that fact, rather than complain it is > corrupt? > > Yep, I just tried it, and it refuses to "zpool > import" the newer pool, > telling me about the incompatible version. So I > guess the pool > format isn''t the correct explanation for the Dick > Davies'' (number9) > problem. > > > > On a S-x86 box running snv_68, ZFS version 7: > > # mkfile 256m /home/leo.nobackup/tmp/zpool_test.vdev > # zpool create test_pool > /home/leo.nobackup/tmp/zpool_test.vdev > # zpool export test_pool > > > On a S-sparc box running snv_61, ZFS version 3 > (I get the same error on S-x86, running S10U2, ZFS > version 2): > > # zpool import -d /home/leo.nobackup/tmp/ > pool: test_pool > id: 6231880247307261822 > tate: FAULTED > status: The pool is formatted using an incompatible > version. > action: The pool cannot be imported. Access the pool > on a system running newer > software, or recreate the pool from backup. > http://www.sun.com/msg/ZFS-8000-A5 > config: > > test_pool > UNAVAIL newer > version > /home/leo.nobackup/tmp//zpool_test.vdev > ONLINEThis message posted from opensolaris.org
On Wed, 27 Jun 2007, [UTF-8] J?rgen Keil wrote:> Yep, I just tried it, and it refuses to "zpool import" the newer pool, > telling me about the incompatible version. So I guess the pool format > isn''t the correct explanation for the Dick Davies'' (number9) problem.Have you tried creating the pool on b61 and importing it into b68? Regards, markm
Thanks to everyone for the sanity check - I think it''s a platform issue, but not an endian one. The stick was originally DOS-formatted, and the zpool was built on the first fdisk partition. So Sparcs aren''t seeing it, but the x86/x64 boxes are. -- Rasputin :: Jack of All Trades - Master of Nuns http://number9.hellooperator.net/
I had a similar situation between x86 and SPARC, version number. When I created the pool on the LOWER rev machine, it was seen by the HIGHER rev machine. This was a USB HDD, not a stick. I can now move the drive between boxes. HTH, Mike Dick Davies wrote:> Thanks to everyone for the sanity check - I think > it''s a platform issue, but not an endian one. > > The stick was originally DOS-formatted, and the zpool was built on the > first > fdisk partition. So Sparcs aren''t seeing it, but the x86/x64 boxes are. > >-- <http://www.sun.com/solaris> * Michael Lee * Area System Support Engineer *Sun Microsystems, Inc.* Phone x40782 / 866 877 8350 Email Mike.Lee at Sun.COM <http://www.sun.com/solaris> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070627/2f035b5d/attachment.html>
William D. Hathaway wrote:> It would be really handy if whoever was responsible for the message at: > http://www.sun.com/msg/ZFS-8000-A5 > could add data about which zpool versions are supported at specific OS/patch releases.Did you look at http://www.opensolaris.org/os/community/zfs/version/N Where ''N'' is the version number? --matt $ zpool upgrade -v This system is currently running ZFS pool version 8. The following versions are supported: VER DESCRIPTION --- -------------------------------------------------------- 1 Initial ZFS version 2 Ditto blocks (replicated metadata) 3 Hot spares and double parity RAID-Z 4 zpool history 5 Compression using the gzip algorithm 6 pool properties 7 Separate intent log devices 8 Delegated administration For more information on a particular version, including supported releases, see: http://www.opensolaris.org/os/community/zfs/version/N Where ''N'' is the version number.