xfs
[Top] [All Lists]

Is xfs_fsr broken for Linux 3.8-rc?

To: xfs@xxxxxxxxxxx
Subject: Is xfs_fsr broken for Linux 3.8-rc?
From: "Michael L. Semon" <mlsemon35@xxxxxxxxx>
Date: Fri, 4 Jan 2013 01:08:06 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=i2WriRdH5hcGTuwXfLns9UkiSlsxT+PlJ7omW9DUkME=; b=eN8jjDilXm3ew19vQKZZHNn6JJHlwx0zzDaJ6MrKHILNcGsLIrgbisR14XFOMZsXgP bjYQX6pBQ1gQZQvbGW7r4i4/xULo87p/x6aDTLGcPKL5CEurzi8kWamM+1PMJrB0Mf0d dukgGc4C79qbjXYTFAI6WfY5T+IDx+Nd0zyeXc9fUejfu2pFBDmjsIy7ub0GpwCafZeo jsmrah6a8VVyKPvqg7UawUL3TSmaTgCZyZxEOEd1Wczn7tWb93srcN0BvJNZOHB8qz4Q J41JU8hcCaNRfHpcqSGtRHaKfyYSeyd0KnzBczA66BoXk7JB3uJ79/LgiqLT7UnGYnbz UpJw==
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.

Thanks!

Michael

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