Dne 21. 01. 19 v 11:32 Zdenek Kabelac napsal(a):
Dne 18. 01. 19 v 1:53 Davis, Matthew napsal(a):
Hi Zdenek,
I assumed that LVM thin snapshots would work like git branches.
Since git also uses diffs on the backend, and git is popular with
developers, the same kind of behaviour seems reasonable
On 1/26/19 10:14 PM, Andrei Borzenkov wrote:
> I attempt to put device nodes for volumes in sub-directory of /dev to
> avoid accidental conflict between device name and volume group and
> general /dev pollution. VxVM always did it, using /dev/vx as base
> directory, so I would use something like /d
Dne 25. 01. 19 v 18:33 Alexander 'Leo' Bergolth napsal(a):
Hi!
If I extend a raid1 LV using lvextend, the newly allocated space in the two
rimage devices isn't synced, just like if I had used the option --nosync.
As a result, a following raid check will report mismatches.
Hi
Please open B
Dne 26. 01. 19 v 22:14 Andrei Borzenkov napsal(a):
I attempt to put device nodes for volumes in sub-directory of /dev to
avoid accidental conflict between device name and volume group and
general /dev pollution. VxVM always did it, using /dev/vx as base
directory, so I would use something like /d
I attempt to put device nodes for volumes in sub-directory of /dev to
avoid accidental conflict between device name and volume group and
general /dev pollution. VxVM always did it, using /dev/vx as base
directory, so I would use something like /dev/lvm.
Option devices/dir sounds like exactly the r
Hi Zdenek,
When 'stripe_size' is the 'right size' - striped device should appear
> faster,
> but telling you what's the best size is some sort of 'black magic' :)
>
> Basically - strip size should match boundaries of thin-pool chunk sizes.
>
> i.e. for thin-pool with 128K chunksize - and 2 disks
