From: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: info about filesystem errors in /sys/fs/ext4/... ?
Date: Mon, 5 May 2014 13:14:20 +0200 [thread overview]
Message-ID: <20140505111420.GJ11499@pcnci.linuxbox.cz> (raw)
In-Reply-To: <alpine.LFD.2.00.1405051253400.2223@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1857 bytes --]
Hello Lukáš,
> Currently I do not think there is a way to check whether mounted
> file system contains errors (EXT2_ERROR_FS flag is set in super
> block).
>
> You either have to check the logs, or run fsck before mounting the
> file system.
>
> It really seems like a optimal thing to provide a way to inform user
> space about this without the need to parse the log. I think that
> sysfs is a perfect place for this.
>
> 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.
>
> What about having this scenario respect "errors=" setting ? Of
> course it might not make sense to panic when mounting file system
> with errors with "errors=panic" option, we can just fail the mount.
>
> Will that help your case ?
Yes for some cases, no for others :) For example I do not want server to
fail booting if it could otherwise start (even though it might need some
intervention, at least running fsck). Giving simple way (like mentioned sysfs
access) would make monitoring such issues much simpler.
Of course for some cases, it's for sure safer to disallow mounting rather
then risking further data corruption...
I'm not sure how big is chance that mounting filesystem with errors can
cause more errors, I guess it depends on the nature of the problem..
cheers!
nik
>
> Thanks!
> -Lukas
>
--
-------------------------------------
Ing. Nikola CIPRICH
LinuxBox.cz, s.r.o.
28.rijna 168, 709 00 Ostrava
tel.: +420 591 166 214
fax: +420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-05-05 11:14 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 [this message]
2014-05-05 11:59 ` Theodore Ts'o
2014-05-05 14:53 ` Eric Sandeen
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=20140505111420.GJ11499@pcnci.linuxbox.cz \
--to=nikola.ciprich@linuxbox.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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).