public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Daniel Goller <morfic@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: State of XFS on ARM
Date: Mon, 01 Feb 2010 21:52:44 -0600	[thread overview]
Message-ID: <4B67A18C.8010009@sandeen.net> (raw)
In-Reply-To: <13bb8ce11002011924h611099feh4955eedcc6e588a6@mail.gmail.com>

Daniel Goller wrote:
> Dear Sir or Madam,
> 
> I Would like to find out about the current state of XFS on ARM.
> I have been using XFS for a while successfully on my laptop, and was
> using XFS on a ARM device (little endian) since it would hold the same
> data i had on the laptop.
> 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.

well, actually neither power issues nor lockups should cause it either ;)

> 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?"

Short answer no, but effort is made.  The last known issue, as far
as I know, is a cache aliasing problem.

This patch is a big-hammer approach, better things have been proposed
but not yet upstream as far as I know.

With "what doesn't work" helpfully commented out  ;) 

Index: linux-2.6.22.18/fs/xfs/linux-2.6/xfs_buf.c
===================================================================
--- linux-2.6.22.18.orig/fs/xfs/linux-2.6/xfs_buf.c
+++ linux-2.6.22.18/fs/xfs/linux-2.6/xfs_buf.c
@@ -1185,6 +1185,8 @@ _xfs_buf_ioapply(
 		bio->bi_end_io = xfs_buf_bio_end_io;
 		bio->bi_private = bp;
 
+		//flush_dcache_page(bp->b_pages[0]);
+		flush_cache_all();
 		bio_add_page(bio, bp->b_pages[0], PAGE_CACHE_SIZE, 0);
 		size = 0;
 
@@ -1211,6 +1213,8 @@ next_chunk:
 		if (nbytes > size)
 			nbytes = size;
 
+		//flush_dcache_page(bp->b_pages[map_i]);
+		flush_cache_all();
 		rbytes = bio_add_page(bio, bp->b_pages[map_i], nbytes, offset);
 		if (rbytes < nbytes)
 			break;



> Thank you in advance for any info you can provide,
> 
> Daniel Goller
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
> 

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-02-02  3:51 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 [this message]
2010-02-02 11:23 ` Christoph Hellwig
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=4B67A18C.8010009@sandeen.net \
    --to=sandeen@sandeen.net \
    --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