From: Marco Gaiarin <gaio@sv.lnf.it>
To: Jason White <jason@jasonjgw.net>, xfs@oss.sgi.com
Subject: Re: XFS check script on boot?
Date: Tue, 18 Mar 2008 11:41:01 +0100 [thread overview]
Message-ID: <20080318104055.GA7903@sv.lnf.it> (raw)
In-Reply-To: <20080318011210.GA12727@jdc.jasonjgw.net>
Mandi! Jason White
In chel di` si favelave...
> The purpose of a journaling file system is to make time-consuming fsck and
> similar checks unnecessary after a reboot.
I know exactly that, and indeed, i agree.
I'm not speaking about writing a script that check everytime the
filesystem, but sometime (triggered by /forcefsck?)
The problem arise when you have on a remote site people with low
knowledge, and have to instruct them to run the kernel in
init=/bin/bash mode or in initrd 'emergency' mode, spelling all command
by phone.
[ok, a remote controlled KVM switch is on the buy list ;]
With a such boot script, if a fsck was forced, and a corruption founded,
the system ask for root password and an operator find a shell with /
mounted readonly and all other system unmounted (eg, the 'normal' way
of checking eg, for EXT3; apart that for other filesystem a 'simple'
check are ever tried, and password are asked only for serious corruption
that need 'fsck -f').
A good starting point for trying a recovery.
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia'' http://www.sv.lnf.it/
Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN)
marco.gaiarin(at)sv.lnf.it tel +39-0434-842711 fax +39-0434-842797
prev parent reply other threads:[~2008-03-18 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 13:48 XFS check script on boot? Marco Gaiarin
2008-03-18 1:12 ` Jason White
2008-03-18 10:41 ` Marco Gaiarin [this message]
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=20080318104055.GA7903@sv.lnf.it \
--to=gaio@sv.lnf.it \
--cc=jason@jasonjgw.net \
--cc=xfs@oss.sgi.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