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
W
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 ch
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
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 poo
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 t
> 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 D
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
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman
> 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