From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1)
Description of problem:
After creating and mounting a RAM disk you can store files on it.
After unmounting and then mounting the RAM disk again these files are
gone. This used to work in other distributions and kernel versions.
Note: the fact that this does not work in itself is not a problem
since you should not use RAM disks for this but use shmfs instead. But
I've got the feeling that this a more fundamental bug somewhere in the
filesystem code, instead of a RAM disk bug. Hence the report.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
dd if=/dev/zero of=/dev/ram0 bs=1024k count=4
(Note - the RAM disk is now 16 MB instead of 4 MB. Strange...)
mount /dev/ram0 /mnt/ramdisk
df (confirms that the FS size is 16 MB)
cp /etc/passwd /mnt/ramdisk/passwd
cat /mnt/ramdisk/passwd (no problem)
mount /dev/ram0 /mnt/ramdisk (no problem so the filesystem info
is still there!)
cat /mnt/ramdisk/passwd (no such file or directory!)
1. Filesystem is 16 MB
2. /mnt/ramdisk/passwd: no such file or directory
1. Filesystem size should have been the size of the ramdisk - 4 MB
2. File should be there and viewable
This has always worked on 2.4 kernels and earlier. Does not work under
the default FC2 kernel, and the problem has been confirmed under
vanilla 2.6.6 as well.
*** Bug 124905 has been marked as a duplicate of this bug. ***
> dd if=/dev/zero of=/dev/ram0 bs=1024k count=4
>1. Filesystem size should have been the size of the ramdisk - 4 MB
Note that you merely blanked 4MB, the size of the ramdisk is fixed
(boot time option and/or compile time I think); ie, try the same with
/dev/hda, would you expect that hda became 4MB?
So I think expectation no.1 is wrong and observed behavior is right
(pass block size to mke2fs to get a 4MB fs)
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.