nilfs2 cannot umount, device is always busy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nilfs-tools (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
nilfs-tools 2.1.5-1 on a fresh install ubuntu 13.10 x86_64
The filesystem mounts and seems to be working correctly (also lscp, mkcp and others seem to work as expected), but when trying to umount the device (be it a real partition, loop device or luks device) the result is always this one:
# umount /mnt/nilfs/
umount.nilfs2: /dev/loop0: device is busy
umount.nilfs2: /dev/loop0: device is busy
# umount /dev/loop0
umount.nilfs2: /dev/loop0: device is busy
umount.nilfs2: /dev/loop0: device is busy
# lsof /mnt/nilfs/
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nilfs_cle 2777 root 5r DIR 7,0 4096 2 /mnt/nilfs
# ps aux | grep 2777
root 2777 0.0 0.0 14824 904 ? Ss 19:59 0:00 /sbin/nilfs_
# kill -9 2777
# umount /mnt/nilfs/ <-- Works
So, it seems like nilfs_cleanered prevents the device from being umounted at all times. This bug is reproducible 100% of the times for me.
Killing the deamon seems to be the only way to umount a nilfs2 mounted partition.
--EDIT--
This is also reproducible when booting from the live CD image of ubuntu 13.10_64 (I booted from liveCD image, added community repository and "apt-get update && apt-get install nilfs-tools")
--EDIT2--
Version 2.1.0-1 of nilfs-tools on Ubuntu 12.04.3 LTS was unaffected from this bug, just tested it.
Status changed to 'Confirmed' because the bug affects multiple users.