> But I really don't know why mkreiserfs is creating a filesystem > with 64k more than allowed by the device... maybe a bug in mkreiserfs? > > The strange is that it didn't happen with the OLD IDE > drivers... could it be a pata_via bug? pata_via doesn't deal with disk sizes. That is handled by the core libata code (and on the whole by the scsi midlayer) Once you've created a raid volume the sizing is however handled by the raid code not by the underlying code at all so it suggests a bug (or some kind of shared misbehaviour) in the various mk* tools. However I've no idea what that should suddenly show up now, and not with every scsi user. > And it seems that mdadm's method to determine the size of the > partition is different from mkreiserfs/mke2fs etc, right? You would need to ask someone familiar with those applications or take a look at the source. - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
