| To: | "Smith, Andy P." <smith-andy@xxxxxxx> |
|---|---|
| Subject: | Re: XFS_DB Problem (Corruption of in-memory data detected.) |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Wed, 11 Feb 2004 14:59:32 +0000 |
| Cc: | Jan Derfinak <ja@xxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <C2586F0871D87141A33EB87FC383B38114D490@danube.rivers.zai.com>; from smith-andy@zai.com on Wed, Feb 11, 2004 at 09:53:39AM -0500 |
| References: | <C2586F0871D87141A33EB87FC383B38114D490@danube.rivers.zai.com> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
On Wed, Feb 11, 2004 at 09:53:39AM -0500, Smith, Andy P. wrote: > Jan, > > In case you're curious I encountered this problem most frequently (and > reproduced it most easily) by using xfs_db interactively whilst performing a > lot of I/O (mostly writes) on the same partition. Yes, this is exactly the expected patter - if you don't actually write to the filesystems the overwriting caused by the blockdevice doesn't matter. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: XFS_DB Problem (Corruption of in-memory data detected.), Smith, Andy P. |
|---|---|
| Next by Date: | Re: dm_write_invis() blocking problem, Dean Roehrich |
| Previous by Thread: | RE: XFS_DB Problem (Corruption of in-memory data detected.), Smith, Andy P. |
| Next by Thread: | TAKE 909260 - trivial tidying, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |