From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o863NXNF148704 for ; Sun, 5 Sep 2010 22:23:33 -0500 Received: from mail.sandeen.net (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 37EBD4E985 for ; Sun, 5 Sep 2010 20:24:15 -0700 (PDT) Received: from mail.sandeen.net (64-131-60-146.usfamily.net [64.131.60.146]) by cuda.sgi.com with ESMTP id 3RF4Hsfu6yA0sIVJ for ; Sun, 05 Sep 2010 20:24:15 -0700 (PDT) Message-ID: <4C845EDE.3010806@sandeen.net> Date: Sun, 05 Sep 2010 22:24:14 -0500 From: Eric Sandeen MIME-Version: 1.0 Subject: Re: xfs on armv5 still with erroneous log in kernel 2.6.35.4 References: <4C835A34.9080008@googlemail.com> <20100906005230.GX7362@dastard> In-Reply-To: <20100906005230.GX7362@dastard> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Dave Chinner Cc: Marcus Osdoba , xfs@oss.sgi.com Dave Chinner wrote: > On Sun, Sep 05, 2010 at 10:52:04AM +0200, Marcus Osdoba wrote: >> Hello XFS mailinglist, >> >> On my armv5 device I like to use XFS for my simple home made nas, >> because I think it is ideal for low/medium performance CPUs. >> I searched the mailing archive about the usage of XFS on arm >> architecture. I figured out, that the patchset of James Bottomley >> was applied to the main line. So I expected xfs to run properly on >> arm. Unfortunatly I still run into this (known) error after writing >> some data on an xfs partition and remounting it: >> " >> SGI XFS with ACLs, security attributes, large block/inode numbers, >> no debug enabled >> SGI XFS Quota Management subsystem >> XFS mounting filesystem sda1 >> Starting XFS recovery on filesystem: sda1 (logdev: internal) >> XFS: xlog_recover_process_data: bad clientid >> XFS: log mount/recovery failed: error 5 >> XFS: log mount failed >> " >> >> Am I still forced to use the "hammer" approach (flushing buffers in >> xfs_buf.c) which was proposed in January 2010? Or did I misinterpret >> the logfile of the xfs component in the kernel (so no arm fixing >> patches were applied)? > > What kernel version are you running? The xfs-vipt branch was merged into > mainline in late February, so kernels from 2.6.34 onwards should be > OK. > > If it isn't ok, then we need to know exactly what ARM CPU arch you > are using, and if the old brute-force cache flushing hack fix the > problem or not. > >> Is xfs NOW be known to work on arm (e.g. armv5)? If so I like to >> complain. If not, I'm willing to test patches which might solve this >> issue. > > I don't know of any outstanding XFS specific issues on ARM, but I > don't have any ARM machines here that I can test on.... I do, and owe their donors some testing; if this is still failing on a kernel with the vipt stuff in place I'll haul them out and do some testing.. -Eric > Cheers, > > Dave. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs