From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: filefrag and btrfs filesystem defragment and maybe snapshots
Date: Fri, 2 Aug 2013 02:27:25 +0000 (UTC) [thread overview]
Message-ID: <pan$4a6c0$5f5b3ad0$c61266cc$feaf3eba@cox.net> (raw)
In-Reply-To: CAPs0BihZNQ1fY4syh-=Pqm_ekVwd7Fw+YhGuVgz0fcO=VUZrFw@mail.gmail. com
Sandy McArthur posted on Thu, 01 Aug 2013 17:18:50 -0400 as excerpted:
> While exploring some btrfs maintenance with respect to defragmenting I
> ran the following commands:
>
> # filefrag /path/to/34G.file /path/to/5.7G.file
> /path/to/34G.file: 2406 extents found
> /path/to/5.7G.file: 572 extents found
>
> Thinking those mostly static files could be less fragmented I ran:
> # btrfs filesystem defragment -c /path/to/34G.file
> # btrfs filesystem defragment -c /path/to/5.7G.file
>
> and to my surprise the number of fragments/extends doubled:
>
> # filefrag /path/to/34G.file /path/to/5.7G.file
> /path/to/34G.file: 6324 extents found
> /path/to/5.7G.file: 1079 extents found
>
> Did I actually improve these files?
>
> I do have a number rolling readonly snapshots on the subvolume these
> files are on. I can imagine how that might be related but I'm not sure.
> When the pre-defrag snapshots are purged will the filefrag extents count
> drop.
I can't answer the snapshot angle, but do you have btrfs compression
turned on? I've read that filefrag always sees btrfs compressed files of
sufficient size as fragmented, due to the way btrfs compression works.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next parent reply other threads:[~2013-08-02 2:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPs0BihZNQ1fY4syh-=Pqm_ekVwd7Fw+YhGuVgz0fcO=VUZrFw@mail.gmail. com>
2013-08-02 2:27 ` Duncan [this message]
2013-08-02 5:02 ` filefrag and btrfs filesystem defragment and maybe snapshots Sandy McArthur
2013-08-01 21:18 Sandy McArthur
2013-08-02 2:19 ` Liu Bo
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='pan$4a6c0$5f5b3ad0$c61266cc$feaf3eba@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).