[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090121040042.GI10158@disturbed>
Date: Wed, 21 Jan 2009 15:00:42 +1100
From: Dave Chinner <david@...morbit.com>
To: Pavel Machek <pavel@...e.cz>
Cc: Christoph Hellwig <hch@...radead.org>,
Eric Sesterhenn <snakebyte@....de>,
Chris Mason <chris.mason@...cle.com>,
linux-kernel@...r.kernel.org, linux-btrfs@...r.kernel.org
Subject: Re: Warning and BUG with btrfs and corrupted image
On Tue, Jan 20, 2009 at 11:20:19PM +0100, Pavel Machek wrote:
> On Tue 2009-01-20 08:28:29, Christoph Hellwig wrote:
> > On Tue, Jan 20, 2009 at 11:59:44PM +1100, Dave Chinner wrote:
> > > > So far the responses from xfs folks have been disappointing, if you are
> > > > interested in bugreports i can send you some.
> > >
> > > Sure I am. It would be good if you could start testing XFS along
> > > with all the other filesystems and report anything you find.
> >
> > I think that was the issue with the debug builds. If you do this
> > testing always do it without CONFIG_XFS_DEBUG set as with that option
> > we intentionally panic on detected disk corruptions.
>
> Uhuh, *_DEBUG options are not supposed to make kernel less
> stable/robust. Should that crashing functionality be guarded with
> command line option or something? ext2 has errors=panic mount
> option...
No, it's a debugging option that is described as:
"Say N unless you are an XFS developer, or you play one on TV."
Seriously, if you aren't trying to develop XFS stuff then *don't turn it
on*.
Cheers,
Dave.
--
Dave Chinner
david@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists