Bug 70526

Summary:	incorrect detection of filesystem type on diskette
Product:	[Retired] Red Hat Linux	Reporter:	Richard Keech <rkeech>
Component:	e2fsprogs	Assignee:	Thomas Woerner <twoerner>
Status:	CLOSED NOTABUG	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	nobody
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-10-07 13:47:42 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 Richard Keech 2002-08-02 05:21:56 UTC

Description of Problem:

It is possible to have a the filesystem type of a diskette
be detected as vfat when the last filesystem put on the 
diskette was ext2. 


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

mount-2.11n-12.7.3, kernel-2.4.18-5


How Reproducible:

every time.


Steps to Reproduce:

1. mformat a:

2. mke2fs /dev/fd0

3. mount /mnt/floppy


Actual Results:

floppy mounted as vfat.


Expected Results:

floppy mounted as ext2.


Additional Information:

Comment 1 Elliot Lee 2002-08-07 21:03:52 UTC

The problem is that e2fsprogs doesn't zero out the first block of the device in mke2fs, 
leaving the FAT info there, and mount happens to check for FAT before ext2. It seems that 
the right place to fix it is in e2fsprogs, because leaving the magic stuff there can cause 
problems for other filesystems as well.

Comment 2 Florian La Roche 2002-08-21 19:26:47 UTC

I think this block is kept as it on purpose to leave bootup support in
place.

greetings,

Florian La Roche