I want to import my zpool''s from FreeBSD 8.0 in OpenSolaris 2009.06. After reading the few posts (links below) I was able to find on the subject, it seems like it there is a differences between FreeBSD and Solaris. FreeBSD operates on directly on the disk and Solaris creates a partion and uses that... is that right? Is it impossible for OpenSolaris to use zpool''s from FreeBSD? * opensolaris.org/jive/thread.jspa?messageID=445766 * opensolaris.org/jive/thread.jspa?messageID=450755&; * mail.opensolaris.org/pipermail/ug-nzosug/2009-June/000027.html This is "zpool import" from my machine with OpenSolaris 2009.06 (all zpool''s are fine in FreeBSD). Notice that the zpool named "temp" can be imported. Why not "secure" then? Is it because it is raidz1? pool: secure id: 15384175022505637073 state: UNAVAIL status: One or more devices contains corrupted data. action: The pool cannot be imported due to damaged devices or data. see: sun.com/msg/ZFS-8000-5E config: secure UNAVAIL insufficient replicas raidz1 UNAVAIL insufficient replicas c8t1d0p0 ONLINE c8t2d0s2 ONLINE c8t3d0s8 UNAVAIL corrupted data c8t4d0s8 UNAVAIL corrupted data pool: temp id: 10889808377251842082 state: ONLINE status: The pool is formatted using an older on-disk version. action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit ''zpool upgrade''. config: temp ONLINE c8t0d0p0 ONLINE -- This message posted from opensolaris.org
Fajar A. Nugraha
2010-Feb-24 02:16 UTC
[zfs-discuss] Import zpool from FreeBSD in OpenSolaris
On Wed, Feb 24, 2010 at 9:11 AM, patrik <spam at dentarg.net> wrote:> This is "zpool import" from my machine with OpenSolaris 2009.06 (all zpool''s are fine in FreeBSD). Notice that the zpool named "temp" can be imported. Why not "secure" then? Is it because it is raidz1?> status: One or more devices contains corrupted data.> ? ? ? ? ? ?c8t3d0s8 ?UNAVAIL ?corrupted data > ? ? ? ? ? ?c8t4d0s8 ?UNAVAIL ?corrupted dataI''d suggest you try reimporting them in FreeBSD. It''s possible that those disks are really corrupted. Another option is to try latest opensolaris livecd from genunix.org, and try to import it there. -- Fajar
On 2010-02-24 03.16, Fajar A. Nugraha wrote:> On Wed, Feb 24, 2010 at 9:11 AM, patrik <spam at dentarg.net> wrote: >> This is "zpool import" from my machine with OpenSolaris 2009.06 (all zpool''s are fine in FreeBSD). Notice that the zpool named "temp" can be imported. Why not "secure" then? Is it because it is raidz1? > >> status: One or more devices contains corrupted data. > >> c8t3d0s8 UNAVAIL corrupted data >> c8t4d0s8 UNAVAIL corrupted data > > I''d suggest you try reimporting them in FreeBSD. It''s possible that > those disks are really corrupted.I have. They are not corrupted. In fact, I''m using them in FreeBSD now. :-)> Another option is to try latest opensolaris livecd from genunix.org, > and try to import it there.I''m gonna give it a try. Thanks.
Bob Friesenhahn
2010-Feb-24 02:22 UTC
[zfs-discuss] Import zpool from FreeBSD in OpenSolaris
On Wed, 24 Feb 2010, Fajar A. Nugraha wrote:> On Wed, Feb 24, 2010 at 9:11 AM, patrik <spam at dentarg.net> wrote: >> This is "zpool import" from my machine with OpenSolaris 2009.06 (all zpool''s are fine in FreeBSD). Notice that the zpool named "temp" can be imported. Why not "secure" then? Is it because it is raidz1? > >> status: One or more devices contains corrupted data. > >> ? ? ? ? ? ?c8t3d0s8 ?UNAVAIL ?corrupted data >> ? ? ? ? ? ?c8t4d0s8 ?UNAVAIL ?corrupted data > > I''d suggest you try reimporting them in FreeBSD. It''s possible that > those disks are really corrupted. > Another option is to try latest opensolaris livecd from genunix.org, > and try to import it there.Just a couple of days ago there was discussion of importing disks from Linux FUSE zfs. The import was successful. The same methods used (directory containing symbolic links to desired device partitions) might be used. Bob -- Bob Friesenhahn bfriesen at simple.dallas.tx.us, simplesystems.org/users/bfriesen GraphicsMagick Maintainer, GraphicsMagick.org
Thomas Burgess
2010-Feb-24 02:25 UTC
[zfs-discuss] Import zpool from FreeBSD in OpenSolaris
When i needed to do this, the only way i could get it to work was to do this: Take some disks, use a Opensolaris Live CD and label them EFI Create a ZPOOL in FreeBSD with these disks copy my data from freebsd to the new zpool export the pool import the pool On Tue, Feb 23, 2010 at 9:11 PM, patrik <spam at dentarg.net> wrote:> I want to import my zpool''s from FreeBSD 8.0 in OpenSolaris 2009.06. > > After reading the few posts (links below) I was able to find on the > subject, it seems like it there is a differences between FreeBSD and > Solaris. FreeBSD operates on directly on the disk and Solaris creates a > partion and uses that... is that right? Is it impossible for OpenSolaris to > use zpool''s from FreeBSD? > > * opensolaris.org/jive/thread.jspa?messageID=445766 > * opensolaris.org/jive/thread.jspa?messageID=450755&; > * mail.opensolaris.org/pipermail/ug-nzosug/2009-June/000027.html > > This is "zpool import" from my machine with OpenSolaris 2009.06 (all > zpool''s are fine in FreeBSD). Notice that the zpool named "temp" can be > imported. Why not "secure" then? Is it because it is raidz1? > > pool: secure > id: 15384175022505637073 > state: UNAVAIL > status: One or more devices contains corrupted data. > action: The pool cannot be imported due to damaged devices or data. > see: sun.com/msg/ZFS-8000-5E > config: > > secure UNAVAIL insufficient replicas > raidz1 UNAVAIL insufficient replicas > c8t1d0p0 ONLINE > c8t2d0s2 ONLINE > c8t3d0s8 UNAVAIL corrupted data > c8t4d0s8 UNAVAIL corrupted data > > > pool: temp > id: 10889808377251842082 > state: ONLINE > status: The pool is formatted using an older on-disk version. > action: The pool can be imported using its name or numeric identifier, > though > some features will not be available without an explicit ''zpool > upgrade''. > config: > > temp ONLINE > c8t0d0p0 ONLINE > -- > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100223/d390a3ce/attachment.html>
Marc Nicholas
2010-Feb-24 02:30 UTC
[zfs-discuss] Import zpool from FreeBSD in OpenSolaris
send and receive?! -marc On Tue, Feb 23, 2010 at 9:25 PM, Thomas Burgess <wonslung at gmail.com> wrote:> When i needed to do this, the only way i could get it to work was to do > this: > > Take some disks, use a Opensolaris Live CD and label them EFI > Create a ZPOOL in FreeBSD with these disks > copy my data from freebsd to the new zpool > export the pool > import the pool > > > > > On Tue, Feb 23, 2010 at 9:11 PM, patrik <spam at dentarg.net> wrote: > >> I want to import my zpool''s from FreeBSD 8.0 in OpenSolaris 2009.06. >> >> After reading the few posts (links below) I was able to find on the >> subject, it seems like it there is a differences between FreeBSD and >> Solaris. FreeBSD operates on directly on the disk and Solaris creates a >> partion and uses that... is that right? Is it impossible for OpenSolaris to >> use zpool''s from FreeBSD? >> >> * opensolaris.org/jive/thread.jspa?messageID=445766 >> * opensolaris.org/jive/thread.jspa?messageID=450755&; >> * mail.opensolaris.org/pipermail/ug-nzosug/2009-June/000027.html >> >> This is "zpool import" from my machine with OpenSolaris 2009.06 (all >> zpool''s are fine in FreeBSD). Notice that the zpool named "temp" can be >> imported. Why not "secure" then? Is it because it is raidz1? >> >> pool: secure >> id: 15384175022505637073 >> state: UNAVAIL >> status: One or more devices contains corrupted data. >> action: The pool cannot be imported due to damaged devices or data. >> see: sun.com/msg/ZFS-8000-5E >> config: >> >> secure UNAVAIL insufficient replicas >> raidz1 UNAVAIL insufficient replicas >> c8t1d0p0 ONLINE >> c8t2d0s2 ONLINE >> c8t3d0s8 UNAVAIL corrupted data >> c8t4d0s8 UNAVAIL corrupted data >> >> >> pool: temp >> id: 10889808377251842082 >> state: ONLINE >> status: The pool is formatted using an older on-disk version. >> action: The pool can be imported using its name or numeric identifier, >> though >> some features will not be available without an explicit ''zpool >> upgrade''. >> config: >> >> temp ONLINE >> c8t0d0p0 ONLINE >> -- >> This message posted from opensolaris.org >> _______________________________________________ >> zfs-discuss mailing list >> zfs-discuss at opensolaris.org >> mail.opensolaris.org/mailman/listinfo/zfs-discuss >> > > > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > mail.opensolaris.org/mailman/listinfo/zfs-discuss > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100223/beca7d52/attachment.html>
On Tue, Feb 23, 2010 at 21:22, Bob Friesenhahn <bfriesen at simple.dallas.tx.us> wrote:> On Wed, 24 Feb 2010, Fajar A. Nugraha wrote: > > On Wed, Feb 24, 2010 at 9:11 AM, patrik <spam at dentarg.net> wrote: >> >>> This is "zpool import" from my machine with OpenSolaris 2009.06 (all >>> zpool''s are fine in FreeBSD). Notice that the zpool named "temp" can be >>> imported. Why not "secure" then? Is it because it is raidz1? >>> >> >> status: One or more devices contains corrupted data. >>> >> >> c8t3d0s8 UNAVAIL corrupted data >>> c8t4d0s8 UNAVAIL corrupted data >>> >> >> I''d suggest you try reimporting them in FreeBSD. It''s possible that >> those disks are really corrupted. >> Another option is to try latest opensolaris livecd from genunix.org, >> and try to import it there. >> > > Just a couple of days ago there was discussion of importing disks from > Linux FUSE zfs. The import was successful. The same methods used > (directory containing symbolic links to desired device partitions) might be > used. > > Bob > -- >Yes, I ran into this very recently, moving from zfs-fuse on linux to OpenSolaris. My import looked almost exactly like yours. I did something along the lines of: mkdir dskp0s # create a temp directory to point to the p0 partitions of the relevant disks cd dskp0s ln -s /dev/dsk/c8t1d0p0 ln -s /dev/dsk/c8t2d0p0 ln -s /dev/dsk/c8t3d0p0 ln -s /dev/dsk/c8t4d0p0 zpool import -d . secure (substituting in info for your pool) and it imported, no problem. -Ethan -------------- next part -------------- An HTML attachment was scrubbed... URL: <mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100223/a5f0fb6f/attachment.html>
lists at dentarg.net
2010-Feb-24 13:12 UTC
[zfs-discuss] Import zpool from FreeBSD in OpenSolaris
On Wed, Feb 24, 2010 at 3:31 AM, Ethan <notethan at gmail.com> wrote:> On Tue, Feb 23, 2010 at 21:22, Bob Friesenhahn > <bfriesen at simple.dallas.tx.us> wrote: >> Just a couple of days ago there was discussion of importing disks from >> Linux FUSE zfs. ?The import was successful. ?The same methods used >> (directory containing symbolic links to desired device partitions) might be >> used. > > Yes, I ran into this very recently, moving from zfs-fuse on linux to > OpenSolaris. My import looked almost exactly like yours. I did something > along the lines of: > mkdir dskp0s # create a temp directory to point to the p0 partitions of the > relevant disks > cd dskp0s > ln -s /dev/dsk/c8t1d0p0 > ln -s /dev/dsk/c8t2d0p0 > ln -s /dev/dsk/c8t3d0p0 > ln -s /dev/dsk/c8t4d0p0 > zpool import -d .?secure > (substituting in info for your pool) and it imported, no problem.I have read your thread now ("Help with corrupted pool" for anyone interested). It raised some questions in my head... Someone wrote that this method "will not work at boot"? Does that mean that the pool won''t automount at boot or that I can''t boot from it (that one I don''t mind)? Also, if I import the pool successfully in OpenSolaris (and don''t do zfs/zpool upgrade), will that destroy my chances of importing it in FreeBSD again in the (near) future? I haven''t tried importing because I''m not yet ready to make the switch to OpenSolaris, I need to replace a controller (Promise PDC40518 SATA150 TX4) that isn''t recognized, but that''s another issue. I too would want an answer to "Is there any significant advantage to having a partition table?", but seeing that your last post is pretty new, maybe that will come. Thanks for the help.
On Wed, Feb 24, 2010 at 08:12, <lists at dentarg.net> wrote:> On Wed, Feb 24, 2010 at 3:31 AM, Ethan <notethan at gmail.com> wrote: > > On Tue, Feb 23, 2010 at 21:22, Bob Friesenhahn > > <bfriesen at simple.dallas.tx.us> wrote: > >> Just a couple of days ago there was discussion of importing disks from > >> Linux FUSE zfs. The import was successful. The same methods used > >> (directory containing symbolic links to desired device partitions) might > be > >> used. > > > > Yes, I ran into this very recently, moving from zfs-fuse on linux to > > OpenSolaris. My import looked almost exactly like yours. I did something > > along the lines of: > > mkdir dskp0s # create a temp directory to point to the p0 partitions of > the > > relevant disks > > cd dskp0s > > ln -s /dev/dsk/c8t1d0p0 > > ln -s /dev/dsk/c8t2d0p0 > > ln -s /dev/dsk/c8t3d0p0 > > ln -s /dev/dsk/c8t4d0p0 > > zpool import -d . secure > > (substituting in info for your pool) and it imported, no problem. > > I have read your thread now ("Help with corrupted pool" for anyone > interested). It raised some questions in my head... Someone wrote that > this method "will not work at boot"? Does that mean that the pool > won''t automount at boot or that I can''t boot from it (that one I don''t > mind)? > > Also, if I import the pool successfully in OpenSolaris (and don''t do > zfs/zpool upgrade), will that destroy my chances of importing it in > FreeBSD again in the (near) future? > > I haven''t tried importing because I''m not yet ready to make the switch > to OpenSolaris, I need to replace a controller (Promise PDC40518 > SATA150 TX4) that isn''t recognized, but that''s another issue. > > I too would want an answer to "Is there any significant advantage to > having a partition table?", but seeing that your last post is pretty > new, maybe that will come. > > Thanks for the help. >My pool, using p0 devices, does currently mount at boot. This is using the p0 devices in /dev/dsk, not symlinks in a directory (those have been deleted). This does seem like it might indicate that importing the devices changed something on disk - I''m not sure what, but something that has caused it to know that it should use the p0 devices rather than s2 or s8. I have no idea whether this would affect ability to import in BSD. It does not seem like it should, intuitively, but I don''t have much basis in actual knowledge of the inner workings to say that - you shouldn''t take my word for it. As for partition tables, everything seems to be working happily without them. I''d still like to know from somebody more knowledgeable about what I might lose, not having them, but I haven''t run into any issues yet. -Ethan -------------- next part -------------- An HTML attachment was scrubbed... URL: <mail.opensolaris.org/pipermail/zfs-discuss/attachments/20100224/e6b38422/attachment.html>
Mark J Musante
2010-Feb-24 17:19 UTC
[zfs-discuss] Import zpool from FreeBSD in OpenSolaris
On Tue, 23 Feb 2010, patrik wrote:> I want to import my zpool''s from FreeBSD 8.0 in OpenSolaris 2009.06. > > secure UNAVAIL insufficient replicas > raidz1 UNAVAIL insufficient replicas > c8t1d0p0 ONLINE > c8t2d0s2 ONLINE > c8t3d0s8 UNAVAIL corrupted data > c8t4d0s8 UNAVAIL corrupted dataThe zpool import command is finding the wrong slices to import. Notice this says s8 for the last two slice numbers. It''s also using s2 for the second disk, but s2 is typcally the entire disk anyway, so it''s able to see all the data. On the other hand, s8 is typically just the first cylinder -- just enough information for zfs to see the front labels, but not enough to see all the data. zfs should probably be better about what it chooses for a disk to import. A coworker suggests looking at the zdb -l output, fdisk output, and prtvtoc output to see if there''s a common theme that will lead to a solution independent of modifying zfs import code. Regards, markm