public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Nathan Scott <nathans@sgi.com>
Cc: Nico Schottelius <nico-kernel@schottelius.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: another hard disk broken or xfs problems?
Date: Thu, 26 Feb 2004 11:26:51 -0800	[thread overview]
Message-ID: <403E487B.8020707@matchmail.com> (raw)
In-Reply-To: <20040226204615.A481868@wobbly.melbourne.sgi.com>

Nathan Scott wrote:
> On Thu, Feb 26, 2004 at 09:25:51AM +0100, Nico Schottelius wrote:
>>And btw, do all filesystem drivers behave in this way, printing internal
>>errors and displaying call traces when they find errors in the
>>filesystem?
> 
> 
> No, not all filesystem behave this way.  And it is configurable
> in XFS; if you don't want this to happen, you can switch it off
> via the sysctl/procfs interface - see the "error_level" section
> in Documentation/filesystems/xfs.txt.

I like this idea.

Is it just calling dump_stack() based on error level?

  reply	other threads:[~2004-02-26 19:29 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 [this message]
2004-02-27  5:53             ` Nathan Scott
2004-02-26 10:02         ` Rogier Wolff

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=403E487B.8020707@matchmail.com \
    --to=mfedyk@matchmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox