Doesn't work w/ an initial offset of 256 either. I suspect that it's something to do w/ it being an USB disk. It's been an EFI label in both instances. I tried offsets from 34 to ~64 w/o any change in behavior.
BTW what's the deal w/ 34? If you try to set anything smaller it's disallowed, though I did manage somehow to get it set to 6. There is a *lot* of inconsistency in the rules in the various parts of the format(1m) utility. I had to dd /dev/zero to straighten up one of the messes I made. I got into a situation where I could not write a label at all until I did that. It would be really nice if one could do a zfs send to an USB disk for backup. Even better if you could form a USB based RAIDZ w/ 3 TB disks. Have Fun! Reg --- On Sat, 1/26/13, Jim Klimov <jimkli...@cos.ru> wrote: > Well, to be pedantic, I'd add that ashift only dictates > minimum block > size and alignment relative to the storage device provided > to ZFS - > the slice or partition. Hardware-alignment of 4kb writes > would also > need that the partition itself is aligned with 4KB sectors - > i.e. that > its starting offset is divisible by 8 (in classic 512b > sector count). > If you dedicate the disk to ZFS and it is automatically > partitioned > with GPT, then the problem is taken care of - with offset > being 256. > On MBR the default offset is 34 or so, and can present a > problem that > is solvable by manual partitioning. > > HTH, > //Jim > > _______________________________________________ > OpenIndiana-discuss mailing list > OpenIndiana-discuss@openindiana.org > http://openindiana.org/mailman/listinfo/openindiana-discuss > _______________________________________________ OpenIndiana-discuss mailing list OpenIndiana-discuss@openindiana.org http://openindiana.org/mailman/listinfo/openindiana-discuss
