xfs
[Top] [All Lists]

Re: xfs compat_ioctl?

To: Tim Walberg <twalberg@xxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
Subject: Re: xfs compat_ioctl?
From: Tim Walberg <twalberg@xxxxxxxxxxx>
Date: Wed, 2 Sep 2009 06:51:23 -0500
In-reply-to: <20090831190209.GD19343@xxxxxxxxxxx>
Mail-followup-to: Tim Walberg <twalberg@xxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, Linux-kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
References: <4A9B759B.7020401@xxxxxxxxxxxxxxxx> <20090831123010.GA2368@xxxxxxxxxxxxx> <20090831183751.GC19343@xxxxxxxxxxx> <20090831184822.GA10393@xxxxxxxxxxxxx> <20090831184918.GB10393@xxxxxxxxxxxxx> <20090831190209.GD19343@xxxxxxxxxxx>
Reply-to: Tim Walberg <twalberg@xxxxxxxxxxx>
User-agent: Mutt/1.5.16 (2007-06-09)
Ok, that patch has fixed my issues with xfs_fsr. Now I just need to
pull a new copy of xfs_progs to get the xfs_db alignment issue fix...


                Thanks,
                        tw


On 08/31/2009 14:02 -0500, Walberg, Tim wrote:
>>      
>>      
>>      On 08/31/2009 14:49 -0400, Christoph Hellwig wrote:
>>      >>      On Mon, Aug 31, 2009 at 02:48:22PM -0400, Christoph Hellwig 
>> wrote:
>>      >>      > On Mon, Aug 31, 2009 at 01:37:51PM -0500, Tim Walberg wrote:
>>      >>      > > Linux sparcy 2.6.30.4-sparcy #2 Sat Aug 1 21:14:46 CDT 2009 
>> sparc64 GNU/Linux
>>      >>      > > sparcy:~# file $(which xfs_fsr)
>>      >>      > > /usr/sbin/xfs_fsr: ELF 32-bit MSB executable, SPARC32PLUS, 
>> V8+ Required, version 1 (SYSV), dynamically linked (uses shared libs), for 
>> GNU/Linux 2.6.18, stripped
>>      >>      > 
>>      >>      > I'll take a look at that, thanks.
>>      >>      
>>      >>      Err, sorry - is that with the patch I posted in this thread or 
>> without?
>>      End of included message
>>      
>>      
>>      No, that's the generic 2.6.30.4... I can attempt with that patch as 
>> well, but
>>      it might be a day or two...
>>      
>>                                      tw
>>      


End of included message



-- 
twalberg@xxxxxxxxxxx

Attachment: pgpqBfHWSBP8c.pgp
Description: PGP signature

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