Bug 52634 - mount doesn't always show the correct fs type
Summary: mount doesn't always show the correct fs type
Keywords:
Status: CLOSED DUPLICATE of bug 52299
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: mount
Version: roswell
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-27 14:57 UTC by Stephen Tweedie
Modified: 2007-04-18 16:36 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-08-28 14:07:31 UTC
Embargoed:


Attachments (Terms of Use)

Description Stephen Tweedie 2001-08-27 14:57:28 UTC
Description of Problem:

Mount usually shows the fstype in /etc/fstab, not the actual fs type from
/proc/mounts, for the root filesystem.

This is a serious problem because there is a common failure mode where
people think they have upgraded to ext3 but haven't built a new initrd, so
the root fs is actually loaded as ext2 despite "mount" claiming that it is
mounted as ext3.

Version-Release number of selected component (if applicable):
mount-2.11g-5

How Reproducible:
100%

Steps to Reproduce:
1. Convert to ext3 on root filesystem (with ext3 in /etc/fstab)
2. Boot a kernel without an initrd (so we don't have an ext3 module loaded)
   The kernel loads the root filesystem as ext2, not ext3, as expected.
3. Run "mount" to display mounted filesystems.

Actual Results:
[sct@dax] ~ $ mount
/dev/hdc1 on / type ext3 (rw,usrquota,grpquota)

but in actual fact it is an ext2 filesystem:

[sct@dax] ~ $ cat /proc/mounts 
/dev/root / ext2 rw 0 0


Expected Results:

mount should display what IS mounted, not just what it thinks OUGHT to be
mounted.

Additional Information:

Comment 1 Bernhard Rosenkraenzer 2001-08-28 14:07:24 UTC
What does your /etc/mtab say?


Comment 2 Bernhard Rosenkraenzer 2001-09-03 11:34:27 UTC

*** This bug has been marked as a duplicate of 52299 ***


Note You need to log in before you can comment on or make changes to this bug.