From: "Theodore Ts'o" <tytso@mit.edu>
To: Stanislav Brabec <sbrabec@suse.cz>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: [PATCH] fsck: implement fsck -r {fd}
Date: Tue, 28 Apr 2015 13:13:03 -0400 [thread overview]
Message-ID: <20150428171302.GA11351@thunk.org> (raw)
In-Reply-To: <553FAD98.5070202@suse.cz>
On Tue, Apr 28, 2015 at 05:56:08PM +0200, Stanislav Brabec wrote:
>
> >We're not parsing the output; it's something that we look at in the
> >log files manually (i.e., by humans when trying to debug a problem.)
>
> SUSE boot scripts parse this output (well, it uses just a part of the
> information) to synchronize fsck and quota activation. Passing an opened
> file descriptor is a good solution for these purposes.
>
> This needs just the one-line statistics generated by fsck, underlying FS
> specific statistics are not needed.
Actually, what of the one-line statistics do you need? Is it just
"we're done checking /dev/sdXX", so you can activate quotas for
/dev/sdXX? If so, one of the other patches which Frank Mayhar (one of
my collegaues) implemented the ability for fsck to run a "completion
handler" which was a program/shell script that would get executed for
each file system the check was completed -- and which would pass the
exit status for each specific file system along to the completion
handler. That allowed us to take specific action on a per-file system
basis if a file system couldn't be repaired, without having to parse
any of the log outputs to determine which file system had
uncorrectable file system problems.
I wonder if something like that would be useful for SuSE?
Regards,
- Ted
next prev parent reply other threads:[~2015-04-28 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 15:20 [PATCH] fsck: implement fsck -r {fd} Stanislav Brabec
2015-04-28 11:52 ` Karel Zak
2015-04-28 14:15 ` Theodore Ts'o
2015-04-28 15:56 ` Stanislav Brabec
2015-04-28 17:13 ` Theodore Ts'o [this message]
2015-04-28 18:30 ` Stanislav Brabec
2015-04-28 15:28 ` Stanislav Brabec
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=20150428171302.GA11351@thunk.org \
--to=tytso@mit.edu \
--cc=kzak@redhat.com \
--cc=sbrabec@suse.cz \
--cc=util-linux@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