From: Just Marc <marc@corky.net>
To: Barry Naujok <bnaujok@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs_fsr, performance related tweaks
Date: Fri, 29 Jun 2007 07:41:15 +0100 [thread overview]
Message-ID: <4684A98B.1030000@corky.net> (raw)
In-Reply-To: <op.tun7i8wd3jf8g2@pc-bnaujok.melbourne.sgi.com>
Barry Naujok wrote:
> On Fri, 29 Jun 2007 16:21:58 +1000, Just Marc <marc@corky.net> wrote:
>
>> Hi Eric,
>>
>> In my particular case, and I'm sure for many other people, files that
>> are stored never change again until they deleted. I hinted that
>> there could be a command line switch to turn this functionality on,
>> as it may not be perfect for everyone's use cases.
>>
>> If nobody likes this still, I would appreciate some hints on how to
>> mark files as no-defrag from within fsr itself given that I only have
>> the file descriptor ... A hack like looking up the descriptor in
>> /proc/self/fd should work, but is linux specific and is too hackish
>> in my opinion. I'd like to at least have a nice simple patch for my
>> own uses.
>
> Eric,
>
> You can use the xfs_io chattr command to mark known files as
> nodefrag. Using the chattr -R option can be used to recurse
> directories.
>
>
Barry,
That's right but I can't do this on a filesystem that's just been
defragged say a minute ago, and in the mean time 20 new files got added
(I don't know what these files are... ).
The whole filesystem has to be scanned again and here comes the issue:
fsr wants to try and reduce the extents of many files for which it can't
do it thus incurring lots of work and load until it can even reach the
new files do defrag them...
Marc
next prev parent reply other threads:[~2007-06-29 6:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 12:47 xfs_fsr, performance related tweaks Just Marc
2007-06-28 20:38 ` Eric Sandeen
2007-06-29 0:52 ` Andi Kleen
2007-06-29 6:21 ` Just Marc
2007-06-29 6:41 ` Barry Naujok
2007-06-29 6:41 ` Just Marc [this message]
2007-06-29 7:08 ` David Chinner
2007-06-29 7:16 ` Just Marc
2007-06-29 7:33 ` Nathan Scott
2007-06-29 7:41 ` David Chinner
2007-06-29 7:39 ` Just Marc
2007-06-30 17:17 ` Eric Sandeen
2007-07-01 22:43 ` David Chinner
-- strict thread matches above, loose matches on Subject: below --
2007-06-28 12:47 Just Marc
2007-06-29 0:12 ` Nathan Scott
2007-06-29 6:31 ` Just Marc
2007-06-29 8:13 ` Andi Kleen
2007-06-29 8:23 ` Just Marc
2007-06-29 8:58 ` Andi Kleen
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=4684A98B.1030000@corky.net \
--to=marc@corky.net \
--cc=bnaujok@sgi.com \
--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