Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 57253 - kernel 2.4.26-gentoo-r5 & 2.6.7-gentoo-r11 fail to "mount -o remount,ro /" in /etc/init.d/halt.sh
Summary: kernel 2.4.26-gentoo-r5 & 2.6.7-gentoo-r11 fail to "mount -o remount,ro /" in...
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-15 21:35 UTC by Gregory P. Smith
Modified: 2004-09-26 07:02 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
workaround patch for halt.sh (halt.sh.no-remount-ro-nfsroot.patch,860 bytes, patch)
2004-07-15 21:37 UTC, Gregory P. Smith
Details | Diff
2.4.26-gentoo-r5 .config that exhibits the problem (config-2.4.26-gentoo-r5,30.13 KB, text/plain)
2004-07-16 23:49 UTC, Gregory P. Smith
Details
2.6.7-gentoo-r11 .config that exhibits the problem (config-2.6.7-gentoo-r11,29.93 KB, text/plain)
2004-07-16 23:50 UTC, Gregory P. Smith
Details
vanilla 2.4.26 .config that does NOT exhibit the problem (config-vanilla-2.4.26,21.41 KB, text/plain)
2004-07-16 23:50 UTC, Gregory P. Smith
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregory P. Smith 2004-07-15 21:35:45 UTC
/etc/init.d/halt.sh includes a step to remount all filesystems read only before shutting down or rebooting.  On kernel 2.4.25-gentoo and all earlier kernels that I have used (2.4.22-gentoo and various others) this worked fine.  Upgrading to 2.4.26-gentoo-r3 (and r5) this step fails.  the remount causes / to be inaccessable so the script cannot access what it needs to finish the shutdown.

While this is a kernel bug I'll attach a patch to halt.sh that works around it.

Reproducible: Always
Steps to Reproduce:
1. use the stated kernel with nfsroot (maybe any nfs, i haven't tried)
2. remount nfsroot / as ro
3. enjoy your hosed system
Comment 1 Gregory P. Smith 2004-07-15 21:37:37 UTC
Created attachment 35523 [details, diff]
workaround patch for halt.sh
Comment 2 Tim Yamin (RETIRED) gentoo-dev 2004-07-16 09:47:21 UTC
Could you please try vanilla-sources-2.4.26 to see if we can isolate this to a patch in the gentoo-sources patchset? Thanks...
Comment 3 Gregory P. Smith 2004-07-16 23:48:28 UTC
Okay, i've tried a few kernels now for the halt.sh nfsroot remount,ro problem:

2.4.26-vanilla:          does NOT have the problem
2.4.26-gentoo-r3 & r5:   has the problem
2.6.7-gentoo-r11:        has the problem

i'll attach my .config files for each kernel
Comment 4 Gregory P. Smith 2004-07-16 23:49:28 UTC
Created attachment 35619 [details]
2.4.26-gentoo-r5 .config that exhibits the problem
Comment 5 Gregory P. Smith 2004-07-16 23:50:02 UTC
Created attachment 35620 [details]
2.6.7-gentoo-r11 .config that exhibits the problem
Comment 6 Gregory P. Smith 2004-07-16 23:50:46 UTC
Created attachment 35621 [details]
vanilla 2.4.26 .config that does NOT exhibit the problem
Comment 7 Tim Yamin (RETIRED) gentoo-dev 2004-07-17 03:18:14 UTC
Can you try a similar 2.4 .config on both kernels - there are quite a few =Y <> =M changes between the two which might be causing somehow. But since you're getting this on gentoo-dev-sources too; I suspect this might be due to supermount. Can you please try: UNIPATCH_EXCLUDE="02-02.superMount.1.2.11a.patch" emerge gentoo-sources and see how that goes? Thanks...
Comment 8 Aron Griffis (RETIRED) gentoo-dev 2004-08-01 16:51:11 UTC
Greg, are you able to do the test requested by Tim?  Since it's really a kernel problem I'm really hesitant to apply any patches to halt.sh to workaround
Comment 9 Gregory P. Smith 2004-08-01 16:57:48 UTC
sorry, i haven't had a chance to build a new kernel yet.  i suspect its a supermount bug/issue as that makes the most sense.  i'll follow up once i build a new kernel w/o supermount.
Comment 10 Daniel Drake (RETIRED) gentoo-dev 2004-09-26 07:02:38 UTC
Bump... please try a new and clean kernel (no supermount), and reopen this bug if the issue still exists.