On Wed, Dec 09, 2009 at 11:17:38PM +0100, Penguin Lover Frank Steinmetzger squawked: > I use FAT32 on my external HDDs to make it easier to share with other people > and OSes. Never had a problem before, but now I do. Lately, when I save > videos to my disks, and play them back after the file system cache is > emptied, they have completely different content (of files that are long > deleted).
Please describe in more detail what you actually did. Did you read/write the files in linux? Both under 2.6.31? A step-by-step maybe appreciated. > > I just had the magnificent idea to look into the syslog and found loads of > "kernel: bio too big device sdb (248 > 240)" > > I heard romours of problems with the current FAT implementation due to M$. I > went back to 2.6.30 for the moment. So what???s your proposal? Usually I > don???t > have the need for ??bercurrent kernels, but would installing 2.6.32 help? Did you file a bug? Where did you hear this "rumour"? I don't see any significant changes to the VFAT driver in 2.6.31, and since (I infer from your message) that downgrading to 2.6.30 is okay, I doubt that is the issue. You are not running any sort of LVM, RAID, or encryption, are you? A similar bug seems to have occured in device mapper, where dm gave the underlying fs the wrong values for max_hw_sector. I am somehow more leaning toward the problem being in the usb subsystem. When you plug-in your device, what does /sys/block/sdb/queue/max_hw_sectors_kb say? (I'm afraid I am not actually a kernel dev... but I hope I am asking the right question so someone who actually knows what is going on can help you.) Cheers, W -- I am a nobody Nobody is perfect Therefore, I am perfect. Sortir en Pantoufles: up 1098 days, 9:14