Bug 754816 - wrong alias for ramdisk driver in modprobe config file (has rd, should be brd)
Summary: wrong alias for ramdisk driver in modprobe config file (has rd, should be brd)
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: module-init-tools
Version: 16
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jon Masters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-17 19:54 UTC by floyd smith
Modified: 2011-12-10 20:04 UTC (History)
6 users (show)

Fixed In Version: module-init-tools-3.16-5.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-10 20:04:29 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description floyd smith 2011-11-17 19:54:00 UTC
Description of problem:

First, there are NO /dev/ram[0-9] devices upon install.

Now, MAKEDEV ram9 can be used to make say ram9 and this results in:
# ls -lZ /dev/ram9
brw-rw-rw-. root disk system_u:object_r:fixed_disk_device_t:s0 /dev/ram9

But if mkfs -t ext2 /dev/ram9 is attempted, then this results in:
mkfs.ext2: No such device or address while trying to determine filesystem size

Now, the kernel config file does not compile it statically in the kernel - instead, it sets it as a module (where as previous releases would set it to "=y").
/boot/config-3.1.1-1.fc16.x86_64
has:
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=16384

However, its module should load the first time the device is accessed.

Floyd,

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


How reproducible:
always

Steps to Reproduce:
1.use makedev to create a /dev/ram# device.
2.Try to mk a fs onto - fails.
3.
  
Actual results:
always fails

Expected results:
succeeds in fc15, 13 12 etc.

Additional info:

Comment 1 Chuck Ebbert 2011-11-22 13:28:29 UTC
It looks like we still have the old name in our configuration files. Try changing 

 alias block-major-1-* rd

to

 alias block-major-1-* brd

in /etc/modprobe.d/dist.conf. That should make it auto-load. You can also change the default config options by adding a line to some file in /etc/modprobe.d like this:

options brd rd_nr=X rd_size=Y max_part=Z

where X is the number of ramdisks you want, Y is their size, and Z is the maximum partitions per disk.

Comment 2 Chuck Ebbert 2011-11-29 01:41:37 UTC
Did those suggestions work?

Comment 3 floyd smith 2011-11-29 05:22:21 UTC
(In reply to comment #2)
> Did those suggestions work?

Yes, the first was tried, and it worked. Thanks very much.

Floyd,

Comment 4 Jon Masters 2011-11-29 17:27:39 UTC
Changing to correct email address. Apologies for the delay.

Comment 5 Fedora Update System 2011-11-29 18:01:40 UTC
module-init-tools-3.16-4.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/module-init-tools-3.16-4.fc16

Comment 6 Fedora Update System 2011-11-30 02:02:24 UTC
Package module-init-tools-3.16-4.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing module-init-tools-3.16-4.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16616/module-init-tools-3.16-4.fc16
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2011-12-03 01:05:29 UTC
module-init-tools-3.16-5.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/module-init-tools-3.16-5.fc16

Comment 8 Fedora Update System 2011-12-10 20:04:29 UTC
module-init-tools-3.16-5.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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