| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS_DB Problem (Corruption of in-memory data detected.) |
| From: | Jan Derfinak <ja@xxxxxxxxxxxx> |
| Date: | Tue, 10 Feb 2004 23:58:26 +0100 (CET) |
| Cc: | "Smith, Andy P." <smith-andy@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040210224350.A11692@xxxxxxxxxxxxx> |
| References: | <C2586F0871D87141A33EB87FC383B38114D48C@xxxxxxxxxxxxxxxxxxxxx> <20040210193707.A9197@xxxxxxxxxxxxx> <Pine.LNX.4.58.0402102325340.22771@xxxxxxxxxxxxxxxxxx> <20040210224350.A11692@xxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Tue, 10 Feb 2004, Christoph Hellwig wrote:
Hi.
> > 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.
>
Thanks.
I suggest to notice this in xfs_db man page. From description of '-r' option
isn't clear that it is dangerous.
jan
--
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS_DB Problem (Corruption of in-memory data detected.), Christoph Hellwig |
|---|---|
| Next by Date: | Re: XFS_DB Problem (Corruption of in-memory data detected.), Christoph Hellwig |
| Previous by Thread: | Re: XFS_DB Problem (Corruption of in-memory data detected.), Christoph Hellwig |
| Next by Thread: | Re: XFS_DB Problem (Corruption of in-memory data detected.), Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |