Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] lvm snapshot cloning



>> From: discuss-bounces+blu=nedharvey.com at blu.org [mailto:discuss-
>> bounces+blu=nedharvey.com at blu.org] On Behalf Of
>>
>> Other systems, chain snapshots so that at any time, only one snapshot is
>> receiving COW data, and the subsequent snapshots only forward reference.
>
> Also, other systems don't make you pre-allocate disk space for snapshot
> usage, and other systems don't automatically destroy your snapshot if you
> run out of pre-allocated space.  LVM snapshot is crap compared to other
> systems - but if you want to make a single snapshot so you can dump or tar
> your ext3/4 filesystem in a consistent state or something, then it's good
> for that purpose.  And not much else.

As I have said before, that, most of the time, copying the WHOLE volume is
not a practical option.

1TB at a very very fast rate of 160MB/s, copying a 1TB volume takes HOURS!

As for the pre-allocate space issue, yes, that is bad, but using alerts
and monitoring to increase allocated space will prevent the snapshot from
being nuked.

I'm not implying the LVM2 is great, but I do assert it is quite functional.
>
>
>





BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org