Bug 950012 - fsck.vfat 100% CPU, no read()
Summary: fsck.vfat 100% CPU, no read()
Keywords:
Status: CLOSED DUPLICATE of bug 950007
Alias: None
Product: Fedora
Classification: Fedora
Component: dosfstools
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-04-09 13:08 UTC by Harald Hoyer
Modified: 2013-05-03 13:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-05-03 13:36:13 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Harald Hoyer 2013-04-09 13:08:32 UTC 
Description of problem:
Trying to fsck my /dev/sda1 lets fsck.vfat consume 100% CPU without any disk reads.

strace does not show any syscalls after some read().

Version-Release number of selected component (if applicable):
dosfstools-3.0.16-2.fc19.x86_64

I dd'ed and xz'ed the partition image. Maybe you can debug fsck.vfat with that.

Dropbox link sent to jskarvad in private chat. Please only share with debuggers.
Comment 1 Felix Wiedemann 2013-05-02 18:25:16 UTC 
Same behaviour on my machine while fsck'ing EFI System Partition.

After rebuilding and installing from source rpm, with untouched spec file, dosfsck runs flawlessly -- no idea why.
Comment 2 Jaroslav Škarvada 2013-05-03 13:36:13 UTC 
(In reply to comment #1)
> Same behaviour on my machine while fsck'ing EFI System Partition.
> 
> After rebuilding and installing from source rpm, with untouched spec file,
> dosfsck runs flawlessly -- no idea why.

Confirmed, probably ABI mismatch, but closing as dupe of bug 950007.

*** This bug has been marked as a duplicate of bug 950007 ***
Note You need to log in before you can comment on or make changes to this bug.