Bug 158579 - Multiple entries for /dev/shm in /etc/fstab
Multiple entries for /dev/shm in /etc/fstab
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: MAKEDEV (Show other bugs)
3.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Chris Lumens
Brock Organ
RHEL3U7NAK
:
Depends On:
Blocks: 190430 205158
  Show dependency treegraph
 
Reported: 2005-05-23 15:18 EDT by David Milburn
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-07-10 10:42:58 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David Milburn 2005-05-23 15:18:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
When /etc/fstab has an entry for /dev/shm mount point
that mounts a ramfs instead of a tmpfs, an upgrade from
dev-3.3.12-1 to dev-3.3.12.3-1 will generate another
/etc/fstab entry for /dev/shm with a filesystem type
of tmpfs. 

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

How reproducible:
Always

Steps to Reproduce:
1. Change /dev/shm entry in /etc/fstab to mount ramfs instead of tmpfs.
2. Upgrade to dev-3.3.12.3-1
3. Cat /etc/fstab
  

Actual Results:  Two entries for /dev/shm

none /dev/shm tmpfs defaults 0 0
none /dev/shm ramfs defaults 0 0

Expected Results:  One entry for /dev/shm

none /dev/shm ramfs defaults 0 0


Additional info:
Comment 1 Nalin Dahyabhai 2005-07-21 18:00:04 EDT
The kernel's tmpfs.txt file doesn't mention that ramfs can be used here
(personally, I don't know why you'd want to), but it's still a bug in the %post
script.  Fixing in 3.3.12.4-1.
Comment 12 Chris Lumens 2007-07-10 10:42:58 EDT
Closing as WONTFIX based on comment #11.

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