From: Christoph Hellwig <hch@infradead.org>
To: Daniel Goller <morfic@gmail.com>, James.Bottomley@HansenPartnership.com
Cc: xfs@oss.sgi.com
Subject: Re: State of XFS on ARM
Date: Tue, 2 Feb 2010 06:23:00 -0500 [thread overview]
Message-ID: <20100202112300.GA23809@infradead.org> (raw)
In-Reply-To: <13bb8ce11002011924h611099feh4955eedcc6e588a6@mail.gmail.com>
On Mon, Feb 01, 2010 at 09:24:33PM -0600, Daniel Goller wrote:
> It seems i have not been able to unmount it and then mounting it
> cleanly once, always required xfs_repair -L /dev/sdc3
> I Could understand power issues or lockups causing this, but on clean
> umount and followed mount to see it fail is surprising.
> When mounting fails on the headless arm machine i move the drive to a
> x86_64 and run xfs_repair there when mounting there fails too (so log
> can't be replayed, making -L necessary).
> All of this leads me to ask: "Is XFS as well maintained on ARM as it
> is on x86/x86_64?"
XFS itself is platform neutral. But it seems like you have an ARM
platform with virtually indexed caches, which currently can't support
the I/O XFS does. James has been working on fixing this for a while,
but so far the architecture support patches for it unfortunately still
haven't made it to mainline despite many people running into this issue.
The git tree with the current versions of the patches to fix this is
here:
http://git.kernel.org/?p=linux/kernel/git/jejb/xfs-vipt/.git;a=summary
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-02-02 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 3:24 State of XFS on ARM Daniel Goller
2010-02-02 3:52 ` Eric Sandeen
2010-02-02 11:23 ` Christoph Hellwig [this message]
2010-02-02 15:42 ` Richard Sharpe
2010-02-02 16:12 ` James Bottomley
2010-02-03 2:19 ` Daniel Goller
2010-02-03 20:34 ` Daniel Goller
2010-02-03 20:38 ` Christoph Hellwig
2010-02-03 20:46 ` Eric Sandeen
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=20100202112300.GA23809@infradead.org \
--to=hch@infradead.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=morfic@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox