xfs
[Top] [All Lists]

Re: XFS_DB Problem (Corruption of in-memory data detected.)

To: Jan Derfinak <ja@xxxxxxxxxxxx>
Subject: Re: XFS_DB Problem (Corruption of in-memory data detected.)
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 10 Feb 2004 22:43:50 +0000
Cc: "Smith, Andy P." <smith-andy@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <Pine.LNX.4.58.0402102325340.22771@xxxxxxxxxxxxxxxxxx>; from ja@xxxxxxxxxxxx on Tue, Feb 10, 2004 at 11:42:16PM +0100
References: <C2586F0871D87141A33EB87FC383B38114D48C@xxxxxxxxxxxxxxxxxxxxx> <20040210193707.A9197@xxxxxxxxxxxxx> <Pine.LNX.4.58.0402102325340.22771@xxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Tue, Feb 10, 2004 at 11:42:16PM +0100, Jan Derfinak wrote:
> > On Linux 2.6 you'll even get a panic for that currently.
> > 
> 
> I have used xfs_db in read-only mode on mounted partitions for long time and I
> never had problem. I use 2.6 kernel now. What is wrong on read-only
> access?

The block device and XFS's metadata use the same pages but they don't
talk to each other enough, so you can get into cases where a page used
by XFS is flushed and the blockdevice code scribbles over the page which
will get you inmemory corruption. 


<Prev in Thread] Current Thread [Next in Thread>