xfs
[Top] [All Lists]

Re: Is xfs_fsr broken for Linux 3.8-rc?

To: "Michael L. Semon" <mlsemon35@xxxxxxxxx>
Subject: Re: Is xfs_fsr broken for Linux 3.8-rc?
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Sun, 20 Jan 2013 22:55:22 +1100
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CAJzLF9mV-8h8XDGS_yJX=O+8_L0KOa7_TcziPqhCTH2yK4erJA@xxxxxxxxxxxxxx>
References: <CAJzLF9mV-8h8XDGS_yJX=O+8_L0KOa7_TcziPqhCTH2yK4erJA@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
On Fri, Jan 04, 2013 at 01:08:06AM -0500, Michael L. Semon wrote:
> Hi!  I upgraded the Linux kernel, glibc (to 2.17), and xfsprogs (to
> 3.1.9) on three 32-bit x86 PCs.  Only one of them was upgraded to
> Linux 3.8-rc2, and I get xfs_fsr output like this, regardless of which
> XFS filesystem on which xfs_fsr is used:
> 
> XFS_IOC_SWAPEXT failed: ino=1048813: Invalid argument
> 
> On this particular XFS filesystem (/var), xfs_repair made no
> difference, so I went through the whole
> xfsdump/umount/zero/mkfs.xfs/mount/xfsrestore cycle for the /var
> partition.  I got the lone fragmented file after a reboot.
> 
> Upgrading yet again to the git version of xfsprogs did not change things.
> 
> If you can reproduce this problem, could you tell me by which kernel
> or xfsprogs version this will be fixed?  Really, a fix isn't really
> needed, merely an assurance that XFS will still be production-ready
> when kernel 3.8 has its main release.

Hi michael,

Can you check that this patch fixes your problem?

http://oss.sgi.com/pipermail/xfs/2013-January/023636.html

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>