| 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:42:16 +0100 (CET) |
| Cc: | "Smith, Andy P." <smith-andy@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040210193707.A9197@xxxxxxxxxxxxx> |
| References: | <C2586F0871D87141A33EB87FC383B38114D48C@xxxxxxxxxxxxxxxxxxxxx> <20040210193707.A9197@xxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Tue, 10 Feb 2004, Christoph Hellwig wrote:
Hi.
> On Tue, Feb 10, 2004 at 02:34:29PM -0500, Smith, Andy P. wrote:
> > Hi,
> >
> > I'm seeing problems with XFS 1.3.1 when using the xfs_db tool. I've tried
> > several different combinations of kernels and hardware including:
>
> Don't use xfs_db on the blockdevice while the filesystem is mounted
> currently. I'm looking into this issue curretnly but it's not easy
> to fix.
>
> 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?
jan
--
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | TAKE 909260 - trivial tidying, Nathan Scott |
|---|---|
| Next by Date: | Re: mkfs.xfs, David Jez |
| 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] |