From: Eric Sandeen <sandeen@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>, "Lukáš Czerner" <lczerner@redhat.com>
Cc: Nikola Ciprich <nikola.ciprich@linuxbox.cz>, linux-ext4@vger.kernel.org
Subject: Re: info about filesystem errors in /sys/fs/ext4/... ?
Date: Mon, 05 May 2014 09:53:25 -0500 [thread overview]
Message-ID: <5367A5E5.10809@redhat.com> (raw)
In-Reply-To: <20140505115919.GB18305@thunk.org>
On 5/5/14, 6:59 AM, Theodore Ts'o wrote:
> On Mon, May 05, 2014 at 01:03:17PM +0200, Lukáš Czerner wrote:
>>
>> However we might to go a step further, because I do not
>> really like the idea of allowing to mount the file system with
>> errors by default. It does not really make sense to me and I wonder
>> whether someone actually intend to do it this way.
>
> We would need to make an exception for the root file system, of
> course. And I've been receiving patches from folks who want to allow
> e2fsck to be able to fix a mounted, read-only /usr partition, since
> systemd is forcing folks to have to mount /usr read-only before it
> will start, which means /usr needs to be mounted before e2fsck gets
> started by systemd.
I hope these patches make it to the list, if you're considering them.
I don't really know why fsck would need to treat filesystems differently
based on where they are mounted; either we can repair a readonly fs
or not, right? And if it's done, then the filesystem needs to be immediately
unmounted & remounted[1], or the system rebooted...
-Eric
[1] and I suppose if it can be unmounted & mounted then there was no
good reason to repair it while mounted RO...
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-05 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 7:08 info about filesystem errors in /sys/fs/ext4/... ? Nikola Ciprich
2014-05-05 11:03 ` Lukáš Czerner
2014-05-05 11:14 ` Nikola Ciprich
2014-05-05 11:59 ` Theodore Ts'o
2014-05-05 14:53 ` Eric Sandeen [this message]
2014-05-05 19:15 ` Theodore Ts'o
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=5367A5E5.10809@redhat.com \
--to=sandeen@redhat.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
--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).