From: Eric Sandeen <sandeen@sandeen.net>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_fsr not defragmenting: 'could not open tmp file'
Date: Fri, 13 Feb 2009 08:12:11 -0600 [thread overview]
Message-ID: <49957FBB.40900@sandeen.net> (raw)
In-Reply-To: <200902131014.59183@zmi.at>
Michael Monnerie wrote:
> On Freitag 13 Februar 2009 Richard Troxell wrote:
>> xfs_fsr is coming from xfsprogs 3.0.0
>> Linux kernel is 2.6.23.9
>> Architecture is x86_64, but xfs_fsr is 32bit.
>
> I'm not a dev, but I'd suggest trying the newest 2.6.28 kernel and see
> if the problem persists. There have been many fixes since your kernel.
>
> mfg zmi
Actually, yes. there were 32/64 issues until recently, and fsr was in
fact using an ioctl that did not have a 32-bit handler. These weren't
fixed until 2.6.29-rc1.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-02-13 14:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 3:15 xfs_fsr not defragmenting: 'could not open tmp file' Richard Troxell
2009-02-13 9:14 ` Michael Monnerie
2009-02-13 14:12 ` Eric Sandeen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49957FBB.40900@sandeen.net \
--to=sandeen@sandeen.net \
--cc=michael.monnerie@is.it-management.at \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox