"umount: / is busy"

[Ralf Ertzinger]

Hi.

Sometimes, after a "yum upgrade", I get a message on shutdown saying that
/ is busy and can not be unmounted, leading to a filesystem check on the
next reboot (or better: a journal replay). So far I have not been able to
figure out what exactly causes this. My first thought was that a package
used a loop mounted file system for something and forgot to umount it,
but, having unloaded the loop driver manually before reboot, this can not
be the solution.

Anyone else seeing this or having an idea?

-- 
The Thread went ACPI and couldn't resume.
          -- Florian Laws, dasr <slrnb174fi.1j8.fl-usenet(a)void.s.bawue.de&gt;

[Florin Andrei]

On Mon, 2005-08-08 at 02:44 +0200, Ralf Ertzinger wrote:
>  
>  Sometimes, after a "yum upgrade", I get a message on shutdown saying that
>  / is busy and can not be unmounted, leading to a filesystem check on the
>  next reboot (or better: a journal replay). So far I have not been able to
>  figure out what exactly causes this. 
I noticed that it seems to always happen when upgrading glibc, but
perhaps other packages too can trigger it.

It is the reason why I pretty much always do "sync" before "reboot",
"halt" or "poweroff".
It would be nice if "sync" was included in the system scripts, right
before doing umount.

-- 
Florin Andrei

http://florin.myip.org/

[Ralf Ertzinger]

Hi.

Florin Andrei <florin(a)andrei.myip.org&gt; wrote:

>  It is the reason why I pretty much always do "sync" before
> "reboot",
>  "halt" or "poweroff".
>  It would be nice if "sync" was included in the system scripts, right
>  before doing umount. 
I was under the impression that umounting a partition means that
sync is called implicitly. You have to free your dirty buffers before
removing the medium...


-- 
Angie chalks another Blue, mother smiles, she did it too...
		-- Marillion, "Garden Party"

[Russell Coker]

On Monday 08 August 2005 16:21, Florin Andrei <florin(a)andrei.myip.org&gt; wrote:
>  On Mon, 2005-08-08 at 02:44 +0200, Ralf Ertzinger wrote:
>  > Sometimes, after a "yum upgrade", I get a message on shutdown saying that
>  > / is busy and can not be unmounted, leading to a filesystem check on the
>  > next reboot (or better: a journal replay). So far I have not been able to
>  > figure out what exactly causes this.
>
>  I noticed that it seems to always happen when upgrading glibc, but
>  perhaps other packages too can trigger it.
>
>  It is the reason why I pretty much always do "sync" before "reboot",
>  "halt" or "poweroff".
>  It would be nice if "sync" was included in the system scripts, right
>  before doing umount. 
Below is the relevant section from the source of /sbin/shutdown.  halt also 
calls sync() so there's no need for scripts to do such things.

  sync();
  fprintf(stderr, "shutdown: turning off swap\r\n");
  spawn(0, "swapoff", "-a", NULL);
  fprintf(stderr, "shutdown: unmounting all file systems\r\n");
  spawn(0, "umount", "-a", NULL);

  /* We're done, halt or reboot now. */
  if (do_halt) {
        fprintf(stderr, "The system is halted. Press CTRL-ALT-DEL or turn off 
power\r\n");
        init_reboot(BMAGIC_HALT);
        exit(0);
  }
  fprintf(stderr, "Please stand by while rebooting the system.\r\n");
  init_reboot(BMAGIC_REBOOT);
  exit(0);


-- 
http://www.coker.com.au/selinux/   My NSA Security Enhanced Linux packages
http://www.coker.com.au/bonnie++/  Bonnie++ hard drive benchmark
http://www.coker.com.au/postal/    Postal SMTP/POP benchmark
http://www.coker.com.au/~russell/  My home page