[Top] [All Lists]

Re: xfs on armv5 still with erroneous log in kernel

To: Marcus Osdoba <marcus.osdoba@xxxxxxxxxxxxxx>
Subject: Re: xfs on armv5 still with erroneous log in kernel
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Wed, 8 Sep 2010 17:43:57 +1000
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <4C86B4E3.5090202@xxxxxxxxxxxxxx>
References: <4C835A34.9080008@xxxxxxxxxxxxxx> <20100906005230.GX7362@dastard> <4C845EDE.3010806@xxxxxxxxxxx> <4C8534D0.3050003@xxxxxxxxxxxxxx> <20100907060331.GK705@dastard> <4C86B4E3.5090202@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.20 (2009-06-14)
On Tue, Sep 07, 2010 at 11:55:47PM +0200, Marcus Osdoba wrote:
>  Am 07.09.2010 08:03, schrieb Dave Chinner:
> >On Mon, Sep 06, 2010 at 08:37:04PM +0200, Marcus Osdoba wrote:
> >>I'm using the latest stable kernel The filesystem was
> >>created on the target device with a cross compiled xfsprogs 3.1.3.
> >>The systems runs on an armv5te architecture (sheevaplug derivative).
> >>After creating, mounting and writing some data on it, re-mounting
> >>was not possible with the above mentioned error. I've found this
> >>message in the mailinglistarchive and thought the patches were
> >>integrated into mainline.
> >>
> >>How can I help? What additional information do you need?

> Is sync'ing enough for solving this issue? -> Reproduce:
> >mount /dev/sda1 /data
> >cp something more on it
> >sync
> >umount /data
> >device or resource busy

What is this error? Anything in dmesg? Does this always occur
before the log recovery error on next mount?

FWIW, please copy the exact commands and errors from your terminal -
paraphrasing them like this does not help me underѕtand exactly what
is happening...


Dave Chinner

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