From: David Nicol <davidnicol@gmail.com>
To: Hugo Mills <hugo@carfax.org.uk>, Bernhard Duebi <bernhard@due.bi>,
linux-btrfs@vger.kernel.org
Subject: Re: btrfs defra
Date: Thu, 16 Jun 2011 08:50:10 -0500 [thread overview]
Message-ID: <BANLkTim-gxATkTSgGncJcc_WC4RHvtibWg@mail.gmail.com> (raw)
In-Reply-To: <20110613155420.GA14384@carfax.org.uk>
> =C2=A0 Defrag works on individual files, and tries to find a contiguo=
us
> sequence of bytes to write the file's data to. In the process, the
> current implementation will break any CoW duplication -- either withi=
n
> single files (copies with cp --reflink=3Dalways) 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?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-16 13:50 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 [this message]
2011-06-17 12:19 ` Bernhard Duebi
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=BANLkTim-gxATkTSgGncJcc_WC4RHvtibWg@mail.gmail.com \
--to=davidnicol@gmail.com \
--cc=bernhard@due.bi \
--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).