On Wed, Feb 17, 2010 at 15:22, Daniel Carosone <d...@geek.com.au> wrote:
> On Wed, Feb 17, 2010 at 12:31:27AM -0500, Ethan wrote: > > And I just realized - yes, labels 2 and 3 are in the wrong place relative > to > > the end of the drive; I did not take into account the overhead taken up > by > > truecrypt when dd'ing the data. The raw drive is 1500301910016 bytes; the > > truecrypt volume is 1500301647872 bytes. Off by 262144 bytes - I need a > > slice that is sized like the truecrypt volume. > > It shouldn't matter if the slice is larger than the original; this is > how autoexpand works. 2 should be near the start (with 1), 3 should > be near the logical end (with 4). > > Did this resolve the issue? You didn't say, and I have my doubts. I'm > not sure this is your problem, but it seems you're on the track to > finding the real problem. > > In the labels you can see, are the txg's the same for all pool > members? If not, you may still need import -F, once all the > partitioning gets sorted out. > > Also, re-reading what I wrote above, I realised I was being ambiguous > in my use of "label". Sometimes I meant the zfs labels that zdb -l > prints, and sometimes I meant the vtoc that format uses for slices. In > the BSD world we call those labels too, and I didn't realise I was > mixing terms. Sorry for any confusion but it seems you figured out > what I meant :) > > -- > Dan. 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. 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. 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. txg is the same for every volume. -Ethan
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
