linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernhard Duebi <bernhard@due.bi>
To: David Nicol <davidnicol@gmail.com>
Cc: Hugo Mills <hugo@carfax.org.uk>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs defra
Date: Fri, 17 Jun 2011 14:19:27 +0200	[thread overview]
Message-ID: <1308313167.2504.157.camel@andromeda> (raw)
In-Reply-To: <BANLkTim-gxATkTSgGncJcc_WC4RHvtibWg@mail.gmail.com>

On Thu, 2011-06-16 at 08:50 -0500, David Nicol wrote:
> >   Defrag works on individual files, and tries to find a contiguous
> > sequence of bytes to write the file's data to. In the process, the
> > current implementation will break any CoW duplication -- either within
> > single files (copies with cp --reflink=always) or files copied via
> > snapshotting.
> 
> 
> While it's obviously impossible to defrag and maintain deduplicated
> partial chunks simultaneously without some kind of compromise (the
> ideal form of which is just beyond the reach of this list
> participant's obviousness flashlight),  how difficult is it going to
> be to modify the current defrag implementation to hip the additional
> references to the file to the fact that a contiguous version (of an
> individual file) is now available and it's time to update their links
> too, after each file with multiple reflinks/snapshots to its current
> form has been copied to contiguous space?
> 
> Could Bernhard Duebi do it?

Unfortunately not, I'm just a system engineer with interest in storage.
I'm sorry to disapoint you.

Sincerely
Bernhard




      reply	other threads:[~2011-06-17 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-13 14:50 btrfs defra Bernhard Duebi
2011-06-13 15:54 ` Hugo Mills
2011-06-16 13:50   ` David Nicol
2011-06-17 12:19     ` Bernhard Duebi [this message]

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=1308313167.2504.157.camel@andromeda \
    --to=bernhard@due.bi \
    --cc=davidnicol@gmail.com \
    --cc=hugo@carfax.org.uk \
    --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).