public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: tytso@mit.edu, akpm@linux-foundation.org, adilger@sun.com,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/3][RFC] add a message in mount/remount/umount for ext2/ext3/ext4
Date: Wed, 16 Sep 2009 13:51:53 +0900	[thread overview]
Message-ID: <20090916135153.9b49c58b.toshi.okajima@jp.fujitsu.com> (raw)
In-Reply-To: <4AAFAFAE.2090801@redhat.com>

Hi Eric,
Thanks for your comment.

On Tue, 15 Sep 2009 10:15:58 -0500
Eric Sandeen <sandeen@redhat.com> wrote:
> Toshiyuki Okajima 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.
> > 
> > The following patch series implement above demand. 
> > Please apply it.
> 
> If this is really a common requirement, perhaps we should at least
> consider putting it in the vfs, in  vfs_kern_mount(),
> generic_shutdown_super(), and do_remount_sb().
Yes. I also thought it was appropriate that where this feature was implemented
was on VFS. But ext3/ext4 has already included the message mechanism which
operates when ext3/ext4 is mounted/remounted.

So, to achieve this feature easily, I have rearranged the message mechanism in
ext3/ext4 (ext2 is newly implemented).

> 
> That way we'll have common behavior and less replicated code; nothing in
> this patch series is unique to ext[234] as far as I can tell.
> 
> sb->s_type->name could be used to print the fs type in a generic message.

Thanks,
Toshiyuki Okajima

  reply	other threads:[~2009-09-16  4:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-15  6:20 [PATCH 0/3][RFC] add a message in mount/remount/umount for ext2/ext3/ext4 Toshiyuki Okajima
2009-09-15 15:15 ` Eric Sandeen
2009-09-16  4:51   ` Toshiyuki Okajima [this message]
2009-09-15 22:20 ` Andrew Morton
2009-09-16  4:55   ` Toshiyuki Okajima

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090916135153.9b49c58b.toshi.okajima@jp.fujitsu.com \
    --to=toshi.okajima@jp.fujitsu.com \
    --cc=adilger@sun.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox