Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 3.3.2018 v 19:32 Xen napsal(a): Zdenek Kabelac schreef op 28-02-2018 22:43: It still depends - there is always some sort of 'race' - unless you are willing to 'give-up' too early to be always sure, considering there are technologies that may write many GB/s... That

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 1.3.2018 v 13:48 Gionatan Danti napsal(a): On 01/03/2018 12:23, Zdenek Kabelac wrote: In general - for extX  it's remount read-only upon error - which works for journaled metadata - if you want same protection for 'data' you need to switch to rather expensive data journal

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 1.3.2018 v 10:52 Gionatan Danti napsal(a): On 01/03/2018 09:31, Zdenek Kabelac wrote: If the tool wanted to write  1sector  to 256K chunk that needed provisioning, and provisioning was not possible - after reboot - you will still see the 'old' content. > In case of filesystem,

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 1.3.2018 v 10:43 Gianluca Cecchi napsal(a): On Thu, Mar 1, 2018 at 9:31 AM, Zdenek Kabelac <mailto:zkabe...@redhat.com>> wrote: Also note - we are going to integrate VDO support - which will be a 2nd. way for thin-provisioning with different set of features - missing

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 1.3.2018 v 08:14 Gionatan Danti napsal(a): Il 28-02-2018 22:43 Zdenek Kabelac ha scritto: On default - full pool starts to 'error' all 'writes' in 60 seconds. Based on what I remember, and what you wrote below, I think "all writes" in the context above mean

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 28.2.2018 v 20:07 Gionatan Danti napsal(a): Hi all, Il 28-02-2018 10:26 Zdenek Kabelac ha scritto: Overprovisioning on DEVICE level simply IS NOT equivalent to full filesystem like you would like to see all the time here and you've been already many times explained that filesystem

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 27.2.2018 v 19:39 Xen napsal(a): Zdenek Kabelac schreef op 24-04-2017 23:59: I'm just currious -  what the you think will happen when you have root_LV as thin LV and thin pool runs out of space - so 'root_LV' is replaced with 'error' target. Why do you suppose

Re: [linux-lvm] The benefits of lvmlockd over clvmd?

Dne 10.1.2018 v 15:42 Eric Ren napsal(a): Zdenek, Thanks for helping make this more clear to me :) There are couple fuzzy sentences - so lets try to make them more clear. Default mode for 'clvmd' is to 'share' resource everywhere - which clearly comes from original 'gfs' requirement and 'li

Re: [linux-lvm] The benefits of lvmlockd over clvmd?

Dne 10.1.2018 v 08:11 Eric Ren napsal(a): Hi David, Thanks for your explanations! On 01/10/2018 12:06 AM, David Teigland wrote: On Tue, Jan 09, 2018 at 11:15:24AM +0800, Eric Ren wrote: Hi David, Regarding the question of the subject, I can think of three main benefits of lvmlockd over clvmd

Re: [linux-lvm] lvm filter regex format

Dne 18.12.2017 v 19:53 matthew patton napsal(a):   https://github.com/jthornber/lvm2-ejt/blob/master/libdm/regex/parse_rx.h not to be ungrateful but why on earth would one NOT use the glibc standard regex library? Nobody cares about pointless optimization. Surprises like "well, we only imple

Re: [linux-lvm] LVM2 - pvresize alert

Dne 12.12.2017 v 14:13 VESELÍK Jan napsal(a): Hello, I would like to suggest small tweak in command pvresize. If you use parameter –setphysicalvolumesize, you will get only pasive wargning with this potentially dangerous action. In comparrison to lvresize with parameter –L -, meaning making l

Re: [linux-lvm] Why LVM doesn't send the dm-thin delete message immediately after volume creation failure

Dne 4.12.2017 v 05:30 Ming-Hung Tsai napsal(a): Hi All, I'm not sure if it is a bug or an intention. If there's error in volume creation, the function _lv_create_an_lv() invokes lv_remove() to delete the newly created volume. However, in the case of creating thin volumes, it just queues a "delet

Re: [linux-lvm] Reattach cache

Dne 22.11.2017 v 11:15 Xen napsal(a): Zdenek Kabelac schreef op 22-11-2017 10:57: In your case - just destroy the cache (--uncache) and do not try to reuse cache-pool unless you really know what you are doing. But I still don't know how to clean the metadata manually. Just drop/lvr

Re: [linux-lvm] Reattach cache

Dne 22.11.2017 v 09:55 Xen napsal(a): Ehm, When you split a cache and later reattach it, LVM ensures it is in a consistent state right? LVM is a bit old, I mean Ubuntu 16.04 version, so something about 133. Hi Sorry but version 133 is really ancient - the original purpose of 'cache' --sp

Re: [linux-lvm] LVM hangs

Dne 16.11.2017 v 12:02 Alexander 'Leo' Bergolth napsal(a): On 2017-11-13 15:51, Zdenek Kabelac wrote: Dne 13.11.2017 v 14:41 Alexander 'Leo' Bergolth napsal(a): I have a EL7 desktop box with two sata harddisks and two ssds in a LVM raid1 - thin pool - cache configuratio

Re: [linux-lvm] LVM hangs

Dne 13.11.2017 v 18:41 Gionatan Danti napsal(a): On 13/11/2017 16:20, Zdenek Kabelac wrote: Are you talking about RH bug 1388632? https://bugzilla.redhat.com/show_bug.cgi?id=1388632 Unfortunately I can only view the google-cached version of the bugzilla page, since the bug is restricted to

Re: [linux-lvm] LVM hangs

Dne 13.11.2017 v 16:12 Alexander 'Leo' Bergolth napsal(a): Hi! On 11/13/2017 03:51 PM, Zdenek Kabelac wrote: Dne 13.11.2017 v 14:41 Alexander 'Leo' Bergolth napsal(a): I have a EL7 desktop box with two sata harddisks and two ssds in a LVM raid1 - thin pool - cache

Re: [linux-lvm] LVM hangs

Dne 13.11.2017 v 14:41 Alexander 'Leo' Bergolth napsal(a): Hi! I have a EL7 desktop box with two sata harddisks and two ssds in a LVM raid1 - thin pool - cache configuration. (Just migrated to this setup a few weeks ago.) After some days, individual processes start to block in disk wait. I don'

Re: [linux-lvm] 答复: [dm-devel] dmsetup hangs forever

Dne 27.10.2017 v 10:00 Zhangyanfei (YF) napsal(a): Hello If the udevd daemon would not timeout, I think dmsetup mandatory wait udev finalizing any timeouts is good idea. But udevd would timeout in 180 sencond and kill the event process( systemd-udevd[39029]: timeout: killing). In this situation

Re: [linux-lvm] [dm-devel] dmsetup hangs forever

Dne 26.10.2017 v 10:07 Zhangyanfei (YF) napsal(a): Hello I find an issue when use  dmsetup in the situation udev event timeout. Dmsetup use the dm_udev_wait function sync with udev event.When use the dmsetup generate a new dm-disk, if the raw disk is abnormal(for example ,a ipsan disk hung IO

Re: [linux-lvm] unable to remove snapshot of raid1 leg

Dne 23.10.2017 v 18:40 Alexander 'Leo' Bergolth napsal(a): On 10/23/2017 04:44 PM, Heinz Mauelshagen wrote: LVM snapshots are meant to be used on the user visible raid1 LVs. You found a bug allowing it to be used on its hidden legs. Removing such per leg snapshot should be possible after the ra

Re: [linux-lvm] cache on SSD makes system unresponsive

Dne 21.10.2017 v 16:33 Oleg Cherkasov napsal(a): On 20. okt. 2017 21:35, John Stoffel wrote: "Oleg" == Oleg Cherkasov writes: Oleg> On 19. okt. 2017 21:09, John Stoffel wrote: Oleg> RAM 12Gb, swap around 12Gb as well.  /dev/sda is a hardware RAID1, the Oleg> rest are RAID5. Interesting,

Re: [linux-lvm] Difference between Debian and some other distributions with thin provisioning

Dne 29.9.2017 v 18:42 Jan Tulak napsal(a): Hi guys, I found out this difference and I'm not sure what is the cause. A command for creating a thin LV, which works on Archlinux, Centos and Fedora, fails on Debian and Ubuntu: lvm lvcreate FOOvg1 \ -T \ -l 100%PVS \ -n FOOvg1_thin001

Re: [linux-lvm] Restoring snapshot gone bad

Dne 22.9.2017 v 08:03 Mauricio Tavares napsal(a): I have a lv, vmzone/desktop that I use as drive for a kvm guest; nothing special here. I wanted to restore its snapshot so like I have done many times before I shut guest down and then lvconvert --merge vmzone/desktop_snap_20170921 Logical vol

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 21.9.2017 v 16:49 Xen napsal(a): However you would need LVM2 to make sure that only origin volumes are marked as critical. 'dmeventd' executed binary - which can be a simple bash script called at threshold level can be tuned to various naming logic. So far there is no plan to enforce '

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 21.9.2017 v 12:22 Xen napsal(a): Hi, thank you for your response once more. Zdenek Kabelac schreef op 21-09-2017 11:49: Hi Of course this decision makes some tasks harder (i.e. there are surely problems which would not even exist if it would be done in kernel)  - but lots of other

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 20.9.2017 v 15:05 Xen napsal(a): Gionatan Danti schreef op 18-09-2017 21:20: Xen, I really think that the combination of hard-threshold obtained by setting thin_pool_autoextend_threshold and thin_command hook for user-defined script should be sufficient to prevent and/or react to full thin

Re: [linux-lvm] Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"

Dne 19.9.2017 v 16:14 David Teigland napsal(a): On Tue, Sep 19, 2017 at 01:11:09PM +0200, Zdenek Kabelac wrote: IMHO the most convenient in my eyes is a usage of some sort of 'envvar' LVM_SUPPRESS_POOL_WARNINGS I think we're looking at the wrong thing. The root proble

Re: [linux-lvm] Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"

Dne 19.9.2017 v 16:34 matthew patton napsal(a): LVM and thin in particular is not for noobies or novices. If they get burned then they deserve it for using a technology they didn't bother to study and learn Well it's not for novices ;) yet I believe 'lvm2' should not be an easy weapon for mas

Re: [linux-lvm] Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"

Dne 19.9.2017 v 10:49 Gionatan Danti napsal(a): On 18/09/2017 23:10, matthew patton wrote: If the warnings are not being emitted to STDERR then that needs to be fixed right off the bat. The line with WARNINGs are written on STDERR, at least con recent LVM version. 'lvs -q blah' should squash

Re: [linux-lvm] Option to silence "WARNING: Sum of all thin volume sizes exceeds the size of thin pool"

Dne 18.9.2017 v 21:07 Gionatan Danti napsal(a): Il 18-09-2017 20:55 David Teigland ha scritto: It's definitely an irritation, and I described a configurable alternative here that has not yet been implemented: https://bugzilla.redhat.com/show_bug.cgi?id=1465974 Is this the sort of topic where w

Re: [linux-lvm] pvscan: bugs in manpage and implementation

Dne 18.9.2017 v 09:52 Tom Hale napsal(a): Hi, MAN PAGE In http://man7.org/linux/man-pages/man8/pvscan.8.html I see the following issues: * The string "-a--activate" appears several times. Should be: "-a|--activate" * "-a|--activate y|n|ay" is mentioned, but later on: "Only ay is applicable

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 17.9.2017 v 00:33 Xen napsal(a): Zdenek Kabelac schreef op 15-09-2017 11:22: lvm2 makes them look the same - but underneath it's very different (and it's not just by age - but also for targeting different purpose). - old-snaps are good for short-time small snapshots - whe

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 15.9.2017 v 10:15 matthew patton napsal(a): From the two proposed solutions (lvremove vs lverror), I think I would prefer the second one. I vote the other way. :) First because 'remove' maps directly to the DM equivalent action which brought this about. Second because you are in fact

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 15.9.2017 v 09:34 Xen napsal(a): Zdenek Kabelac schreef op 14-09-2017 21:05: But if I do create snapshots (which I do every day) when the root and boot snapshots fill up (they are on regular lvm) they get dropped which is nice, old snapshot are different technology for different

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 14.9.2017 v 07:59 Xen napsal(a): Zdenek Kabelac schreef op 13-09-2017 21:35: We are moving here in right direction. Yes - current thin-provisiong does not let you limit maximum number of blocks individual thinLV can address (and snapshot is ordinary thinLV) Every thinLV can address

Re: [linux-lvm] Performance penalty for 4k requests on thin provisioned volume

Dne 14.9.2017 v 12:57 Gionatan Danti napsal(a): On 14/09/2017 11:37, Zdenek Kabelac wrote: Sorry my typo here - is NOT ;) Zdenek Hi Zdenek, as the only variable is the LVM volume type (fat/thick vs thin), why the thin volume is slower than the thick one? I mean: all other things being

Re: [linux-lvm] Performance penalty for 4k requests on thin provisioned volume

Dne 14.9.2017 v 11:00 Zdenek Kabelac napsal(a): Dne 14.9.2017 v 00:39 Dale Stephenson napsal(a): On Sep 13, 2017, at 4:19 PM, Zdenek Kabelac wrote: md127 is an 8-drive RAID 0 As you can see, there’s no lvm striping; I rely on the software RAID underneath for that.  Both thick and thin

Re: [linux-lvm] Performance penalty for 4k requests on thin provisioned volume

Dne 14.9.2017 v 00:39 Dale Stephenson napsal(a): On Sep 13, 2017, at 4:19 PM, Zdenek Kabelac wrote: Dne 13.9.2017 v 17:33 Dale Stephenson napsal(a): Distribution: centos-release-7-3.1611.el7.centos.x86_64 Kernel: Linux 3.10.0-514.26.2.el7.x86_64 LVM: 2.02.166(2)-RHEL7 (2016-11-16) Volume

Re: [linux-lvm] Performance penalty for 4k requests on thin provisioned volume

Dne 13.9.2017 v 17:33 Dale Stephenson napsal(a): Distribution: centos-release-7-3.1611.el7.centos.x86_64 Kernel: Linux 3.10.0-514.26.2.el7.x86_64 LVM: 2.02.166(2)-RHEL7 (2016-11-16) Volume group consisted of an 8-drive SSD (500G drives) array, plus an additional SSD of the same size. The array

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 20:43 Xen napsal(a): There is something else though. You cannot set max size for thin snapshots? We are moving here in right direction. Yes - current thin-provisiong does not let you limit maximum number of blocks individual thinLV can address (and snapshot is ordinary thin

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 19:41 Xen napsal(a): Zdenek Kabelac schreef op 12-09-2017 23:57: Users interested in thin-provisioning are really mostly interested in performance - especially on multicore machines with lots of fast storage with high IOPS throughput  (some of them even expect it should be at

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 10:28 Gionatan Danti napsal(a): Il 13-09-2017 10:15 Zdenek Kabelac ha scritto: Ohh this is pretty major constrain ;) I can well imagine  LVM will let you forcible  replace such LV with error target  - so instead of  thinLV  - you will have  single 'error' targe

Re: [linux-lvm] Reserve space for specific thin logical volumes

D     # fsfreeze The above should have the result you want - essentially locking out all non-critical file systems.  The admin can easily turn them back on via fsfreeze one-by-one as they resolve the critical lack of space. If you find this too heavy-handed, perhaps try something else for inst

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 09:53 Gionatan Danti napsal(a): Il 13-09-2017 01:22 matthew patton ha scritto: Step-by-step example:  > - create a 40 GB thin volume and subtract its size from the thin pool (USED 40 GB, FREE 60 GB, REFER 0 GB);  > - overwrite the entire volume (USED 40 GB, FREE 60 GB, REFER 40

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 04:23 matthew patton napsal(a): I don't recall seeing an actual, practical, real-world example of why this issue got broached again. So here goes. Create a thin LV on KVM dom0, put XFS/EXT4 on it, lay down (sparse) files as KVM virtual disk files. Create and launch VMs and conf

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 02:04 matthew patton napsal(a): 'yes' The filesystem may not be resident on the hypervisor (dom0) so 'dmsetup suspend' is probably more apropos. How well that propagates upward to the unwary client VM remains to be seen. But if one were running a NFS server using thin+xfs/ext4

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 01:15 Gionatan Danti napsal(a): There could be a simple answer and complex one :) I'd start with simple one - already presented here - There you can decide - if you want to extend thin-pool... You may drop some snapshot... You may fstrim mounted thinLVs... You can kill volumes

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 00:55 Gionatan Danti napsal(a): Il 13-09-2017 00:41 Zdenek Kabelac ha scritto: There are maybe few worthy comments - XFS is great on stanadar big volumes, but there used to be some hidden details when used on thinly provisioned volumes on older RHEL (7.0, 7.1) So now it depend

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 13.9.2017 v 00:41 Gionatan Danti napsal(a): Il 13-09-2017 00:16 Zdenek Kabelac ha scritto: Dne 12.9.2017 v 23:36 Gionatan Danti napsal(a): Il 12-09-2017 21:44 matthew patton ha scritto: Again, please don't speak about things you don't know. I am *not* interested in thin pr

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 12.9.2017 v 19:09 Gionatan Danti napsal(a): Hi, The default combination is automatically the most tested one. This will really pay off when you face some unexptected bug/behavior And yet you persist on using the dumbest combo available: thin + xfs. No offense to LVM Thin, it works grea

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 12.9.2017 v 23:36 Gionatan Danti napsal(a): Il 12-09-2017 21:44 matthew patton ha scritto: Again, please don't speak about things you don't know. I am *not* interested in thin provisioning itself at all; on the other side, I find CoW and fast snapshots very useful. Not going to comment

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 12.9.2017 v 19:14 Gionatan Danti napsal(a): On 12/09/2017 16:37, Zdenek Kabelac wrote: ZFS with zpolls with thin with thinpools running directly on top of device. If zpools - are 'equally' fast as thins  - and gives you better protection, and more sane logic the why is still an

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 12.9.2017 v 14:47 Xen napsal(a): Zdenek Kabelac schreef op 12-09-2017 14:03: Unfortunatelly lvm2 nor dm  can be responsible for whole kernel logic and all user-land apps... What Gionatan also means, or at least what I mean here is, If functioning is chain and every link can be the

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 12.9.2017 v 14:37 Xen napsal(a): Zdenek Kabelac schreef op 12-09-2017 13:46: You know Zdenek, it often appears to me your job here is to dissuade people from having any wishes or wanting anything new. But if you look a little bit further, you will see that there is a lot more possible

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 12.9.2017 v 13:34 Gionatan Danti napsal(a): On 12/09/2017 13:01, Zdenek Kabelac wrote: There is very good reason why thinLV is fast - when you work with thinLV - you work only with data-set for single thin LV. Sad/bad news here - it's not going to work this way No, I absolutel

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 11.9.2017 v 15:46 Xen napsal(a): Zdenek Kabelac schreef op 11-09-2017 15:11: Thin-provisioning is - about 'postponing'  available space to be delivered in time That is just one use case. Many more people probably use it for other use case. Which is fixed storage spac

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 11.9.2017 v 23:59 Gionatan Danti napsal(a): Il 11-09-2017 12:35 Zdenek Kabelac ha scritto: The first question here is - why do you want to use thin-provisioning ? Because classic LVM snapshot behavior (slow write speed and linear performance decrease as snapshot count increases) make

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 11.9.2017 v 18:55 David Teigland napsal(a): On Mon, Sep 11, 2017 at 03:11:06PM +0200, Zdenek Kabelac wrote: Aye but does design have to be complete failure when condition runs out? YES I am not satisfied with the way thin pools fail when space is exhausted, and we aim to do better. Our

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 11.9.2017 v 16:00 Xen napsal(a): Just responding to second part of your email. Only manual intervention this one... and last resort only to prevent crash so not really useful in general situation? Let's simplify it for the case: You have  1G thin-pool You use 10G of thinLV on top of 1G t

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 11.9.2017 v 17:31 Eric Ren napsal(a): Hi Zdenek, On 09/11/2017 09:11 PM, Zdenek Kabelac wrote: [..snip...] So don't expect lvm2 team will be solving this - there are more prio work Sorry for interrupting your discussion. But, I just cannot help to ask: It's not the fi

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 11.9.2017 v 14:06 Xen napsal(a): Zdenek Kabelac schreef op 11-09-2017 13:20: Wondering from where they could get this idea... We always communicate clearly - do not plan to use 100% full unresizable thin-pool as a part of regular work-flow No one really PLANS for that. They probably

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 11.9.2017 v 12:55 Xen napsal(a): Zdenek Kabelac schreef op 11-09-2017 12:35: As thin-provisioning is about 'promising the space you can deliver later when needed'  - it's not about hidden magic to make the space out-of-nowhere. The idea of planning to operate thin-pool o

Re: [linux-lvm] Reserve space for specific thin logical volumes

Dne 10.9.2017 v 00:04 Gionatan Danti napsal(a): Il 08-09-2017 12:35 Gionatan Danti ha scritto: Hi list, as by the subject: is it possible to reserve space for specific thin logical volumes? This can be useful to "protect" critical volumes from having their space "eaten" by other, potentially mi

Re: [linux-lvm] lv raid - how to read this?

Dne 8.9.2017 v 13:00 Ming-Hung Tsai napsal(a): Oops, I mean, unsuitable for lvm-raid ... Excuses me, does that mean kernel md-raid module in kernel 4.1~4.5 are unstable or unsuitable for linux-md? Is there any reference threads? Yep - take my comments purely in context of lvm2 md core usa

Re: [linux-lvm] lv raid - how to read this?

Dne 8.9.2017 v 11:22 lejeczek napsal(a): On 08/09/17 09:49, Zdenek Kabelac wrote: Dne 7.9.2017 v 15:12 lejeczek napsal(a): On 07/09/17 10:16, Zdenek Kabelac wrote: Dne 7.9.2017 v 10:06 lejeczek napsal(a): hi fellas I'm setting up a lvm raid0, 4 devices, I want raid0 and I under

Re: [linux-lvm] lv raid - how to read this?

Dne 8.9.2017 v 11:22 lejeczek napsal(a): On 08/09/17 09:49, Zdenek Kabelac wrote: Dne 7.9.2017 v 15:12 lejeczek napsal(a): On 07/09/17 10:16, Zdenek Kabelac wrote: Dne 7.9.2017 v 10:06 lejeczek napsal(a): hi fellas I'm setting up a lvm raid0, 4 devices, I want raid0 and I under

Re: [linux-lvm] lv raid - how to read this?

Dne 8.9.2017 v 11:39 lejeczek napsal(a): On 08/09/17 10:34, Zdenek Kabelac wrote: Dne 8.9.2017 v 11:22 lejeczek napsal(a): On 08/09/17 09:49, Zdenek Kabelac wrote: Dne 7.9.2017 v 15:12 lejeczek napsal(a): On 07/09/17 10:16, Zdenek Kabelac wrote: Dne 7.9.2017 v 10:06 lejeczek napsal(a

Re: [linux-lvm] lv raid - how to read this?

Dne 7.9.2017 v 15:12 lejeczek napsal(a): On 07/09/17 10:16, Zdenek Kabelac wrote: Dne 7.9.2017 v 10:06 lejeczek napsal(a): hi fellas I'm setting up a lvm raid0, 4 devices, I want raid0 and I understand & expect - there will be four stripes, all I care of is speed. I do: $ lvcrea

Re: [linux-lvm] lv raid - how to read this?

Dne 7.9.2017 v 10:06 lejeczek napsal(a): hi fellas I'm setting up a lvm raid0, 4 devices, I want raid0 and I understand & expect - there will be four stripes, all I care of is speed. I do: $ lvcreate --type raid0 -i 4 -I 16 -n 0 -l 96%pv intel.raid0-0 /dev/sd{c..f} # explicitly four stripes

Re: [linux-lvm] Distributed Locking of LVM

Dne 31.8.2017 v 08:32 Kalyana sundaram napsal(a): Thanks all people I understand reboot/fencing is mandatory I hope the visibility might be better in external locking tool like redis With lvmlockd I find no deb available for ubuntu, and documentations for clvm to handle an issue is difficult to

Re: [linux-lvm] Distributed Locking of LVM

Dne 28.8.2017 v 14:41 Kalyana sundaram napsal(a): We have a shared iscsi disk at all our boxes, with one vg. We are using clvm to manage locks to create extend activate delete list. CLVM is tedious to manage especially especially due to reboot if locking is struck somewhere. Instead we are think

[linux-lvm] BUG: unable to handle kernel NULL pointer dereference in notifier_call_chain

Hi I've booted 4.13-rc1 a56e88ec05df50110f2bf578b6e17128f37111ed and seen this BUG report on boot of my T61 (C2D, 4G Ram, Fedora Rawhide): (not sure if the 2nd. sleep is side-effect - it could be possibly unrelated issue) audit: type=1131 audit(1500843225.056:150): pid=1 uid=0 auid=42949672

Re: [linux-lvm] convert LV to physical device _in_place_?

Dne 13.7.2017 v 15:25 Matthias Leopold napsal(a): hi, i'm fiddling around with LVM backed KVM raw disks, that i want to use _directly_ in oVirt virtualization (as "Direct LUN"). i would like to avoid "importing", dd, etc. if possible. in the KVM origin system exists a mapping of one iSCSI who

Re: [linux-lvm] LVM send/receive support?

Dne 5.6.2017 v 10:11 Gionatan Danti napsal(a): Hi all, I wonder if using LVM snapshots (even better: lvmthin snapshots, which are way faster) we can wire something like zfs or btrfs send/receive support. In short: take a snapshot, do a full sync, take another snapshot and sync only the change

Re: [linux-lvm] LVM send/receive support?

Dne 5.6.2017 v 10:48 Gionatan Danti napsal(a): Hi Zdenek, thanks for pointing me to thin_delta - very useful utility. Maybe I can code around it... As an additional question, is direct lvm2 support for send/receive planned, or not? Hi It will certainly happen - just not sure in which year.

Re: [linux-lvm] lvm.conf parameter for PVs to use for lvcreate ?

Dne 23.5.2017 v 17:57 Oliver Rath napsal(a): Hi list, if I use mulitiple PVs, Im able to select these PVs which should be used by my lv, i.e. lvcreate --size 10G --name mylv myvg /dev/sda3 /dev/sdb3 Is it possible to set these "/dev/sda3 /dev/sdb3" as default in lvm.conf if nothing is explicit

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 16.5.2017 v 09:53 Gionatan Danti napsal(a): On 15/05/2017 17:33, Zdenek Kabelac wrote:> Ever tested this: mount -o errors=remount-ro,data=journal ? Yes, I tested it - same behavior: a full thinpool does *not* immediately put the filesystem in a read-only state, even when using s

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 15.5.2017 v 16:48 Gionatan Danti napsal(a): On 15/05/2017 14:50, Zdenek Kabelac wrote> Hi What I does not understand is how XFS and EXT4 differs when a thinp is full. From a previous your reply, after I asked how to put thinp in read only mode when full: "Using 'ext4

Re: [linux-lvm] Howto change cachepolicy on cached thinpool devices?

Dne 15.5.2017 v 15:25 Oliver Rath napsal(a): Hi list, caching the _tdata part of a thinpool works fine now. Unfortunatly with lvchange it is not possible to change the policy (vg:dmivg, cachepool:dmipool,thinpool:winthinpool): # lvchange --cachepolicy cleaner dmivg/dmicache Operation not per

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 14.5.2017 v 22:39 Gionatan Danti napsal(a): Il 12-05-2017 15:42 Joe Thornber ha scritto: On Fri, May 12, 2017 at 03:02:58PM +0200, Gionatan Danti wrote: On 02/05/2017 13:00, Gionatan Danti wrote: >>Anyway, I think (and maybe I am wrong...) that the better solution is to >>fail *all* writes

Re: [linux-lvm] on discards

Dne 15.5.2017 v 05:16 Xen napsal(a): On discards, I have a thin pool that filled up when there was enough space, because the filesystem hadn't issued discards. I have ext4 mounted with the discard option, I hope, because it is in the list of default mount options of tune2fs: Default mount

Re: [linux-lvm] Sector size is assumed 512

Dne 11.5.2017 v 12:39 Tomasz Lasko napsal(a): Hi, I'm not a part of the list or the project, just a random guy dropping by to say I found one suspicious thing: after looking for what 's' size stands for, I found that your lvmcmdline.c source code

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 26.4.2017 v 15:37 Gionatan Danti napsal(a): On 26/04/2017 13:23, Zdenek Kabelac wrote: You need to use 'direct' write more - otherwise you are just witnessing issues related with 'page-cache' flushing. Every update of file means update of journal - so you surely c

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 26.4.2017 v 10:10 Gionatan Danti napsal(a): I'm not sure this is sufficient. In my testing, ext4 will *not* remount-ro on any error, rather only on erroneous metadata updates. For example, on a thinpool with "--errorwhenfull y", trying to overcommit data with a simple "dd if=/dev/zero of=

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 26.4.2017 v 09:26 Gionatan Danti napsal(a): Il 24-04-2017 23:59 Zdenek Kabelac ha scritto: If you set '--errorwhenfull y' - it should instantly fail. It's my understanding that "--errorwhenfull y" will instantly fail writes which imply new allocation reques

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 24.4.2017 v 23:02 Xen napsal(a): Zdenek Kabelac schreef op 23-04-2017 11:26: I'm just currious - what the you think will happen when you have root_LV as thin LV and thin pool runs out of space - so 'root_LV' is replaced with 'error' target. Why do you suppose

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 24.4.2017 v 15:49 Gionatan Danti napsal(a): On 22/04/2017 23:22, Zdenek Kabelac wrote: ATM there is even bug for 169 & 170 - dmeventd should generate message at 80,85,90,95,100 - but it does it only once - will be fixed soon... Mmm... quite a bug, considering how important is monito

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 23.4.2017 v 07:29 Xen napsal(a): Zdenek Kabelac schreef op 22-04-2017 23:17: That is awesome, that means a errors=remount-ro mount will cause a remount right? Well 'remount-ro' will fail but you will not be able to read anything from volume as well. Well that is still pre

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 22.4.2017 v 09:14 Gionatan Danti napsal(a): Il 14-04-2017 10:24 Zdenek Kabelac ha scritto: However there are many different solutions for different problems - and with current script execution - user may build his own solution - i.e. call 'dmsetup remove -f' for running thin vo

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 22.4.2017 v 18:32 Xen napsal(a): Gionatan Danti schreef op 22-04-2017 9:14: Il 14-04-2017 10:24 Zdenek Kabelac ha scritto: However there are many different solutions for different problems - and with current script execution - user may build his own solution - i.e. call 'dmsetup remo

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 15.4.2017 v 23:48 Xen napsal(a): Gionatan Danti schreef op 14-04-2017 20:59: There is something similar already in place: when pool utilization is over 95%, lvmthin *should* try a (lazy) umount. Give a look here: https://www.redhat.com/archives/linux-lvm/2016-May/msg00042.html Monitoring i

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 14.4.2017 v 11:07 Gionatan Danti napsal(a): Il 14-04-2017 10:24 Zdenek Kabelac ha scritto: But it's currently impossible to expect you will fill the thin-pool to full capacity and everything will continue to run smoothly - this is not going to happen. Even with EXT4 and errors=remou

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 14.4.2017 v 09:20 Gionatan Danti napsal(a): Il 13-04-2017 14:41 Xen ha scritto: See, you only compared multiple non-thin with a single-thin. So my question is: did you consider multiple thin volumes? Hi, the multiple-thin-volume solution, while being very flexible, is not well underst

Re: [linux-lvm] Snapshot behavior on classic LVM vs ThinLVM

Dne 13.4.2017 v 15:52 Xen napsal(a): Stuart Gathman schreef op 13-04-2017 14:59: If you are going to keep snapshots around indefinitely, the thinpools are probably the way to go. (What happens when you fill up those? Hopefully it "freezes" the pool rather than losing everything.) My experien

Re: [linux-lvm] stripped LV with segments vs one segment

Dne 10.4.2017 v 13:16 lejeczek napsal(a): On 10/04/17 12:03, Zdenek Kabelac wrote: Dne 10.4.2017 v 11:29 lejeczek napsal(a): hi there I could not extend my stripped LV, had 3 stripes and wanted to add one more. Only way LVM let me do it was where I ended up with this: --- Segments

Re: [linux-lvm] stripped LV with segments vs one segment

Dne 10.4.2017 v 11:29 lejeczek napsal(a): hi there I could not extend my stripped LV, had 3 stripes and wanted to add one more. Only way LVM let me do it was where I ended up with this: --- Segments --- Logical extents 0 to 751169: Typestriped Stripes3 Stripe siz

Re: [linux-lvm] root: Failed query for merging percentage. Aborting merge

Dne 9.4.2017 v 09:17 Roger Morton napsal(a): I wanted to merge a old snap shot (root_snap10) of my root file system back into root. LV VG Attr LSizePool Origin Data% Meta% Move Log Cpy%Sync Convert home_lv kubuntu-vg rwi-aor--- 1000.00g 100.00 root

Re: [linux-lvm] Possible bug in thin metadata size with Linux MDRAID

Dne 20.3.2017 v 12:52 Gionatan Danti napsal(a): On 20/03/2017 12:01, Zdenek Kabelac wrote: As said - please try with HEAD - and report back if you still see a problem. There were couple issue fixed along this path. Ok, I tried now with tools and library from git: LVM version: 2.02.169

Re: [linux-lvm] Possible bug in thin metadata size with Linux MDRAID

Dne 20.3.2017 v 11:45 Gionatan Danti napsal(a): On 20/03/2017 10:51, Zdenek Kabelac wrote: Please check upstream behavior (git HEAD) It will still take a while before final release so do not use it regularly yet (as few things still may change). I will surely try with git head and report

<    1   2   3   4   5   6   >