FS#25149 - [initscripts] /dev/sda3, sometimes sda4, busy during shutdown
Attached to Project:
Arch Linux
Opened by RMS (TechnicalRah) - Sunday, 17 July 2011, 18:22 GMT
Last edited by Tom Gundersen (tomegun) - Sunday, 06 November 2011, 01:14 GMT
Opened by RMS (TechnicalRah) - Sunday, 17 July 2011, 18:22 GMT
Last edited by Tom Gundersen (tomegun) - Sunday, 06 November 2011, 01:14 GMT
|
Details
Description:
Following an update to the initscripts package, every time my system shuts down, now, the shutdown script reports that /dev/sda3 is busy and will be remounted read-only. This happens directly after killing all processes and, momentarily after receiving the message about the partition being busy the system powers off, so I cannot bring up a shell to check what's happening. Here's some info: * I have confirmed this to happen on 3 clean installations, as of first reboot after booting from HDD. * Issue has been confirmed with EFI and MBR partitions. * I have 8 partitions on my HDD, in order: /, /usr, /usr/local, /opt, /var, /tmp, swap, /home. * Issue has also happened with the above partition scheme plus an additional /boot partition. With the added /boot partition, /dev/sda4 becomes affected. * I have checked all system logs under /var but find no errors relating to halt. * Partitions are listed in order as above in fstab, so I am certain that /usr isn't trying to unmount before /usr/local. * There are no mounting errors on boot. * Issue happens whether I'm rebooting or halting. * I have run a read-write sector scan of my HDD with Spinrite and all sectors are clean. * I have not confirmed whether this happens on single partition installations. Additional info: * package version(s): 2011.06.4-1 Steps to reproduce: * Install Arch Linux. * Reboot/halt system following initial HDD boot, and any subsequent boot. |
This task depends upon
Closed by Tom Gundersen (tomegun)
Sunday, 06 November 2011, 01:14 GMT
Reason for closing: Works for me
Additional comments about closing: If this can be reproduced without a separate /usr and with initscripts from testing, please open a new report.
Sunday, 06 November 2011, 01:14 GMT
Reason for closing: Works for me
Additional comments about closing: If this can be reproduced without a separate /usr and with initscripts from testing, please open a new report.
Could you possibly try if this is also a problem if /usr and /usr/local are on the root partition? (Having /usr on a separate partition is known to cause problems).
tomegun: I have attached my fstab for you. Sure, I can try a single partition set-up, no problem; I'll keep you posted.
I also tried changing the verbosity level in rc.conf to 10, but that didn't yield anything on shutdown.
I don't think it's the partition scheme that's causing the problem as I have always had this scheme on any distro that I've used, including Arch; I've been using Arch daily for approx 4 years now. That said, I'm still not sure where the problem lies precisely as the rc.shutdown script is only running the standard umount command.
The mind boggles...
(By the way: the meaning of DAEMON_LOCALE="yes" is that your LOCALE variable is passed to the daemons. If you set it to "no", we unset LOCALE before starting daemons.)
If anyone can figure out exactly what happens I'd be happy to hear it. My suspicion is that this is something we cannot fix, and that we should officially stop pretending that we support a separate /usr, but I'd like to know for sure.
# strace -e trace=file mount -a
...
open("/usr/lib/locale/locale-archive", O_RDONLY) = 3
So it looks like even "mount" accesses locale-archive. This could be worked around by unsetting the locale in rc.shutdown, but knowing the number of other problems caused by using a separate /usr, I don't think this is worth it.
If someone is motivated to do this, I guess one option could be to support mounting and unmounting /usr in the mkinitramfs.