From: Rogier Wolff <R.E.Wolff@BitWizard.nl>
To: Nico Schottelius <nico-kernel@schottelius.org>,
Nathan Scott <nathans@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: another hard disk broken or xfs problems?
Date: Thu, 26 Feb 2004 11:02:02 +0100 [thread overview]
Message-ID: <20040226100202.GA7006@bitwizard.nl> (raw)
In-Reply-To: <20040226082551.GA218@schottelius.org>
On Thu, Feb 26, 2004 at 09:25:51AM +0100, Nico Schottelius wrote:
> I am really wondering about the error message, as "internal errors"
> indicate for me an error in the kernel.
[...]
> And btw, do all filesystem drivers behave in this way, printing internal
> errors and displaying call traces when they find errors in the
> filesystem?
For a filesystem driver, things are clear: it's the only one writing
to the data on the drive. So when things go wrong: in principle, it's
an internal error.
It would be nice if you'd always be able to salvage your data by
just mounting the partition, but that's not the case. A specialized
program like ...-repair or fsck will do a better job.
Now for a logging filesystem, the assumption that it messed up itself
is even stronger than for a classical filesystem. It should be able
to handle whatever happens.
It's very difficult to check all assumptions about what's on the disk
at every step and still have a reasonable performance. That's why some
errors may only be noticed a bit late and lead to slightly misleading
error messages.
Roger.
--
** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 **
*-- BitWizard writes Linux device drivers for any device you may have! --*
**** "Linux is like a wigwam - no windows, no gates, apache inside!" ****
prev parent reply other threads:[~2004-02-26 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 22:00 another hard disk broken or xfs problems? Nico Schottelius
2004-02-25 22:34 ` Nathan Scott
2004-02-25 23:10 ` Michael Joy
2004-02-28 21:43 ` Stephen Satchell
2004-02-29 8:07 ` John Bradford
2004-02-25 23:49 ` Nico Schottelius
2004-02-26 3:27 ` Nathan Scott
2004-02-26 8:25 ` Nico Schottelius
2004-02-26 9:46 ` Nathan Scott
2004-02-26 19:26 ` Mike Fedyk
2004-02-27 5:53 ` Nathan Scott
2004-02-26 10:02 ` Rogier Wolff [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=20040226100202.GA7006@bitwizard.nl \
--to=r.e.wolff@bitwizard.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=nico-kernel@schottelius.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.