On Tue, Jan 18, 2005 at 01:37:08PM +0100, Andries Brouwer wrote: > On Tue, Jan 18, 2005 at 06:45:26AM -0200, Marcelo Tosatti wrote: > > > > I suppose that what happens is the following: > > > mounting sets the blocksize to 4096. > > > After reading 9992360 sectors, reading the next block means reading > > > the next 8 sectors and that fails because only 6 sectors are left. > > > > So this is either not a Linux error and not a disk error, its just that the > > "use with filesystem" then "direct access" is a unfortunate combination. > > It is not a disk error, but I consider it a Linux error.
OK. > > What would be the correct fix for this for this, if any? > > For 2.4 my reaction would be to say that it is a known property > of the system, possibly less fortunate, an unimportant flaw. This seems to be harmless, so, better do nothing about it. > Of course a fix is possible if this is deemed important for some reason. > > > v2.6 should suffer from the same issues? > > I don't think so. But 2.6 details are rather different. OK! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
