xfs
[Top] [All Lists]

Re: xfs_fsr allocation group optimization

To: Johan Andersson <johan@xxxxxxxxx>
Subject: Re: xfs_fsr allocation group optimization
From: Chris Wedgwood <cw@xxxxxxxx>
Date: Mon, 11 Jun 2007 08:58:24 -0700
Cc: xfs@xxxxxxxxxxx
In-reply-to: <1181558353.19145.76.camel@gentoo-johan.transmode.se>
References: <1181544692.19145.44.camel@gentoo-johan.transmode.se> <20070611073559.GA26257@tuatara.stupidest.org> <1181551409.19145.57.camel@gentoo-johan.transmode.se> <20070611090138.GA28907@tuatara.stupidest.org> <1181553356.19145.65.camel@gentoo-johan.transmode.se> <20070611094133.GA31108@tuatara.stupidest.org> <1181558353.19145.76.camel@gentoo-johan.transmode.se>
Sender: xfs-bounce@xxxxxxxxxxx
On Mon, Jun 11, 2007 at 12:39:13PM +0200, Johan Andersson wrote:

> In the way xfs_fsr operates now, in almost all user space, I don't
> see any good way to tell XFS where to place the extents, other than
> creating the temporary file in the same directory as the original
> file.

Exactly.

> My question is really, is there a better way than "find -xdev -inum"
> to find what file points to a given inode?

You can build then entire tree in-core using bulkstat and readdir,
doing the bulkstat first means you can try to optimize the order you
do the readdirs in somewhat.


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