After some exchanges with Linus on the upstream bug I'm un-duplicating this from #77734. That bug can deal with the kernel versions that allowed the disk I/O to be attempted. It appears the current code was introduced by:
git describe --contains a168ee84c90b39ece357da127ab388f2f64db19c v2.6.25-rc1~1160 where __generic_make_request() calls bio_check_eod() which will generate the warning in handle_bad_sector(). As this commit refactored the block code significantly I'm not sure at this point if there was similar protection in earlier code. This bug can deal with limiting the warning messages. Neil Brown (upstream) believes this may be fixed by commit ac0d86f5809598ddcd6bfa0ea8245ccc910e9eac: git describe --contains ac0d86f5809598ddcd6bfa0ea8245ccc910e9eac v2.6.28-rc1~347 and therefore will be included in Jaunty. Neil says: "It is certainly a problem that I have seen before. mdadm destroy all partitions in a device that it includes in an array to try to stop other code getting confused. Presumably dmraid doesn't. But from .28 it probably shouldn't need to." It may be, if we can show this patch can resolve the issue, that it might be a candidate for an SRU back-port. Could one of the affected users do a test with Jaunty (kernel 2.6.28) and attach the resulting /var/log/kern.log to this report for us to examine? -- dmraid & attempt to access beyond end of device https://bugs.launchpad.net/bugs/329880 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
