linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yongqiang Yang <xiaoqiangnk@gmail.com>
To: Sunil Mushran <sunil.mushran@oracle.com>
Cc: "Amir G." <amir73il@users.sourceforge.net>,
	Mike Snitzer <snitzer@redhat.com>,
	Lukas Czerner <lczerner@redhat.com>,
	linux-ext4@vger.kernel.org, tytso@mit.edu,
	linux-kernel@vger.kernel.org, sandeen@redhat.com
Subject: Re: LVM vs. Ext4 snapshots (was: [PATCH v1 00/30] Ext4 snapshots)
Date: Thu, 9 Jun 2011 10:05:42 +0800	[thread overview]
Message-ID: <BANLkTi=4=YkZezxkFh80JAwjH16Fu8PFXA@mail.gmail.com> (raw)
In-Reply-To: <4DEFC43B.1080802@oracle.com>

On Thu, Jun 9, 2011 at 2:49 AM, Sunil Mushran <sunil.mushran@oracle.com> wrote:
> On 06/08/2011 11:26 AM, Amir G. wrote:
>>
>> 2. Data blocks are never copied
>> The move-on-write technique is used to re-allocate data blocks on rewrite
>> instead of copying them.
>> This is not something that can be done when the snapshot is stored on
>> external storage, but it can done when the snapshot file lives in the fs.
>
> But does that not lead to fragmentation. And if I am understanding this,
> the fragmentation will not resolve after dropping the snapshot. So while
> you do save the overhead on write, you make the user pay on all future
> reads (that need to hit the disk).
Hi Sunil,

I am undertaking a project which aims to reduce fragmentation when the
file is rewritten.  When the snapshot is deleted, fragmentation
introduced by snapshot will be removed once the file is rewritten.  If
it is necessary, I think defragmentation can be done when the file is
read.

But it is not ready yet.  So it is not a part of the code which are
going to be merged.

Does I answer your question?
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>



-- 
Best Wishes
Yongqiang Yang
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2011-06-09  2:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-08 18:26 LVM vs. Ext4 snapshots (was: [PATCH v1 00/30] Ext4 snapshots) Amir G.
2011-06-08 18:49 ` Sunil Mushran
2011-06-09  2:05   ` Yongqiang Yang [this message]
2011-06-09 10:52 ` Christoph Hellwig
2011-06-09 11:44   ` Amir G.
2011-06-10  7:45 ` Amir G.
2011-06-10  8:08   ` Amir G.
2011-06-10  9:01     ` Lukas Czerner
2011-06-10 10:11       ` Joe Thornber
2011-06-10 14:15         ` Amir G.
2011-06-10 15:01           ` Joe Thornber
2011-06-11  4:01             ` Amir G.
2011-06-11  7:49               ` Joe Thornber
2011-06-11  8:18                 ` Alex Bligh
2011-06-11  9:44                   ` Amir G.
2011-06-11  5:41         ` Amir G.
2011-06-11  7:35           ` Joe Thornber
2011-06-11  9:58             ` Amir G.
2011-06-13  8:50               ` Joe Thornber

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='BANLkTi=4=YkZezxkFh80JAwjH16Fu8PFXA@mail.gmail.com' \
    --to=xiaoqiangnk@gmail.com \
    --cc=amir73il@users.sourceforge.net \
    --cc=lczerner@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=sunil.mushran@oracle.com \
    --cc=tytso@mit.edu \
    /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).