5

rc.shutdown doesn't seem to umount the filesystems correctly

view full story
linux-howto

https://bbs.archlinux.org – The problem is that each time I shutdown/reboot, there's a message saying "Unmounting Non-API Filesystems" failed, and the next time system boots, fsck will recover journal. I looked into etc/rc.shutdown, found that it calls umount_all in etc/rc.d/functions. I made the following changes to umount_all (just add some echo to record infomation in /tmp/permanent/umount_all_log):umount_all() { # $1: restrict to fstype local mounts ( while read -r target fstype options; do echo "got: $taret $fstype $options" # match only targetted fstypes if [[ $1 && (HowTos)

missing's picture
Submitted by missing on 01/01/2012 – Made popular on 01/01/2012

Stories similar to rc.shutdown doesn't seem to umount the filesystems correctly

At boot I mount NFS drives to my NAS and it works great. However at shutdown, I noticed that it hangs on "Unmounting all filesystems" (over a minute), and intermittently would generate some sort of RPC error. It is not unimaginable for it to take long ...

autofs doesn't work 3 years 11 weeks ago

I'm trying to mount my local hard disk automatically with autofs ... I have modified the files auto.master and auto.misc in accordance with the instructions and restarted the autofs, but nothing changes ...

see below the modified auto.master and auto.misc: /etc/auto.master

Code: # # Sample auto.master file

Ok, I've made my first backup script to be run as a cron job. It tars three directories: /etc -> /media/Storage/backup/etc.tar.bz2 /root -> /media/Storage/backup/home/root.tar.bz2 /home/matthew -> /media/Storage/backup/home/matthew.tar.bz2

etc.tar.bz2 and root.tar.bz2 come out ok, but matthew.tar.bz2 does not. it isn't corrupted, it

As I said above "Thith doth driveth me nutth."Before I left three weeks ago shutdown was working.  So I come back and read pubby's post.  I next upgraded so my system would be current.Sure enough the bad penny returns.  If I select "shutdown" on the Xfce GUI menu, my system appears to shutdown but the power never turns off.  In effect what I get is a re

I seem to have found a suspect via dmesg here it goes, I've highlighted the relevant section[ 1441.563262] INFO: task shutdown:1011 blocked for more than 120 seconds.[ 1441.563264] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.[ 1441.563262] INFO: task shutdown:1011 blocked for more than 120 seconds. [ 1441.563264] "echo 0 > /proc/sys/kernel/hun

Hi,friends

I vividly remember the beep in 9.04 when I shutdown the computer

sudo shutdown -h now

and I will hear a "DI"/"Bee" sound

sudo shutdown -h +5

and I will hear 5 beeps every minute till it is power off

The beep is a great warning for me and I really need this feature

systemd-fsck boot message 30 weeks 3 days ago

fsck stands for "file system check" [1].  systemd will check all of your filesystems every time you boot [2].  systemd-fsck[145]: /dev/sda4: clean, 2977/296096 files, 85427/1217024 blocks systemd-fsck[151]: /dev/sda1: clean, 345/26104 files, 34083/104388 blocks (check after next mount)These messages mean that there are no problems with your filesystems and they are "clean&

shutdown slowly 10 weeks 3 days ago

Any difference if you use KDE shutdown dialog, or use "sudo shutdown -h now" ?Are bundles unmounting cleanly?  Tried stopping bundles and running "cb-clean-lopps" before shutting down?

I don't mean to wield the Grammar Hammer here, but something that's been irking me on shutdown is a message that says "Shutting down, please standby" after you hit the "shutdown" button.On this side of the Atlantic, and maybe in Britain it's different, we'd say "please stand by" -- two words -- meaning to wait, as opposed to being on "standby,