xfs
[Top] [All Lists]

Re: xfs_fsr broken again?

To: Juha K Kallio <bunnyh@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: xfs_fsr broken again?
From: Chris Wedgwood <cw@xxxxxxxx>
Date: Mon, 7 Oct 2002 23:27:10 -0700
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <20021008061844.GA455@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
References: <20021008061844.GA455@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4i
On Tue, Oct 08, 2002 at 09:18:44AM +0300, Juha K Kallio wrote:

> I'm running a 2 days old CVS kernel, and 2 days old xfsprogs. The
> new xfs_fsr worked OK, before I upgraded the kernel too. After that,
> it just produces *lots* of lines like this:

What version of xfs_fsr do youi have? (xfs_fsr -v).

What kernel version (dmesg|grep ^SGI\ XFS)?

> could not pre-alloc tmp space: /.fsr/ag1/tmp427

This normally comes from a non-root user trying tro reserve space.
The trace seems to indicate yoiu are indeed root, so I wonder if you
have an old xfs_fsr somehow which setuid's to the file owner.

> I've included the strace output as an attachment.

You actually need 'strace -f' to follow forks.  You could also try
something like:

          strace -f -otrace.log xfs_fsr -v -d /path/to/fragmented.file



  --cw


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