Bug 570952

Summary: dosfsck crashes while checking SD card.
Product: [Fedora] Fedora Reporter: Mark van Rossum <mvanross>
Component: dosfstoolsAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jskarvad
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 09:01:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Mark van Rossum 2010-03-05 22:45:24 UTC
Description of problem:
I have a  SD card with some faulty files, shown under /dev/mmcblk0p1 in my build-in cardreader, that I like to check.

This runs fine:
 fsck.vfat   /dev/mmcblk0p1
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
Reclaimed 2275 unused clusters (74547200 bytes).
Leaving file system unchanged.
/dev/mmcblk0p1: 545 files, 59447/61980 clusters

But with the -a option

fsck.vfat -a  /dev/mmcblk0p1
dosfsck 3.0.1, 23 Nov 2008, FAT32, LFN
*** buffer overflow detected ***: fsck.vfat terminated
======= Backtrace: =========
/lib/libc.so.6(__fortify_fail+0x4d)[0x5351ed]
/lib/libc.so.6[0x53330a]
/lib/libc.so.6[0x532a38]
/lib/libc.so.6(_IO_default_xsputn+0xb6)[0x4adbd6]
/lib/libc.so.6(_IO_vfprintf+0x1007)[0x481217]
/lib/libc.so.6(__vsprintf_chk+0xa7)[0x532ae7]
/lib/libc.so.6(__sprintf_chk+0x2d)[0x532a2d]
fsck.vfat[0x804cffe]
fsck.vfat[0x804e0b0]
fsck.vfat[0x804907f]
/lib/libc.so.6(__libc_start_main+0xe6)[0x457bb6]
fsck.vfat[0x8048b01]
======= Memory map: ========
003f8000-003f9000 r-xp 00000000 00:00 0          [vdso]
0041f000-0043d000 r-xp 00000000 08:03 375448     /lib/ld-2.11.1.so
0043d000-0043e000 r--p 0001d000 08:03 375448     /lib/ld-2.11.1.so
0043e000-0043f000 rw-p 0001e000 08:03 375448     /lib/ld-2.11.1.so
00441000-005b0000 r-xp 00000000 08:03 375450     /lib/libc-2.11.1.so
005b0000-005b2000 r--p 0016e000 08:03 375450     /lib/libc-2.11.1.so
005b2000-005b3000 rw-p 00170000 08:03 375450     /lib/libc-2.11.1.so
005b3000-005b6000 rw-p 00000000 00:00 0 
00927000-00944000 r-xp 00000000 08:03 376815     /lib/libgcc_s-4.4.3-20100127.so.1
00944000-00945000 rw-p 0001c000 08:03 376815     /lib/libgcc_s-4.4.3-20100127.so.1
08047000-08054000 r-xp 00000000 08:03 458133     /sbin/dosfsck
08054000-08055000 rw-p 0000c000 08:03 458133     /sbin/dosfsck
08055000-08057000 rw-p 00000000 00:00 0 
09181000-091c0000 rw-p 00000000 00:00 0          [heap]
b75f9000-b76ed000 rw-p 00000000 00:00 0 
b7715000-b7717000 rw-p 00000000 00:00 0 
bf97f000-bf994000 rw-p 00000000 00:00 0          [stack]
Aborted

Works fine on another card.


Version-Release number of selected component (if applicable):


How reproducible:
Always, with this card.

Additional info:

The partition table of this device is empty, or least not recognized.
This seems to be common on these SD cards.

parted  /dev/mmcblk0p1
GNU Parted 1.9.0
Using /dev/mmcblk0p1
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) p                                                                
Model: Unknown (unknown)
Disk /dev/mmcblk0p1: 2031MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start  End  Size  Type  File system  Flags

(parted).

Comment 1 Jaroslav Škarvada 2010-03-15 16:01:42 UTC
Currently there is dosfstools-3.0.9-2.fc14 in rawhide with many bug fixes. Please check if the problem persists.

Comment 2 Mark van Rossum 2010-07-25 20:59:34 UTC
Sorry I reformatted the card, and have had no opportunity to check the same situation again.

Comment 3 Jaroslav Škarvada 2010-07-26 07:15:55 UTC
Many problems were fixed by new version bump, maybe also your specific issue. I am unable to reproduce this. If you don't mind I am going to close this as INSUFFICIENT_DATA.

Comment 4 Bug Zapper 2010-11-03 20:42:15 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Jaroslav Škarvada 2010-11-08 09:01:59 UTC
I am unable to reproduce it. If the problem persists, feel free to reopen.