fsck.vfat hangs after renaming to FSCK9999.REN
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dosfstools (Ubuntu) |
Fix Released
|
Medium
|
Onno Benschop |
Bug Description
Binary package hint: dosfstools
Running fsck -a /dev/sda1 on a vfat external USB disk with a personality disorder, fsck.vfat hangs after renaming file #9999 to FSCK9999.REN and uses all free CPU time - from top(1):
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
8554 root 25 0 128m 127m 380 R 91.1 12.6 223:23.54 fsck.vfat
It is obviously trying to rename to FSCK(9999+1).REN which doesn't work.
The man page claims that fsck.vfat cvan fix "Directories with a large number of bad entries (probably corrupt). The directory can be dropped.". It would be nice to be able to specify which directory should be dropped as the filesystem crashes when trying rm -rf on this directory. Now fsck crashes too :(
Changed in dosfstools: | |
status: | Fix Committed → Fix Released |
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