From: Dave Chinner <david@fromorbit.com>
To: "Linda A. Walsh" <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs.fsck change that is unhelpful
Date: Sun, 15 Aug 2010 10:52:40 +1000 [thread overview]
Message-ID: <20100815005240.GH10429@dastard> (raw)
In-Reply-To: <4C670101.8050901@tlinx.org>
On Sat, Aug 14, 2010 at 01:48:01PM -0700, Linda A. Walsh wrote:
>
> Some time ago, when I upgraded a system, I ran into problems when
> it hit a file system that was offline. It wasn't a critical
> partition, so it normally wouldn't have been an issue, but somewhere
> along the line
> someone mangled fsck.xfs.
fsck.xfs is behaving identically to e2fsck when presented with an
invalid block device - it exits with an error of 8, which is defined
as "operational error" in the e2fsck man page.
> Instead of doing the useful thing with an xfs file system and being a
> link to ->/bin/true, someone thought it would be neat to return failure if
> it couldn't find the file system that it was supposed to check
If the device is not present when the bootup sequence is attempting
to access it, then you've got a configuration error somewhere. It
should return an error.
> (mount-by-name, name not yet present, => system refuse to boot).
That sounds like a problem with the distro init scripts or you've
stuffed up your /etc/fstab config (i.e. fs_passno is wrong). Indeed,
setting fs_passno = 0 will cause the filesysetm fsck to be skipped
completely on boot, regardless of the fs type...
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-15 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 20:48 xfs.fsck change that is unhelpful Linda A. Walsh
2010-08-15 0:52 ` Dave Chinner [this message]
2010-08-15 2:03 ` Linda Walsh
2010-08-15 18:54 ` Hans-Peter Jansen
2010-08-15 22:43 ` Matthias Schniedermeyer
2010-08-16 1:55 ` Dave Chinner
2010-08-16 2:26 ` Linda Walsh
2010-08-16 9:44 ` Stan Hoeppner
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=20100815005240.GH10429@dastard \
--to=david@fromorbit.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.