From: Eric Sandeen <sandeen@sandeen.net>
To: Luca Olivetti <luca@ventoso.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] fix dir2 shortform structures on ARM old ABI
Date: Wed, 19 Mar 2008 07:53:14 -0500 [thread overview]
Message-ID: <47E10CBA.9020904@sandeen.net> (raw)
In-Reply-To: <47E0F746.1090508@ventoso.org>
Luca Olivetti wrote:
> En/na Josef 'Jeff' Sipek ha escrit:
>
>
>> Thanks for the heads up wrt ARM EABI.
>
> Well, I have a linkstation lspro, even if it's running now "freelink"
> (i.e. debian, oabi, for the linkstation
> http://buffalo.nas-central.org/index.php/FreeLink), it's using the
> stock, eabi[*], kernel (Linux lspro 2.6.12.6-arm1 #2 Mon Jul 23 22:35:39
> CEST 2007 armv5tejl GNU/Linux) and xfs works just fine.
yeah, it should. For my list of on-disk structures, arm eabi structure
layout is identical to ia64 - I don't think any heads up is needed.
> [*] though I think, but I'm not sure, it was not the real thing but
> something that marvell patched in.
>
> However, any later kernel I tried "breaks" xfs (that's why I originally
> subscribed to this list), i.e. I cannot see the contents of some directories
> (more details here:
> http://buffalo.nas-central.org/forums/viewtopic.php?p=35061#p35061)
do you still have that small fs image? I'll take a look. There was
also an arm get_unaligned issue which hit xfs in another spot,
http://marc.info/?l=git-commits-head&m=120433318323826&w=3
might be worth seeing if you still have trouble with that fix in place
(which is slated for 2.6.25)
-Eric
> The strange thing is that I can mount the failing image on i386, so it
> probably has the correct structures on disk.
>
> Maybe looking at what marvell/buffalo patched in that kernel could give
> some insight on the xfs issues with arm.
> Bye
next prev parent reply other threads:[~2008-03-19 12:56 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 23:49 [PATCH] fix dir2 shortform structures on ARM old ABI Andre Draszik
2008-03-19 0:23 ` Josef 'Jeff' Sipek
2008-03-19 11:21 ` Luca Olivetti
2008-03-19 12:53 ` Eric Sandeen [this message]
2008-03-19 14:11 ` Luca Olivetti
[not found] ` <47E11F4A.3090205@ventoso.org>
[not found] ` <47E12D20.4010901@sandeen.net>
2008-03-19 15:34 ` Luca Olivetti
2008-03-19 15:40 ` Eric Sandeen
[not found] ` <47E14FF1.2020100@sandeen.net>
2008-03-19 18:24 ` Luca Olivetti
-- strict thread matches above, loose matches on Subject: below --
2008-03-18 23:31 Andre Draszik
2008-03-19 3:18 ` Eric Sandeen
2008-03-19 3:40 ` Eric Sandeen
2008-03-19 5:11 ` Eric Sandeen
2008-03-19 5:31 ` Eric Sandeen
2008-03-20 0:35 ` Timothy Shimmin
2008-03-15 3:24 Eric Sandeen
2008-03-15 4:17 ` Josef 'Jeff' Sipek
2008-03-15 4:23 ` Eric Sandeen
2008-03-15 4:27 ` Josef 'Jeff' Sipek
2008-03-15 4:33 ` Eric Sandeen
2008-03-15 4:51 ` Josef 'Jeff' Sipek
2008-03-17 18:32 ` Eric Sandeen
2008-03-17 19:53 ` Josef 'Jeff' Sipek
2008-03-17 20:04 ` Eric Sandeen
2008-03-17 20:28 ` Josef 'Jeff' Sipek
2008-03-17 23:35 ` Timothy Shimmin
2008-03-17 23:42 ` Josef 'Jeff' Sipek
2008-03-18 4:31 ` Timothy Shimmin
[not found] ` <20080315043622.GA11547@puku.stupidest.org>
2008-03-15 4:45 ` Eric Sandeen
2008-03-20 3:02 ` Eric Sandeen
2008-05-05 7:38 ` Barry Naujok
2008-06-06 14:15 ` Eric Sandeen
2008-04-09 19:53 ` Eric Sandeen
2008-04-23 0:58 ` Eric Sandeen
2008-05-02 20:55 ` Eric Sandeen
2008-05-05 7:08 ` David Chinner
2008-05-05 13:07 ` Eric Sandeen
2008-05-06 4:21 ` Timothy Shimmin
2008-05-06 13:43 ` Eric Sandeen
2008-06-05 5:38 ` Eric Sandeen
2008-06-05 5:46 ` Mark Goodwin
2008-06-05 5:49 ` Eric Sandeen
2008-06-05 6:02 ` Mark Goodwin
2008-06-05 6:04 ` Mark Goodwin
2008-06-05 6:06 ` Eric Sandeen
2008-06-05 5:49 ` Chris Wedgwood
2008-06-05 5:52 ` Eric Sandeen
2008-06-05 6:34 ` 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=47E10CBA.9020904@sandeen.net \
--to=sandeen@sandeen.net \
--cc=luca@ventoso.org \
--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.