On Wed, Feb 17, 2010 at 03:37:59PM -0500, Ethan wrote: > On Wed, Feb 17, 2010 at 15:22, Daniel Carosone <d...@geek.com.au> wrote: > I have not yet successfully imported. I can see two ways of making progress > forward. One is forcing zpool to attempt to import using slice 2 for each > disk rather than slice 8. If this is how autoexpand works, as you say, it > seems like it should work fine for this. But I don't know how, or if it is > possible to, make it use slice 2.
Just get rid of 8? :-) Normally, when using the whole disk, convention is that slice 0 is used, and there's a small initial offset (for the EFI label). I think you probably want to make a slice 0 that spans the right disk sectors. Were you using some other partitioning inside the truecrypt "disks"? What devices were given to zfs-fuse, and what was their starting offset? You may need to account for that, too. How did you copy the data, and to what target device, on what platform? Perhaps the truecrypt device's partition table is now at the start of the physical disk, but solaris can't read it properly? If that's an MBR partition table (which you look at with fdisk), you could try zdb -l on /dev/dsk/c...p[01234] as well. We're just guessing here.. to provide more concrete help, you'll need to show us some of the specifics, both of what you did and what you've ended up with. fdisk and format partition tables and zdb -l output would be a good start. Figuring out what is different about the disk where s2 was used would be handy too. That may be a synthetic label because something is missing from that disk that the others have. > The other way is to make a slice that is the correct size of the volumes as > I had them before (262144 bytes less than the size of the disk). It seems > like this should cause zpool to prefer to use this slice over slice 8, as it > can find all 4 labels, rather than just labels 0 and 1. I don't know how to > go about this either, or if it's possible. I have been starting to read > documentation on slices in solaris but haven't had time to get far enough to > figure out what I need. format will let you examine and edit these. Start by making sure they have all the same partitioning, flags, etc. > I also have my doubts about this solving my actual issues - the ones that > caused me to be unable to import in zfs-fuse. But I need to solve this issue > before I can move forward to figuring out/solving whatever that issue was. Yeah - my suspicion is that import -F may help here. That is a pool recovery mode, where it rolls back progressive transactions until it finds one that validates correctly. It was only added recently and is probably missing from the fuse version. -- Dan.
pgpZ5Qt78UfHj.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
