linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
To: Theodore Tso <tytso@mit.edu>
Cc: akpm@linux-foundation.org, adilger@sun.com, sandeen@redhat.com,
	linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/3][RFC](Repost) ext4: add a message in remount/umount for ext4
Date: Thu, 01 Oct 2009 12:20:17 +0900	[thread overview]
Message-ID: <4AC41FF1.7060703@jp.fujitsu.com> (raw)
In-Reply-To: <20090930172220.GL24383@mit.edu>

Hi Ted, thank you for your comment.

Theodore Tso wrote:
 > On Wed, Sep 30, 2009 at 03:49:31PM +0900, Toshiyuki Okajima wrote:
 > > > From: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
 > > >
 > > > ext4 doesn't log a record of having unmounted the filesystem. And ext4 doesn't
 > > > log a record when the filesystem is remounted also with read-only. Therefore
 > > > in the system log, we cannot judge whether or not at the certain time this
 > > > filesystem user touches it.
 > > > For enterprise users, they often want to know when a certain filesystem is
 > > > mounted/remounted/unmounted.
 > > >
 > > > So, we output the message to the system log when the filesystem is
 > > > remounted/unmounted.
 > > >
 > > > Signed-off-by: Toshiyuki Okajima <toshi.okajima@jp.fujitsu.com>
 >
 > The question of whether this should be at the VFS layer is still an
 > open one, I think.  It is true that ext3 and ext4 does print some
I am recognizing it. But I think I have already explained its answer as follows:
  - A print mechanism has already been included at mount time.
  - The umount operation is opposite "mount operation". Therefore I think
    it is no problem that we add the print mechanism at the umount time.

 > filesystem specific information, but that could be handled via a new
 > method function in struct super_ops:
 >
 >        mount_msg(struct super *sb, char *buf, int buflen)
 >
However, I have noticed that the purpose of ext3/ext4 messages at mount time
is for specific information but not for a general purpose by this comment.

So, I think I should rearrange this feature into the VFS layer.
I try to reimplement it later.

Thanks,
Toshiyuki Okajima


  reply	other threads:[~2009-10-01  3:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  6:49 [PATCH 3/3][RFC](Repost) ext4: add a message in remount/umount for ext4 Toshiyuki Okajima
2009-09-30 17:22 ` Theodore Tso
2009-10-01  3:20   ` Toshiyuki Okajima [this message]
2009-10-01  3:55     ` Theodore Tso
2009-10-01  4:32       ` 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=4AC41FF1.7060703@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;
as well as URLs for NNTP newsgroup(s).