On 18/09/2009, at 1:08 PM, Fajar A. Nugraha wrote:
There was a post from Ricardo on zfs-fuse list some time ago.
Apparently if you do a "zpool create" on whole disks, Linux on
Solaris behaves differently:
- solaris will create EFI partition on that disk, and use the
partition as vdev
- Linux will use the whole disk without any partition, just like with
a file-based vdev.
The result is that you might be unable to import the pool on
*solaris or *BSD.
The recommended way to create a "portable" pool is to create the pool
on a partition setup recognizable on all those OS. He suggested a
simple DOS/MBR partition table.
I haven't tried this on OSX yet, but I was fighting with this problem
for quite a while with pools created on raw disk devices under
FreeBSD. I'm still confused as to why Solaris won't recognise them,
but both Solaris and FreeBSD will happily import/export pools created
on an EFI/GPT partition using FreeBSD's gpart(1), so if Linux
understands GPT partitions as well that's probably the way to go for
portable pools. FreeBSD 7.2-STABLE will NOT see pools created by
OpenSolaris though, again I don't understand why this is since it
should in theory understand EFI partition tables fine.
I'll try importing a pool on a USB disk with a GPT table on my mac and
see what happens.
--
Alasdair Muckart | William de Wyke | http://wherearetheelves.blogspot.com
"Any sufficiently advanced stupididty is indistinguishable from malice"
-- James D. Macdonald
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
