All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Carsten Oberscheid <oberscheid@doctronic.de>
Cc: xfs@oss.sgi.com
Subject: Re: Strange fragmentation in nearly empty filesystem
Date: Fri, 23 Jan 2009 09:25:27 -0600	[thread overview]
Message-ID: <4979E167.2040806@sandeen.net> (raw)
In-Reply-To: <20090123102130.GB8012@doctronic.de>

Carsten Oberscheid wrote:
> Hi there,
> 
> I am experiencing my XFS filesystem degrading over time in quite a
> strange and annoying way. Googling "XFS fragmenation" tells me either
> that this does not happen or to use xfs_fsr, which doesn't really help
> me anymore -- see below. I'd appreciate any help on this.
> 
> Background: I am using two VMware virtual machines on my Linux
> desktop. These virtual machines store images of their main memory in
> .vmem files, which are about half a gigabyte in size for each of my
> VMs. The .vmem files are created when starting the VM, written when
> suspending it and read when resuming. I prefer suspendig and resuming
> over shutting down and booting again, so with my VMs these files can
> have a lifetime of several weeks.

I would suggest using xfs_bmap to look at the file layout, it will be
much more informative than filefrag.

I don't know how vmware is writing the files out (I don't use vmware, so
can't test) but I'd suggest looking at xfs_bmap output when it's first
created, and then also when it's first written (but perhaps before it
gets too horribly fragmented).

The first question I'd ask is whether it's a swiss-cheese looking sparse
file with many holes.

-Eric

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-01-23 15:26 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 [this message]
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
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=4979E167.2040806@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.