Bug 81042
Summary: | ramfs broken on kernel 2.4.18-14 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Tim Russell <timruss> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 | CC: | dombek, kar, michael, timruss |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-05 13:46:56 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
Tim Russell
2003-01-03 18:31:51 UTC
I'm not sure if there were any relevant changes but have you looked into the latest errata kernel for Red Hat Linux 8.0? (2.4.18-19.8.0) Haven't actually tried out the newer kernel, but I downloaded the source from both 2.4.18-14 and 2.4.18-19 and fs/ramfs/inode.c are exactly the same. FYI, I "updated" this system in-place to the 2.4.7-10 kernel from RH 7.2 and everything works perfectly, so this isn't wierdness with anything else in 8.0 besides the kernel. So RedHat 8.0 with a 7.2 kernel works perfect. Something got broken in ramfs after 7.2. Well, apparently I'm not going to get a response on this, even though it was Red Hat who accepted Alan Cox's ramfs patch that caused this mess. I switched the system over to tmpfs and it's working fine with 2.4.18-19. Arjan is an extremely busy person - I'm sure if you would have simply "pinged" him via this bug, or simply sent him a courteous request email - he would have eventually replied. Arjan has been helpful to me, personally, off to the side. Tested a SuSe 7.3, 2.4.16 Kernel and RAMFS worked without incident. So when is RedHat going to finally do anything about this bug? The problem has been verified on 7.3 and 8.0 so far. I don't have a 9.0 install to test with. this condition also exists for kernel versions: Linux 107.back 2.4.18-18.7.xbigmem #1 SMP Wed Nov 13 18:24:15 EST 2002 i686 unknown AND Linux dannon 2.4.18-26.7.xbigmem #1 SMP Mon Feb 24 09:18:30 EST 2003 i686 unknown mkdir /tmp/ramfs mount -t ramfs -o none /dev/ram1 /tmp/ramfs -o maxsize=128000 cp /home0/aalexand/tmp/rpt_104_16_track.dat /tmp/ramfs/ df -h /tmp/ramfs /dev/ram1 125M 33M 92M 26% /tmp/ramfs rm /tmp/ramfs/rpt_104_16_track.dat df -h /tmp/ramfs /dev/ram1 125M 33M 92M 26% /tmp/ramfs ls /tmp/ramfs directory empty We are using tmpfs as a substitute for ramfs, but are unpleased with its performance under load. We are also looking into ramdisk, but are having performance issues with ramdisks as large as we are hoping to use (>=512MB). Please let me know if there is a patch being developed to fix ramfs or if there is a workaround in place. kar aim: thequeen232323 rm Later Red Hat dropped those changes as do the errata kernels. |