Bug 756801

Summary: syslinux creates filesystem that fsck.vfat consider so bad that it won't fix
Product: [Fedora] Fedora Reporter: Mads Kiilerich <mads>
Component: syslinuxAssignee: Peter Jones <pjones>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: mads, michele, pjones
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 08:48:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mads Kiilerich 2011-11-24 16:16:03 UTC
With sdb on a USB stick I see:

# parted --script /dev/sdb mklabel msdos mkpart primary fat32 2048s 100% set 1 boot on

# mkdosfs /dev/sdb1
mkdosfs 3.0.12 (29 Oct 2011)

# fsck.vfat -rvw /dev/sdb1
dosfsck 3.0.12 (29 Oct 2011)
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
Checking we can access the last sector of the filesystem
Boot sector contents:
System ID "mkdosfs"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
      4096 bytes per cluster
        32 reserved sectors
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
   3903488 bytes per FAT (= 7624 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 7823360 (sector 15280)
    975242 data clusters (3994591232 bytes)
62 sectors/track, 124 heads
         0 hidden sectors
   7817216 sectors total
Checking for unused clusters.
Checking free cluster summary.
/dev/sdb1: 0 files, 1/975242 clusters

# syslinux /dev/sdb1

# fsck.vfat -rw /dev/sdb1
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  3:53/6d, 4:59/6b, 5:53/64, 6:4c/6f, 7:49/73, 8:4e/66, 9:55/73, 10:58/00
...
  , 466:72/00, 467:72/00, 468:6f/00, 469:72/00, 470:0d/00, 471:0a/00
1) Copy original to backup
2) Copy backup to original
3) No action
? 1
Perform changes ? (y/n) y
/dev/sdb1: 1 files, 9/975242 clusters

# fsck.vfat -rw /dev/sdb1
dosfsck 3.0.12, 29 Oct 2011, FAT32, LFN
/dev/sdb1: 1 files, 9/975242 clusters


Assuming fsck is right I would expect syslinux to update the boot sector backup too.


syslinux-4.02-5.fc16.x86_64
dosfstools-3.0.12-1.fc16.x86_64

Comment 1 Mads Kiilerich 2012-10-01 16:36:28 UTC
same with syslinux-4.05-1.fc17.x86_64

Comment 2 Fedora End Of Life 2013-07-04 02:36:13 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. 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 '17'.

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 17'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 17 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, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

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.

Comment 3 Fedora End Of Life 2013-08-01 08:49:02 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.