http://oss.sgi.com/bugzilla/show_bug.cgi?id=731
Summary: XFS IOCTL interface not consistent between 32 and 64 bit
kernels
Product: Linux XFS
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: trivial
Priority: P2
Component: xfsdump
AssignedTo: xfs-master@xxxxxxxxxxx
ReportedBy: hb@xxxxxxxxxxxx
This is not exactly a bug per se. However, it would be nice to have it fixed.
I have two machines with XFS file systems. One is an AMD64 which is running a 64
bit Linux kernel and 64 bit userland tools. The other was an AMD 32 bit machine
running a 32 bit Linux kernel and 32 bit userland tools. I upgraded the 32 bit
machine to a 64 bit CPU, and later I installed the same kernel from my first
machine.
The 32 bit userland works fine with the 64 bit kernel, via emulation. The only
program that doesn't work, so far, is xfs_fsr. If I try to run it I get this on
the console:
spatula ~ # xfs_fsr -v /
/ start inode=0
unable to get handle: /: Invalid argument
and this in dmesg:
ioctl32(xfs_fsr:14862): Unknown cmd fd(4) cmd(c01c5868){00} arg(ffa7f1fc) on /
If I copy the xfs_fsr binary over from my 64 bit machine (along with
libattr.so.1 and libhandle.so.1) then it works fine. So, presumably this is due
to the IOCTL interface differing on the 32 and 64 bit kernels. While this is
understandable, I think it's sub-optimal. If there's a good reason for it, then
you probably won't want to make any changes. However, there's a chance this is
unintentional. Therefore I thought I'd bring it to your attention.
The Kernel version is 2.6.17-gentoo-r8.
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|