From: Eric Sandeen <sandeen@sandeen.net>
To: Ofer Heifetz <oferh@marvell.com>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: XFS support for ARMv5
Date: Sun, 22 Nov 2009 10:53:02 -0600 [thread overview]
Message-ID: <4B096C6E.8010508@sandeen.net> (raw)
In-Reply-To: <EE71107DF0D1F24FA2D95041E64AB9E8985A59F17F@IL-MB01.marvell.com>
Ofer Heifetz wrote:
> Hi Eric,
>
> I have tried the patch you advised and still get the same error using 2.6.31.6, xfs version 2.10.2 on Ubuntu 9.04.
>
> Any other suggestions you think that might help me with this?
Please start by:
> when you get that error from mount, look at dmesg to see what really went wrong ...
because all I know now is "it didn't mount" which isn't much to go on.
-Eric
> -Ofer
>
> -----Original Message-----
> From: Eric Sandeen [mailto:sandeen@sandeen.net]
> Sent: Wednesday, November 18, 2009 6:04 PM
> To: Ofer Heifetz
> Cc: xfs@oss.sgi.com
> Subject: Re: XFS support for ARMv5
>
> oferh@marvell.com wrote:
>> Hi,
>>
>> I have noticed that XFS on ARMv5TE with latest kernel (2.6.31.6)
>> fails to mount after copying some data and reboot the system.
>>
>> I get "mount: /dev/sda1: can't read superblock", I understand that
>> there were some problems with virtual aliasing that was added to XFS
>> some time ago but ARM arch has not dealt with this properly.
>
> when you get that error from mount, look at dmesg to see what really went wrong ...
>
>> Is there any patch for this bug?
>
> This is a big-hammer approach for the aliasing problem:
>
> Index: linux-2.6.25-rc1/fs/xfs/linux-2.6/xfs_buf.c
> ===================================================================
> --- linux-2.6.25-rc1.orig/fs/xfs/linux-2.6/xfs_buf.c
> +++ linux-2.6.25-rc1/fs/xfs/linux-2.6/xfs_buf.c
> @@ -1172,6 +1172,7 @@ _xfs_buf_ioapply(
> bio->bi_end_io = xfs_buf_bio_end_io;
> bio->bi_private = bp;
>
> + flush_dcache_page(bp->b_pages[0]);
> bio_add_page(bio, bp->b_pages[0], PAGE_CACHE_SIZE, 0);
> size = 0;
>
> @@ -1198,6 +1199,7 @@ next_chunk:
> if (nbytes > size)
> nbytes = size;
>
> + flush_dcache_page(bp->b_pages[map_i]);
> rbytes = bio_add_page(bio, bp->b_pages[map_i], nbytes, offset);
> if (rbytes < nbytes)
> break;
>
>
>
>> xfsprogs version used: 2.10.2
>>
>> -Ofer
>>
>> -- This message was sent on behalf of oferh@marvell.com at
>> openSubscriber.com
>> http://www.opensubscriber.com/messages/xfs@oss.sgi.com/topic.html
>>
>> _______________________________________________ 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
next prev parent reply other threads:[~2009-11-22 16:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 12:21 XFS support for ARMv5 oferh
2009-11-18 16:03 ` Eric Sandeen
2009-11-22 16:20 ` Ofer Heifetz
2009-11-22 16:45 ` Richard Sharpe
2009-11-22 20:07 ` Ofer Heifetz
2009-11-22 20:16 ` Richard Sharpe
2009-11-23 15:56 ` Ofer Heifetz
2009-11-22 16:53 ` Eric Sandeen [this message]
2009-11-23 14:46 ` Ofer Heifetz
2009-11-25 16:30 ` Andy Poling
2009-11-25 21:06 ` Christoph Hellwig
2009-11-25 22:10 ` Eric Sandeen
2009-11-25 22:29 ` Richard Sharpe
2009-11-26 14:19 ` Ofer Heifetz
2009-11-26 14:24 ` Christoph Hellwig
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=4B096C6E.8010508@sandeen.net \
--to=sandeen@sandeen.net \
--cc=oferh@marvell.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