"umount: / is busy"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx>

-- 
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
http://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux