On 01/21/2012 04:48 PM, Lars Ellenberg wrote:
Yet, it would be nice if the "utilization percentage" reported
for drbd device was meaningful.
Thanks for the reminder...
besides these stats not being very useful for "virtual" block devices
that do not have any queue anyways, it looks like our sta
Hi,
On 01/25/2012 02:26 PM, Oren Nechushtan wrote:
> Hi,
> Is there a built in way to keep snapshots on the same node?
> Namely, on each (e.g., of the two) nodes
> Allocate extra space in advance
> Configure DRBD to
> /dev/drbd0
> /dev/sda1 - active partition
> /dev/sda0 - dedicated for kee
Hi,
Is there a built in way to keep snapshots on the same node?
Namely, on each (e.g., of the two) nodes
Allocate extra space in advance
Configure DRBD to
/dev/drbd0
/dev/sda1 - active partition
/dev/sda0 - dedicated for keeping one snapshot
Take snapshot should be fast - much faster th
Oren,
AFAIK, DRBD doesnt support snapshotting natively. Therefore, if Im
correct, you only have 2 ways to achieve what you intend to do :
- Setup an VG/LV structure on top of your DRBD resource and make
use of the LVM snapshot facility. Beware, Ive read many articles mentioning
tha
Hi,Is there a built in way to keep snapshots?Namely, on each (e.g., of the two)
nodes Allocate space in advance Configure DRBD to /dev/drbd0 /dev/sda1 -
active partition /dev/sda0 - dedicated for keeping one snapshot Take snapshot
should be fast - much faster than ddAllow Reverting to th
On 01/25/2012 05:34 AM, Trey Dockendorf wrote:
> When the metadata is created the corresponding /dev/drbd0 resource is
> also created and that will replace /dev/vg_cllakvm2/lv_vmstore as what
> is mounted to the directory /vmstore ? So the block device can have
> data when it's made into a DRBD re
