|To:||Stephen Lord <lord@xxxxxxx>|
|Subject:||Re: du vs. df inconsistency|
|From:||Jameel Akari <jakari@xxxxxxxxxxx>|
|Date:||Fri, 4 Feb 2005 11:26:08 -0500 (EST)|
|Cc:||Eric Sandeen <sandeen@xxxxxxx>, linux-xfs@xxxxxxxxxxx|
|References:||<Pine.OSF.firstname.lastname@example.org> <4202D839.email@example.com> <Pine.OSF.firstname.lastname@example.org> <Pine.OSF.email@example.com> <42039EBD.firstname.lastname@example.org>|
Feb 4 10:54:01 alb-ndm kernel: VFS: Busy inodes after unmount. Self-destruct in 5 seconds. Have a nice day...
That's what I figured. I'll definitely move this to the top of "reasons to upgrade already!" pile. (I'd do it tomorrow if there were some XFS-patched RHEL kernels ready to go... ;)
If you reboot and run repair you should be ok.
I found some mention of this on the mailing list where it was suggested to `mount -o nouuid`. This worked for me - the filesystem recovered itself, and I see the freed space now.
Those unlinked bucket messages refer to unlinked inodes which should have been freed at some point. They probably still have a reference count inside xfs which means they did not get freed. This is where your space has gone.
Well, now I know more about XFS internals than I did before. Always has to learned the hard way...
Thanks for your replies.
-- #!/jameel/akari sleep 4800; make clean && make breakfast
|<Prev in Thread]||Current Thread||[Next in Thread>|