| Summary: | dosfstools FAT corruption with fsck on 64-bit | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | stormi-mageia, sysadmin-bugs, tmb |
| Version: | 3 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | http://freecode.com/projects/dosfstools/releases/360772 | ||
| Whiteboard: | has_procedure mga3-64-ok mga3-32-ok advisory | ||
| Source RPM: | dosfstools-3.0.16-1.mga3.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2014-01-24 03:20:57 CET
David Walser
2014-01-24 03:23:09 CET
Hardware:
i586 =>
x86_64 Testing complete mga3 64 Created some files on a vfat usb stick $ for (( i=100;i<200;i++ )) do echo "File ok" > /run/media/claire/USBSTICK/file$i; done $ cat /run/media/claire/USBSTICK/file* $ cat /run/media/claire/USBSTICK/file* | wc -l 100 Before ------ # dosfsck -vr /dev/sdd dosfsck 3.0.16 (01 Mar 2013) dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN Logical sector size (56113 bytes) is not a multiple of the physical sector size. $ cat /run/media/claire/USBSTICK/file* $ cat /run/media/claire/USBSTICK/file* | wc -l 100 After ----- # dosfsck -vr /dev/sdd dosfsck 3.0.16 (01 Mar 2013) dosfsck 3.0.16, 01 Mar 2013, FAT32, LFN Logical sector size (56113 bytes) is not a multiple of the physical sector size. $ cat /run/media/claire/USBSTICK/file* $ cat /run/media/claire/USBSTICK/file* | wc -l 100 Nothing unusual to note, before or after. Whiteboard:
(none) =>
has_procedure mga3-64-ok Trying again: is there a way to reproduce the filesystem corruption? Testing mga3 32 in progress. mga3 32 testing complete. Whiteboard:
has_procedure mga3-64-ok =>
has_procedure mga3-64-ok mga3-32-ok (In reply to Samuel VERSCHELDE from comment #3) > Trying again: is there a way to reproduce the filesystem corruption? I think in general, fsck doesn't write to a filesystem unless it thinks it needs to (other than marking it as having been checked in some cases), so it might have to already be corrupted a bit to trigger this, but I'm not sure. Advisory added Whiteboard:
has_procedure mga3-64-ok mga3-32-ok =>
has_procedure mga3-64-ok mga3-32-ok advisory Update validated and advisory in SVN. Could sysadmin please push from core/updates_testing to core/updates. Keywords:
(none) =>
validated_update Update pushed: http://advisories.mageia.org/MGAA-2014-0013.html Status:
NEW =>
RESOLVED |