On Tue, 15 Sep 2009 15:20:39 +0900 Toshiyuki Okajima <toshi.okajima@xxxxxxxxxxxxxx> wrote: > Hi Ted, Andrew and all. > > Under the current implementation, we cannot know in the system log > (/var/log/messages) when the filesystem (ext2/ext3/ext4) is unmounted. > For enterprise users, they often want to observe certain filesystems' > actions (mount/unmount) in the system log. Besides, by the system log, > we occasionally wants to know whether a certain filesystem has been > unmounted or not at the time when a problem happens. > I don't think we want to make random printks a part of the kernel ABI like this. I understand that it's practical and easy for people to parse the logs in a local ad-hoc manner such as this, but... ugh. If there's a userspace requirement for notification when filesystems are mounted and unmounted then fine, let's look at that. What is the detailed requirement? What info do we want to see? What is an appropriate way of delivering that info? kobject_uevent() looks like a suitable place to start. That being said, there is perhaps a case to made for being more verbose when filesystems are mounted and unmounted. But yes, doing that in the VFS for all filesystems sounds better. This might upset people who have thousands of NFS autmounts though. -- 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