On 06/11/2010 05:16 PM, James Bottomley wrote:
So best guess is that CONFIG_LBDAF isn't set. This would make all sector_t counts wrap at 2TB (32 bits worth of 512 bytes). It would be rather a daft thing for a distribution not to have set, though ...
Bingo, thanks. It doesn't seem to be set on this machine running the amd64 2.6.32 lucid build which also appears to suffer the same problem. If this config option isn't set though, shouldn't the kernel fail calls like llseek() that try to exceed the limit, rather than silently wrap around to the wrong address?
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
