https://bugzilla.kernel.org/show_bug.cgi?id=61631 --- Comment #4 from Jim Faulkner <jfaulkne@xxxxxxxxxxx> --- FYI, this bug only appears after some period of usage. After a reboot, I can umount without error. After a reboot and an rsync of the gentoo portage tree to the filesystem, I can still umount without error. It seems the filesystem only fails to unmount after the filesystem has been in use for a while. However, it is quite consistent in failing to umount after several days of usage. Some more details on this filesystem: thud ~ # df -h | grep md1 /dev/md1 7.2T 6.7T 488G 94% /nfs thud ~ # df -i | grep md1 /dev/md1 484597760 41868439 442729321 9% /nfs thud ~ # tune2fs -l /dev/md1 tune2fs 1.42.7 (21-Jan-2013) Filesystem volume name: <none> Last mounted on: /nfs Filesystem UUID: a9f907fb-4d04-4a28-8164-a2ac4d5a26f4 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Remount read-only Filesystem OS type: Linux Inode count: 484597760 Block count: 1938377664 Reserved block count: 0 Free blocks: 127846725 Free inodes: 442729321 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 561 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Sat Oct 9 08:53:46 2010 Last mount time: Wed Sep 18 18:25:38 2013 Last write time: Wed Sep 18 18:25:38 2013 Mount count: 4 Maximum mount count: 23 Last checked: Wed Sep 11 04:36:58 2013 Check interval: 15552000 (6 months) Next check after: Mon Mar 10 04:36:58 2014 Lifetime writes: 18 TB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 1584912d-08c0-46a6-a652-60800c55c4df Journal backup: inode blocks thud ~ # -- You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
