From: Theodore Tso <tytso@mit.edu>
To: Eric Sandeen <sandeen@redhat.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH e2fsprogs] - ignore bind mounts in fsck
Date: Thu, 20 Sep 2007 10:42:45 -0400 [thread overview]
Message-ID: <20070920144245.GD30221@thunk.org> (raw)
In-Reply-To: <46F2845C.2010000@redhat.com>
On Thu, Sep 20, 2007 at 09:31:56AM -0500, Eric Sandeen wrote:
> Agreed. If you think fsck shouldn't silently cope with this mistake,
> and instead punish the user for it (it is what they asked for, after
> all), I'm ok with that too. I'm willing to close my end as NOTABUG if
> you don't want to take this patch. :)
I'm willing to take the patch, although I am thinking that it might be
appropriate for fsck to print a warning message --- "Bind mount with
non-zero fsck pass, skipping", or some such.
What do you think?
- Ted
next prev parent reply other threads:[~2007-09-20 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 20:20 [PATCH e2fsprogs] - ignore bind mounts in fsck Eric Sandeen
2007-09-19 20:42 ` Theodore Tso
2007-09-20 14:31 ` Eric Sandeen
2007-09-20 14:42 ` Theodore Tso [this message]
2007-09-20 15:12 ` Eric Sandeen
2007-09-20 18:59 ` Theodore Tso
2007-09-20 19:08 ` Theodore Tso
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=20070920144245.GD30221@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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).