On Tue, Jan 18, 2005 at 06:45:26AM -0200, Marcelo Tosatti wrote: > 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. > What would be the correct fix for this for this, if any?
Well, I personally think at least the EOF behaviour should be fixed somehow. I understand the point that the device's blocksize affects the device's length... obviously a block device can only consist of full blocks, not half a block or something like that. However, if that's right, a block device's length should IMHO also be affected by it's blocksize - thus, the block device should return an EOF after the last block was read. In my case this would mean, it should return an EOF if blocksize is 1024 and 4996183 blocks (9992366 sectors) are read or better, if the 4996184th block is attempted to read and it should return an EOF if blocksize is 4096 and 1249045 blocks (9992360 sectors) are read or better, if the 1249046th block is attempted to read. Another approach could be to allow 'fractions of blocks' :) Then, the device could have a blocksize of 4096 and consist of 1249045 full blocks and a 6/8 block. However, I'm not sure, if this is possible at all. > v2.6 should suffer from the same issues? I don't know, but if it doesn't, one could just backport 2.6's solution :) Mario -- Independence Day: Fortunately, the alien computer operating system works just fine with the laptop. This proves an important point which Apple enthusiasts have known for years. While the evil empire of Microsoft may dominate the computers of Earth people, more advanced life forms clearly prefer Mac's. - 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/
