In article <[EMAIL PROTECTED]>,
David Baron <[EMAIL PROTECTED]> wrote:
>Several posters, including myself, have cited problems umounting the file
>systems on shutdown with recent 2.6.8 kernels. This may be caused by timing
>problems leaving the file systems busy. I got rid of the error messages and
>got almost all clean file systems on restart by using umount -l ("lazy
>umount") and a sleep to let things settle down.
>
>One of the file systems is ALWAYS recovering its journal on restart (mounts
>to /usr/share). It is found clean and everything is OK, but ...
>
>I tried a sync before umount. Did not help. In the umountfs script, it might
>be too late since all processes have been killed off. The journal service for
>each FS is a process, is it not?
No.
>So I put the sync, followed by a sleep, in
>the script before the killall's. Did not help there either.
>
>Any other ideas?
Yes, try to put a "fuser -vm /usr/share; sleep 10" in the script,
after the killalls. That will perhaps tell you what is keeping
the mountpoint busy.
Mike.
--
"In times of universal deceit, telling the truth becomes
a revolutionary act." -- George Orwell.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
