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.
pgpAYV8T7I5RZ.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
