Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Fajar A. Nugraha
On Thu, Sep 17, 2009 at 8:55 PM, Paul Archer p...@paularcher.org wrote:
 I can reboot into Linux and import the pools, but haven't figured out why I
 can't import them in Solaris. I don't know if it makes a difference (I
 wouldn't think so), but zfs-fuse under Linux is using ZFS version 13, where
 Nexenta is using version 14.

Just a guess, but did you use the whole drive while creating the pool
on Linux? Something like zpool create poolname raidz sda sdb sdc ?

-- 
Fajar
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Paul Archer

10:09pm, Fajar A. Nugraha wrote:


On Thu, Sep 17, 2009 at 8:55 PM, Paul Archer p...@paularcher.org wrote:

I can reboot into Linux and import the pools, but haven't figured out why I
can't import them in Solaris. I don't know if it makes a difference (I
wouldn't think so), but zfs-fuse under Linux is using ZFS version 13, where
Nexenta is using version 14.


Just a guess, but did you use the whole drive while creating the pool
on Linux? Something like zpool create poolname raidz sda sdb sdc ?

Yes, I did. I was under the impression that was the way to go. If it's not 
(ie it needs to be a single disk-sized partion), I can try moving. I'm 
assuming if I add a partition, I can do something like:

zpool replace datapool sda sda1

Paul
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Darren J Moffat

Paul Archer wrote:

10:09pm, Fajar A. Nugraha wrote:


On Thu, Sep 17, 2009 at 8:55 PM, Paul Archer p...@paularcher.org wrote:
I can reboot into Linux and import the pools, but haven't figured out 
why I

can't import them in Solaris. I don't know if it makes a difference (I
wouldn't think so), but zfs-fuse under Linux is using ZFS version 13, 
where

Nexenta is using version 14.


Just a guess, but did you use the whole drive while creating the pool
on Linux? Something like zpool create poolname raidz sda sdb sdc ?

Yes, I did. I was under the impression that was the way to go. If it's 
not (ie it needs to be a single disk-sized partion), I can try moving. 
I'm assuming if I add a partition, I can do something like:

zpool replace datapool sda sda1


What kind of partition table is on the disks, is it EFI ?  If not that 
might be part of the issue.


--
Darren J Moffat
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Paul Archer

10:40am, Paul Archer wrote:

I can reboot into Linux and import the pools, but haven't figured out why 
I

can't import them in Solaris. I don't know if it makes a difference (I
wouldn't think so), but zfs-fuse under Linux is using ZFS version 13, 
where

Nexenta is using version 14.


Just a guess, but did you use the whole drive while creating the pool
on Linux? Something like zpool create poolname raidz sda sdb sdc ?

Yes, I did. I was under the impression that was the way to go. If it's not 
(ie it needs to be a single disk-sized partion), I can try moving. I'm 
assuming if I add a partition, I can do something like:

zpool replace datapool sda sda1

Or not. I see that if I try to replace sda with sda1, zpool complains that 
sda1 is too small.


Any suggestions (that don't include 'start over')?

Paul
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Paul Archer

5:08pm, Darren J Moffat wrote:


Paul Archer wrote:

10:09pm, Fajar A. Nugraha wrote:


On Thu, Sep 17, 2009 at 8:55 PM, Paul Archer p...@paularcher.org wrote:
I can reboot into Linux and import the pools, but haven't figured out why 
I

can't import them in Solaris. I don't know if it makes a difference (I
wouldn't think so), but zfs-fuse under Linux is using ZFS version 13, 
where

Nexenta is using version 14.


Just a guess, but did you use the whole drive while creating the pool
on Linux? Something like zpool create poolname raidz sda sdb sdc ?

Yes, I did. I was under the impression that was the way to go. If it's not 
(ie it needs to be a single disk-sized partion), I can try moving. I'm 
assuming if I add a partition, I can do something like:

zpool replace datapool sda sda1


What kind of partition table is on the disks, is it EFI ?  If not that might 
be part of the issue.


I don't believe there is any partition table on the disks. I pointed zfs 
to the raw disks when I setup the pool.


Paul
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Darren J Moffat

Paul Archer wrote:
What kind of partition table is on the disks, is it EFI ?  If not that 
might be part of the issue.


I don't believe there is any partition table on the disks. I pointed zfs 
to the raw disks when I setup the pool.


If you run fdisk on OpenSolaris against this disk what does it show as 
the partition type eg:


fdisk -v /dev/rdsk/c7t4d0p0

Mine shows:

  1 EFI   0  4560045601100

Which tells me I have an EFI label on the disk.

My boot ZFS pool shows this:

one one side of the mirror:

  1 Diagnostic0 3   4  0
  2   ActiveSolaris2  4  4559945596100
and on the other:

  1   ActiveSolaris2  1  4559945599100

--
Darren J Moffat
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Paul Archer

6:44pm, Darren J Moffat wrote:


Paul Archer wrote:
What kind of partition table is on the disks, is it EFI ?  If not that 
might be part of the issue.


I don't believe there is any partition table on the disks. I pointed zfs to 
the raw disks when I setup the pool.


If you run fdisk on OpenSolaris against this disk what does it show as the 
partition type eg:


fdisk -v /dev/rdsk/c7t4d0p0

Mine shows:

 1 EFI   0  4560045601100

Which tells me I have an EFI label on the disk.

My boot ZFS pool shows this:

one one side of the mirror:

 1 Diagnostic0 3   4  0
 2   ActiveSolaris2  4  4559945596100
and on the other:

 1   ActiveSolaris2  1  4559945599100

--


I just took a look, and it seems that all the drives have a single 
partition on them. I'm looking under Linux, as I can't reboot it into 
Solaris again until I get home tonight.


r...@ubuntu:~# fdisk -l /dev/sda

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xce13f90b

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1  182401  1465136001   83  Linux

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Darren J Moffat

Paul Archer wrote:

r...@ubuntu:~# fdisk -l /dev/sda

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xce13f90b

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1  182401  1465136001   83  Linux


That is good enough.  That is your problem right there.  Solaris doesn't 
recognise this partition type.  FreeBSD I think does.


I'm not sure what you can do to get Solaris to recognise this.  If there 
is a non destructive way under Linux to change this to an EFI partition 
that would be a good way to start.


I doubt that simply changing the tag from Linux (32) to Solaris2 (191) 
would be enough since you would lack the vtoc in there.  Plus ideally 
you want this as EFI unless you need to put OpenSolaris into that pool 
to boot from it - but sounds like you don't.


--
Darren J Moffat
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Paul Archer

7:37pm, Darren J Moffat wrote:


Paul Archer wrote:

r...@ubuntu:~# fdisk -l /dev/sda

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xce13f90b

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1  182401  1465136001   83  Linux


That is good enough.  That is your problem right there.  Solaris doesn't 
recognise this partition type.  FreeBSD I think does.


I'm not sure what you can do to get Solaris to recognise this.  If there is a 
non destructive way under Linux to change this to an EFI partition that would 
be a good way to start.


I doubt that simply changing the tag from Linux (32) to Solaris2 (191) would 
be enough since you would lack the vtoc in there.  Plus ideally you want this 
as EFI unless you need to put OpenSolaris into that pool to boot from it - 
but sounds like you don't.




I did a little research and found that parted on Linux handles EFI 
labelling. I used it to change the partition scheme on sda, creating an 
sda1. I then offlined sda and replaced it with sda1. I wish I had just 
tried a scrub instead of the replace, though, as I've gotta wait about 35 
hours for the resilver to finish. (1.5TB data on five disks with a single 
PCI controller card.)


Paul
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Andrew Gabriel

Darren J Moffat wrote:

Paul Archer wrote:

r...@ubuntu:~# fdisk -l /dev/sda

Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
255 heads, 63 sectors/track, 182401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xce13f90b

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   1  182401  1465136001   83  Linux


That is good enough.  That is your problem right there.  Solaris doesn't 
recognise this partition type.  FreeBSD I think does.


I'm not sure what you can do to get Solaris to recognise this.  If there 
is a non destructive way under Linux to change this to an EFI partition 
that would be a good way to start.


ZFS should just find this as /dev/dsk/c?t?d?p1 if the structures really 
are unrecognizable as a zpool device (on x86 only - won't work on 
sparc). I haven't tried importing in this way, but I'm pretty sure I 
have created zpools on raw primary fdisk partitions.


I doubt that simply changing the tag from Linux (32) to Solaris2 (191) 
would be enough since you would lack the vtoc in there. 


You really don't want it to be a partition type Solaris recognizes as 
something else.


Plus ideally 
you want this as EFI unless you need to put OpenSolaris into that pool 
to boot from it - but sounds like you don't.


--
Andrew

___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Fajar A. Nugraha
On Fri, Sep 18, 2009 at 4:08 AM, Paul Archer p...@paularcher.org wrote:
 I did a little research and found that parted on Linux handles EFI
 labelling. I used it to change the partition scheme on sda, creating an
 sda1. I then offlined sda and replaced it with sda1. I wish I had just tried
 a scrub instead of the replace, though, as I've gotta wait about 35 hours
 for the resilver to finish. (1.5TB data on five disks with a single PCI
 controller card.)

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.

So in short, if you had created the pool on top of sda1 instead of
sda, it will work. I'm surprised though that you can offlined sda and
replaced it with sda1 when previously you said I see that if I try
to replace sda with sda1, zpool complains that sda1 is too small

-- 
Fajar
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Paul Archer

Tomorrow, 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.

So in short, if you had created the pool on top of sda1 instead of
sda, it will work. I'm surprised though that you can offlined sda and
replaced it with sda1 when previously you said I see that if I try
to replace sda with sda1, zpool complains that sda1 is too small



I was a bit surprised about that, too. But I found that a standard 
PC/Linux partition reserves around 24MB at the beginning of the disk, and 
an EFI (or actually, GPT) disklabel and partition only uses a few 100KB.


Paul
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss


Re: [zfs-discuss] migrating from linux to solaris ZFS

2009-09-17 Thread Al Muckart

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