linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Marley <bobmarley@shiftmail.org>
To: "Hugo Mills" <hugo@carfax.org.uk>,
	"Swâmi Petaramesh" <swami@petaramesh.org>,
	"Linux Btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS, getting darn slower everyday
Date: Sun, 09 Dec 2012 23:51:36 +0100	[thread overview]
Message-ID: <50C515F8.6020801@shiftmail.org> (raw)
In-Reply-To: <20121209113824.GE14469@carfax.org.uk>

On 12/09/12 12:38, Hugo Mills wrote:
> On Sun, Dec 09, 2012 at 12:20:46PM +0100, Swâmi Petaramesh wrote:
>> Le 09/12/2012 11:41, Roman Mamedov a écrit :
>>> CoW filesystem incurs fragmentation by its nature, not specifically snapshots.
>>> Even without snapshots, rewriting portions of existing files will write the
>>> new blocks not over the original ones, but elsewhere, thus increasing
>>> fragmentation.
>> Is it to expect that somewhere in the future, BTRFS will be able to
>> defragment itself without duplicating snapshot data ?
>     In the presence of snapshots that are modified, no, it's impossible
> to fully defrag all the files.

Of course, but I would agree with the poster that it would be important 
to "partially" defrag all the files, avoiding at least unneeded 
fragmentation...
At least the fragmentation generated by normal writes

  reply	other threads:[~2012-12-09 22:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07  9:26 BTRFS, getting darn slower everyday Swâmi Petaramesh
2012-10-07 10:59 ` Martin Steigerwald
2012-10-07 14:05   ` Swâmi Petaramesh
2012-10-07 14:48     ` Martin Steigerwald
2012-10-08  6:16       ` Swâmi Petaramesh
2012-12-09  5:17       ` Jan Engelhardt
2012-12-09 10:13         ` Martin Steigerwald
2012-12-09 10:41         ` Roman Mamedov
2012-12-09 11:20           ` Swâmi Petaramesh
2012-12-09 11:38             ` Hugo Mills
2012-12-09 22:51               ` Bob Marley [this message]
2012-12-09 14:38           ` Jan Engelhardt
2012-10-07 11:02 ` Martin Steigerwald
2012-10-07 12:33 ` Alex
2012-10-07 13:19   ` Swâmi Petaramesh
2012-10-07 14:44     ` Martin Steigerwald
2012-10-07 22:47       ` Goffredo Baroncelli
2012-10-08  6:08         ` Swâmi Petaramesh
2012-10-08 11:38           ` Goffredo Baroncelli
2012-10-08 13:36             ` Swâmi Petaramesh
2012-10-08 15:50             ` Swâmi Petaramesh
2012-10-08 16:46               ` Goffredo Baroncelli
2012-10-08  6:22       ` Swâmi Petaramesh
2012-11-14 16:17     ` Peter Maloney
2012-10-07 13:00 ` Martin Steigerwald
2012-10-07 13:14   ` Swâmi Petaramesh
2012-10-07 14:41     ` Martin Steigerwald
2012-10-08 16:09 ` Josef Bacik
2012-10-08 16:15   ` Swâmi Petaramesh
2012-10-08 16:31     ` Josef Bacik

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=50C515F8.6020801@shiftmail.org \
    --to=bobmarley@shiftmail.org \
    --cc=hugo@carfax.org.uk \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=swami@petaramesh.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).