| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS support for ARMv5 |
| From: | Richard Sharpe <realrichardsharpe@xxxxxxxxx> |
| Date: | Wed, 25 Nov 2009 14:29:00 -0800 |
| Cc: | Andy Poling <andy@xxxxxxxxxxx>, Ofer Heifetz <oferh@xxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=shwp2YD1oA8ojsgddilMEIBZ33ROnNmDX2vIPuQebjM=; b=DOtDGW9LT4gQDlz+ES8Ts4JoILY2boWiTJK/7cMjUjM9DQayueM01qlF5evjlleKdw 41irHJf6YICbIJdQmaZNOm+lZuUsCmud/K4PXqPL4FN8bn2Ezs/tXDLKitivyPddRKBl ZdMqo91pWN5Z8B1oI+9oRMyXldK4uxh7mQM/k= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GuEUNzIFTlu6s6zO0xgILkyOFhNq/Nu4NSDUHDqCIaeeUDrgBXVuPC6NQZ0m3SQlaN P6/cBMpbw5MdTerEPbPHVEpSNhRJ8Dxs/bR9uR+C+St9CgQx5FYsKJdmh3niQ1Z9SSuV D8iNsaoC2/c2UkRMCajjj3R/q3Pg1MwMlKk+8= |
| In-reply-to: | <20091125210611.GA12150@xxxxxxxxxxxxx> |
| References: | <14274282.01258546868484.JavaMail.root@wombat> <4B041AEE.4040506@xxxxxxxxxxx> <EE71107DF0D1F24FA2D95041E64AB9E8985A59F17F@xxxxxxxxxxxxxxxxxxx> <4B096C6E.8010508@xxxxxxxxxxx> <EE71107DF0D1F24FA2D95041E64AB9E8985A59F31F@xxxxxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0911251025490.28890@andydesk> <20091125210611.GA12150@xxxxxxxxxxxxx> |
On Wed, Nov 25, 2009 at 1:06 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Wed, Nov 25, 2009 at 10:30:09AM -0600, Andy Poling wrote: >> On Mon, 23 Nov 2009, Ofer Heifetz wrote: >>> Here is the dmesg I got for mount /dev/sda3 /mnt/usb: >>> SGI XFS with ACLs, security attributes, large block/inode numbers, no debug >>> enabled >>> XFS mounting filesystem sda3 >>> Starting XFS recovery on filesystem: sda3 (logdev: internal) >>> XFS: xlog_recover_process_data: bad clientid >>> XFS: log mount/recovery failed: error 5 >>> XFS: log mount failed >> >> See this thread in the archives for a patch that may fix this: >> >> http://oss.sgi.com/pipermail/xfs/2009-October/042805.html > > I don't think it's the case you found, although the symptoms are the > same. I'd rather guess this is a case of an architecture with virtually > indexed caches (can anyone confirm the cache architecture?) which The Marvell 78xx series uses a VIVT cache. I will have to consult the documentation about the 6281 (I think that was it). > doesn't cope too well with the way we use vmap to write into a buffer > through virtually mapped linear addresses, but then do block I/O using > the physical addresses of the individual pages. James Bottomley has a > patchset to fix this issue by introducing APIs that allow the > architecture specific memory management to cope with it. He're a > version I could quickly find, although newer ones have been posted > since: > > http://thread.gmane.org/gmane.linux.kernel.cross-arch/4364 > > The patchset is planned to get merged into Linux 2.6.33. > > _______________________________________________ > xfs mailing list > xfs@xxxxxxxxxxx > http://oss.sgi.com/mailman/listinfo/xfs > -- Regards, Richard Sharpe |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS support for ARMv5, Eric Sandeen |
|---|---|
| Next by Date: | Re: [PATCH] Prevent lookup from finding bad buffers, Eric Sandeen |
| Previous by Thread: | Re: XFS support for ARMv5, Eric Sandeen |
| Next by Thread: | RE: XFS support for ARMv5, Ofer Heifetz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |