https://bugzilla.kernel.org/show_bug.cgi?id=61631 --- Comment #7 from Jim Faulkner <jfaulkne@xxxxxxxxxxx> --- (In reply to Theodore Tso from comment #5) > Hmm, can you say a bit more about what sort of files you store on the > file system and how the file system gets used? What looks like is > going on is that there is a whole series of inodes that have been left > stalled on the orpaned inode list. By the time we reach that point in > the unmount, the in-memory orphan list should have been cleared. This filesystem holds a wide variety of files. A fair amount (and the majority of the disk usage), is large mp3 (~5 mb) and video (500 mb to 4 gb) files. However, most I/O happens on small files. It hosts the gentoo portage tree which I update regularly, as well as regular rdiff-backups of other servers on my network. Both of these are involve a lot of reading and modifying of lots of small files. (In reply to Jan Kara from comment #6) > Since the mountpoint is named /nfs, I suppose you are exporting the > filesystem via NFS, right? There has been a bug in NFS server code leading > to exactly the problems you are describing. Commit > bf7bd3e98be5c74813bee6ad496139fb0a011b3b should fix the issue (in 3.12-rc1). Yes, I serve large video and mp3 files over NFS. But in addition, the gentoo portage tree on this filesystem is NFS exported to all gentoo hosts on my network. Any gentoo portage operations (emerge --metadata as well as updates) results in lots of NFS I/O on lots of small files. -- 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
