From: Matthias Schniedermeyer <ms@citd.de>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: xfs.fsck change that is unhelpful
Date: Mon, 16 Aug 2010 00:43:41 +0200 [thread overview]
Message-ID: <20100815224341.GA9438@citd.de> (raw)
In-Reply-To: <4C674AE8.7030107@tlinx.org>
On 14.08.2010 19:03, Linda Walsh wrote:
>
>
> Dave Chinner wrote:
>> 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.
> ---
> That may be fine for the ext2 fs, but I am asserting that in actual
> practice, with xfs, it does more harm than good.
I would suggest using autofs, so that you can keep fstab to an absolut
minimum.
Except for devices related to booting, i personally mount everything
either with autofs or manually(In that case it's normaly a one-shot
thing).
In my case that are all "non boot related" devices, DVD-drive, network
filesystems, some "tmpfs"es for playing, removable-devices, etc.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-15 22:43 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
2010-08-15 2:03 ` Linda Walsh
2010-08-15 18:54 ` Hans-Peter Jansen
2010-08-15 22:43 ` Matthias Schniedermeyer [this message]
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=20100815224341.GA9438@citd.de \
--to=ms@citd.de \
--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.