On Thu, Jun 9, 2011 at 2:49 AM, Sunil Mushran <sunil.mushran@xxxxxxxxxx> 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@xxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
