Actually I was wrong with the usage - I was testing whether /home is in
use with "fuser -m /home". I've added the "-m" argument out of habit.
Actually, /home seems to be unused - plain "fuser /home" shows no
accessing processes. So the cause seems to be different.

The symptoms are:

# fuser /home
# mount /dev/hda6 /home/
mount: /dev/hda6 already mounted or /home/ busy
# mount -v -t xfs /dev/hda6 /home/
mount: /dev/hda6 already mounted or /home/ busy
# hexdump -C /dev/hda6 | head
00000000  58 46 53 42 00 00 10 00  00 00 00 00 01 96 52 e0  |XFSB..........R.|
00000010  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
00000020  c9 e3 cb ee 47 e0 11 d7  9f 33 ed 99 1e fa c2 d0  |....G....3......|
00000030  00 00 00 00 00 d0 00 04  00 00 00 00 00 00 00 80  |................|
00000040  00 00 00 00 00 00 00 81  00 00 00 00 00 00 00 82  |................|
00000050  00 00 00 10 00 10 00 00  00 00 00 1a 00 00 00 00  |................|
00000060  00 00 0c b2 20 94 02 00  01 00 00 10 00 00 00 00  |.... ...........|
00000070  00 00 00 00 00 00 00 00  0c 09 08 04 14 00 00 19  |................|
00000080  00 00 00 00 00 05 c7 80  00 00 00 00 00 01 de a2  |................|
00000090  00 00 00 00 00 32 0f 26  00 00 00 00 00 00 00 00  |.....2.&........|


A sidenote to Stephen: On POSIX systems (including Linux) you actually _can_ 
delete files and directories that are in use, since they are identified by 
their inode numbers.

So if your /home directory is used by some processes, you can still
rmdir or "rm -rf" it and it will disappear. You can mkdir a new /home,
and it will be a different one, and the processess holding the old one
will still see the old one. Its space will be reclaimed in the
filesystem when the last process to use it will close its handle. You
can test a filesystem object's usage using the "fuser" command.

But to be used as a mount point, a directory cannot be in use.

-- 
xfs /home cannot be mounted on boot
https://bugs.launchpad.net/bugs/153600
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to