xfs
[Top] [All Lists]

Re: xfs on armv5 still with erroneous log in kernel 2.6.35.4

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: xfs on armv5 still with erroneous log in kernel 2.6.35.4
From: Marcus Osdoba <marcus.osdoba@xxxxxxxxxxxxxx>
Date: Wed, 08 Sep 2010 20:36:03 +0200
Cc: Eric Sandeen <sandeen@xxxxxxxxxxx>, xfs@xxxxxxxxxxx
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=+FWyLSA6fbyZVb+HJko3oQaHEH8AKq49Hvhn37/poBI=; b=wkUVJ+Vs3zEK+QNdQBI6bvVBBixHV7PoWBY4UpzZu0llRGW0nmM2b3jLdFLe7cq/GF 9ORSImxyK8FEcPYzLErOEsdaOzrHEGLHfr4q7/ir9qtYc4irUmbHQm8Hvdv2nNdVuzm2 OGfuWOQSsJp7ivRVMJdlvtFIfVDz0Xemt4L8w=
Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=iqiOvzZsH68nJAJ/cc1vXUrYoOeHxTre034hOM7iFDeu748mHZouaPFyZ7gCpKNnY1 2Uulw1Vt3/3LpJtwvmEObpL06qEveAf4Wtl0u8eUou9YkPB0aeg9lXWhHLCOIX05vBxP Qf0SG4LsYeDEe9VxsHbBuQq7UwFv/b0SESBq8=
In-reply-to: <20100908074357.GS705@dastard>
References: <4C835A34.9080008@xxxxxxxxxxxxxx> <20100906005230.GX7362@dastard> <4C845EDE.3010806@xxxxxxxxxxx> <4C8534D0.3050003@xxxxxxxxxxxxxx> <20100907060331.GK705@dastard> <4C86B4E3.5090202@xxxxxxxxxxxxxx> <20100908074357.GS705@dastard>
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
 Am 08.09.2010 09:43, schrieb Dave Chinner:

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...
Hi Dave,

I'm very sorry for annoying you. Please excuse this.

You asked me to copy the exact commands from the terminal. I did that despite the fact, that I replaced "cp /bin/* /data" with "cp something on it". All other commands are 100% the same in exactly the given order in the former mail. Furthermore you asked me to give the output of xfs_printlog with and without option -t. I gave that output in the last mail, too.

Please take my apologies and note the workflow I have tested:

>mount -t xfs /dev/sda1 /data
>cp /bin/sh /data
>sync
>umount /data
>xfs_printlog /dev/sda1
#no ERROR entry visible
>mount -t xfs /dev/sda1 /data
#re mounting works fine, no problems!,
#so I thought running a sync before the umount would solve my erroneous log problem on ARM devices

# The following command chain trys to reproduce the error
>mount -t xfs /dev/sda1 /data
>cp /bin/* /data
>sync
Device or resource busy.
>sync
>umount /data
>xfs_printlog /dev/sda1
#includes an ERROR entry at the end, see last mail

The output of dmesg after trying to mount a partition on which I wrote some files before,
I gave in the very first mail:
"
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS mounting filesystem sda1
Starting XFS recovery on filesystem: sda1 (logdev: internal)
XFS: xlog_recover_process_data: bad clientid
XFS: log mount/recovery failed: error 5
XFS: log mount failed
"

My expectations:
- sync should never be mandatory before unmounting to keep the FS clean (any FS)
- umount should never break the log of the FS

Facts:
Mounting the XFS-Parttition, writing some data on it and unmounting results in an erroneous log which forces a xfs_repair -L on the next mount.
(This I do not expect either...)

I do not know which debug procedures are useful and would give you some useful output. Sorry about this.

After summing up the content I gave in the mailchain, please let me know, if solving this issue has any chance of success.

Thanks and kind regards,
Marcus

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