From: Dave Chinner <david@fromorbit.com>
To: Marcus Osdoba <marcus.osdoba@googlemail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs on armv5 still with erroneous log in kernel 2.6.35.4
Date: Mon, 6 Sep 2010 10:52:30 +1000 [thread overview]
Message-ID: <20100906005230.GX7362@dastard> (raw)
In-Reply-To: <4C835A34.9080008@googlemail.com>
On Sun, Sep 05, 2010 at 10:52:04AM +0200, Marcus Osdoba wrote:
> Hello XFS mailinglist,
>
> On my armv5 device I like to use XFS for my simple home made nas,
> because I think it is ideal for low/medium performance CPUs.
> I searched the mailing archive about the usage of XFS on arm
> architecture. I figured out, that the patchset of James Bottomley
> was applied to the main line. So I expected xfs to run properly on
> arm. Unfortunatly I still run into this (known) error after writing
> some data on an xfs partition and remounting it:
> <mailto:xfs@oss.sgi.com>"
> 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
> "
>
> Am I still forced to use the "hammer" approach (flushing buffers in
> xfs_buf.c) which was proposed in January 2010? Or did I misinterpret
> the logfile of the xfs component in the kernel (so no arm fixing
> patches were applied)?
What kernel version are you running? The xfs-vipt branch was merged into
mainline in late February, so kernels from 2.6.34 onwards should be
OK.
If it isn't ok, then we need to know exactly what ARM CPU arch you
are using, and if the old brute-force cache flushing hack fix the
problem or not.
> Is xfs NOW be known to work on arm (e.g. armv5)? If so I like to
> complain. If not, I'm willing to test patches which might solve this
> issue.
I don't know of any outstanding XFS specific issues on ARM, but I
don't have any ARM machines here that I can test on....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-06 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-05 8:52 xfs on armv5 still with erroneous log in kernel 2.6.35.4 Marcus Osdoba
2010-09-06 0:52 ` Dave Chinner [this message]
2010-09-06 3:24 ` Eric Sandeen
2010-09-06 18:37 ` Marcus Osdoba
2010-09-07 6:03 ` Dave Chinner
2010-09-07 21:55 ` Marcus Osdoba
2010-09-08 7:43 ` Dave Chinner
2010-09-08 18:36 ` Marcus Osdoba
2010-09-09 6:45 ` Dave Chinner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100906005230.GX7362@dastard \
--to=david@fromorbit.com \
--cc=marcus.osdoba@googlemail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.