But also makes it not work for odd number of sectors which is much worse IMHO.
Also it is far more surprising to find that the last sector is lost
silently than to have a difference in behaviour, incorrect behaviour needs
to be corrected not kept for backwards compatibility till the end of time.
And the sooner that happens, the better. Both people and utilities will get
used to it. Due to that 1024, mkntfs has to mark the disk dirty because it
can never be sure just how many sectors there really are and hence can't be
sure whether the backup boot sector was written to the correct place or not...
Also, the loop device is currently not consistent with the rest of the kernel:
* kernel physical block device: get_nr_sectors_sys_call returns the real
number of 512 byte sectors
* file mounted on loop device: sam sys_call returns the number of sectors & ~1.
This difference in behaviour causes a much bigger surprise than anything
else if we are talking about surprises!
Best regards,
Anton
-- "Nothing succeeds like success." - Alexandre Dumas-- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Linux NTFS Maintainer / WWW: http://sf.net/projects/linux-ntfs/ ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/