xfs
[Top] [All Lists]

Re: XFS (via CVS, last Thursday) and segfaulting on getfacl.

To: "Ken D'Ambrosio" <kend@xxxxxxxxxxxx>
Subject: Re: XFS (via CVS, last Thursday) and segfaulting on getfacl.
From: Nathan Scott <nathans@xxxxxxx>
Date: Tue, 16 Jul 2002 08:14:02 +1000
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <33881.10.20.1.45.1026758548.squirrel@kend-linux.xanoptix.com>
References: <87adosq2un.wl@khufu.rjmx.net> <33881.10.20.1.45.1026758548.squirrel@kend-linux.xanoptix.com>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.4i
hi Ken,

On Mon, Jul 15, 2002 at 02:42:28PM -0400, Ken D'Ambrosio wrote:
> Howdy, all.  I got the latest and greatest XFS on Thursday, and just tried

Did you get a new kernel and new tools?  (what does getfacl --version
say on your box?)

> something that's got me a bit confused.  I wanted to set ACLs on our Sales
> directory, recursively, so I did
> setfacl -m -R g:gSales:rwx Sales/ which spat back
> 
> setfacl: Option -m: Invalid argument near character 1
> 
> So I then tried reversing "-m" and "-R", and it seemed to work.  However,

Yep, -m needs an argument.

> now when I try to getfacl, I get:
> 
> [root@nebula shared]# getfacl Sales
> # file: Sales
> # owner: root
> # group: root
> Segmentation fault
> 
> Any suggestions as to a) where I screwed up, and b) how to fix it?

Make sure you have latest tools as well as kernel, if that doesn't
help (hopefully it will - I tried but can't reproduce this problem),
we'll need to get a getfacl core dump and start to analyse where its
going wrong.  Remember to type "limit coredumpsize unlimited" before
running getfacl, and then mail the core file to me.

thanks.

-- 
Nathan


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