Jameel Akari wrote:
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
or too many mounted file systems
Oh, and these wonderful kernel messages:
Feb 4 10:54:01 alb-ndm kernel: xfs_unmount: xfs_ibusy says error/16
Feb 4 10:54:01 alb-ndm kernel: XFS unmount got error 16
Feb 4 10:54:01 alb-ndm kernel: linvfs_put_super: vfsp/0xd7861fa0 left
dangling!
Feb 4 10:54:01 alb-ndm kernel: VFS: Busy inodes after unmount.
Self-destruct in 5 seconds. Have a nice day...
Feb 4 10:56:32 alb-ndm kernel: XFS: Filesystem sd(8,5) has duplicate
UUID - can't mount
Feb 4 10:57:05 alb-ndm kernel: XFS: Filesystem sd(8,5) has duplicate
UUID - can't mount
Feb 4 11:04:37 alb-ndm kernel: XFS: Filesystem sd(8,5) has duplicate
UUID - can't mount
This is kernel 2.4.18 w/ XFS1.1. Kernel upgrade not an (immediate) option.
The unmount failed beause xfs thought something was still busy, but the
kernel did not. Looks like a reference count leak somewhere in the old
kernel.
If you reboot and run repair you should be ok.
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.
Steve
|