fsck.vfat hangs, eats CPU on problematic file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dosfstools (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I'm using the Dapper release candidate that was released around 25 May 2006. During the boot process, the fsck of one of my Windows partitions hung indefinitely each time I booted. The error was always the same:
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
/15-sept-
File size is 0 bytes, cluster chain length is > 0 bytes.
Truncating file to 0 bytes.
I could always get past this by ctrl-C during the boot process (and then ctrl-D to continue booting).
Once booted, I did the fsck.vfat in a terminal and watch the CPU monitor. The CPU is pegged when I run this.
I deleted that file. Now when I run fsck.vfat, no problem at all. The entire check completes in several seconds.
So I'm passed the problem for now, but a few note:
This problem never occured to me under Breezy (and I was using the same vfat filesystems under Breezy.) So it's a pretty serious regression.
Hi, thank you for your bug report.
We've just been trying to reproduce this bug, but couldn't. Is there anything you can tell us about your computer that might give more information. For example:
* Was a specific file, or group of files, involved?
* What names did affected files have?
* Were they all in the same directory, what was the name of that directory?
* How big was the partition that contained the files?
* Which language was the file system?
* Was the file of a particular size?
* Was the file a Windows .lnk file?
* What other symptoms did you notice?
We realise that we're asking lots of questions, but the bug you reported has potentially been identified as being part of a problem tucked away in the internal workings of the operating system and if that is the case, it may affect many users.
Thanks,
Stefan and Onno