From: Carsten Oberscheid <oberscheid@doctronic.de>
To: xfs@oss.sgi.com
Subject: Re: Strange fragmentation in nearly empty filesystem
Date: Tue, 27 Jan 2009 08:10:23 +0100 [thread overview]
Message-ID: <20090127071023.GA16511@doctronic.de> (raw)
In-Reply-To: <497E02CD.2020000@sandeen.net>
On Mon, Jan 26, 2009 at 12:37:01PM -0600, Eric Sandeen wrote:
>
> It's possible that vmware changed too, I suppose. If it's leaving holes
> now, you won't get back to one extent.
Point taken.
> How hard would it be to boot a kernel from a year ago, with your current
> vmware, and see how that goes - it might be an interesting test.
Indeed. Unfortunately, since this is my office desktop PC, I'm quite
reluctant to fiddle around with it too much. But perhaps I find an
older live CD to try this with.
> I'd try to sort out the 2 moving parts you have, vmware & kernel. See
> which one seems to have affected this behavior the most; downgrade one
> of the 2 pieces, and see how it behaves.
Sounds perfectly reasonable.
So I understand that there are no known issues with XFS that might
explain this long term fragmentation behaviour, and that there are no
magic XFS options to improve it.
I'll see what tests I can do and report back about the findings.
Thank you & best regards
Carsten Oberscheid
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-27 8:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 10:21 Strange fragmentation in nearly empty filesystem Carsten Oberscheid
2009-01-23 15:25 ` Eric Sandeen
2009-01-24 0:33 ` Dave Chinner
2009-01-26 7:57 ` Carsten Oberscheid
2009-01-26 18:37 ` Eric Sandeen
2009-01-27 7:10 ` Carsten Oberscheid [this message]
2009-01-27 8:40 ` Carsten Oberscheid
2009-01-27 9:30 ` Michael Monnerie
2009-01-27 14:39 ` Carsten Oberscheid
2009-01-27 13:30 ` Eric Sandeen
2009-01-27 14:37 ` Carsten Oberscheid
2009-01-27 15:41 ` Felix Blyakher
2009-01-27 17:26 ` Eric Sandeen
2009-01-27 17:42 ` Felix Blyakher
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=20090127071023.GA16511@doctronic.de \
--to=oberscheid@doctronic.de \
--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