Re: [dm-devel] [PATCH] fix writing to the filesystem after unmount

Dne 08. 09. 23 v 13:32 Christian Brauner napsal(a): I'd say there are several options and we should aim towards the variant which is most usable by normal users. None of the options is sufficiently satisfying to risk intricate behavioral changes with unknown consequences for existing workloads

Re: [dm-devel] [PATCH] fix writing to the filesystem after unmount

Dne 08. 09. 23 v 12:20 Jan Kara napsal(a): On Fri 08-09-23 11:29:40, Zdenek Kabelac wrote: Dne 08. 09. 23 v 9:32 Jan Kara napsal(a): On Thu 07-09-23 14:04:51, Mikulas Patocka wrote: On Thu, 7 Sep 2023, Christian Brauner wrote: I think we've got too deep down into "how to fix things&quo

Re: [dm-devel] [PATCH] fix writing to the filesystem after unmount

Dne 08. 09. 23 v 9:32 Jan Kara napsal(a): On Thu 07-09-23 14:04:51, Mikulas Patocka wrote: On Thu, 7 Sep 2023, Christian Brauner wrote: I think we've got too deep down into "how to fix things" but I'm not 100% We did. sure what the "bug" actually is. In the initial posting Mikulas writes

Re: [dm-devel] [Question] Can DATA_DEV_BLOCK_SIZE_MIN_SECTORS be set to a smaller value

Dne 26. 06. 23 v 14:19 Li Lingfeng napsal(a): Hello: Recently, I found that the used space of the thin-pool will keep rising if I use dm-thin as follow: // create dm-thin dmsetup create linear_1 --table "0 2097152 linear /dev/sdc 0" dmsetup create linear_2 --table "0 16777216  linear

Re: [dm-devel] A hang bug of dm on s390x

Dne 16. 02. 23 v 9:30 Pingfan Liu napsal(a): Hi Ming, Thank you for looking into this. let me loop in Alasdair, Mike and Zdenek for further comment on LVM stuff Thanks, Pingfan Hi From lvm2 POV - couple clarifications - to let thin-pool auto-extend - user has to configure:

Re: [dm-devel] [PATCH 1/2] Fail I/O to thin pool devices

Dne 07. 02. 23 v 17:19 Demi Marie Obenour napsal(a): On Tue, Feb 07, 2023 at 03:02:51PM +, Joe Thornber wrote: Nack. I don't see the security issue; how is this any different from running the thin tools on any incorrect device? Or even the data device that the pool is mirroring. I

Re: [dm-devel] [PATCH 0/2] dm era: avoid deadlock when swapping table with dm-era target

Dne 19. 01. 23 v 10:36 Nikos Tsironis napsal(a): On 1/18/23 18:28, Mike Snitzer wrote: On Wed, Jan 18 2023 at  7:29P -0500, Nikos Tsironis wrote: Hi Mike, Thanks for the quick reply. I couldn't find this constraint documented anywhere and since the various DM targets seem to allow

Re: [dm-devel] Question about how to share dm-thin on multiple hosts

Dne 03. 11. 22 v 8:35 Zhiyong Ye napsal(a): Hi all, I am new to dm-devel. When using dm-thin via lvm, I found it difficult to share dm-thin on multiple hosts. The background is that I want to implement live migration of VMs in the lvm + iSCSI environment, in which lvmlockd is used to

Re: [dm-devel] A crash caused by the commit 0dd84b319352bb8ba64752d4e45396d8b13e6018

Dne 04. 11. 22 v 2:23 Guoqing Jiang napsal(a): On 11/3/22 10:46 PM, Heming Zhao wrote: On 11/3/22 11:47 AM, Guoqing Jiang wrote: Hi, On 11/3/22 12:27 AM, Mikulas Patocka wrote: Hi There's a crash in the test shell/lvchange-rebuild-raid.sh when running the lvm testsuite. It can be

Re: [dm-devel] setting up dmverity using device mapper IOCTLs

Dne 10. 09. 22 v 20:46 Pra.. Dew.. napsal(a): Hello, I need to setup dm-verity from my program-basically mount verity enabled filesystems from my code. I have looked at veritysetup and devicemapper (libdm) library. I was wondering if there is some simple C code to use the DM IOCTLs directly

Re: [dm-devel] Location for the definition of dm_task

Dne 12. 09. 22 v 7:55 Pra.. Dew.. napsal(a): I see that in libdevmapper.c following line is defined struct||dm_task|*|dmt|;| || |I cannot seem to find out where is dm_task and associated functions are

Re: [dm-devel] A kernel panic (or soft lockup) due to stack overflow by recursive dm-table reload

Dne 25. 08. 22 v 15:32 Mikulas Patocka napsal(a): On Thu, 25 Aug 2022, Zdenek Kabelac wrote: Since reproducing this issue is rather 'trival' - since creation of simple linear DM device and reloading it with 'self-reference' table line is easy I'd advocate for some simplistic check on kernel

Re: [dm-devel] A kernel panic (or soft lockup) due to stack overflow by recursive dm-table reload

Dne 24. 08. 22 v 21:42 Mikulas Patocka napsal(a): On Thu, 25 Aug 2022, Coly Li wrote: Hi folks, Recently I received a bug report from Intel developers (big thanks), the kernel panic is caused by a kernel stack overflow and it seems from a recursive dm-table reload. Here is the simplified

Re: [dm-devel] [PATCH 1/1] dm: add message command to disallow device open

Dne 15. 07. 22 v 11:36 Mikulas Patocka napsal(a): On Fri, 15 Jul 2022, Daniil Lunev wrote: Hi Mike, Thank you for your response. I should have probably added more context to the commit message that I specified in the cover letter. The idea is to prohibit access of all userspace, including the

Re: [dm-devel] Potential enhancements to dm-thin v2

Dne 12. 04. 22 v 16:29 David Teigland napsal(a): Dne 11. 04. 22 v 0:03 Demi Marie Obenour napsal(a): For quite a while, I have wanted to write a tool to manage thin volumes that is not based on LVM. On Tue, Apr 12, 2022 at 11:32:09AM +0200, Zdenek Kabelac wrote: Here is actually

Re: [dm-devel] Potential enhancements to dm-thin v2

Dne 12. 04. 22 v 0:30 Demi Marie Obenour napsal(a): On Mon, Apr 11, 2022 at 10:16:43PM +0200, Zdenek Kabelac wrote: Dne 11. 04. 22 v 19:22 Demi Marie Obenour napsal(a): On Mon, Apr 11, 2022 at 10:16:02AM +0200, Zdenek Kabelac wrote: Dne 11. 04. 22 v 0:03 Demi Marie Obenour napsal(a): Your

Re: [dm-devel] Potential enhancements to dm-thin v2

Dne 11. 04. 22 v 19:22 Demi Marie Obenour napsal(a): On Mon, Apr 11, 2022 at 10:16:02AM +0200, Zdenek Kabelac wrote: Dne 11. 04. 22 v 0:03 Demi Marie Obenour napsal(a): Your proposal actually breaks this sequence and would move things to the state of  'guess at which states we are now

Re: [dm-devel] Potential enhancements to dm-thin v2

Dne 11. 04. 22 v 0:03 Demi Marie Obenour napsal(a): For quite a while, I have wanted to write a tool to manage thin volumes that is not based on LVM. The main thing holding me back is that the current dm-thin interface is extremely error-prone. The only per-thin metadata stored by the kernel

Re: [dm-devel] Can not remove device. No files open, no processes attached. Forced to reboot server.

Dne 06. 02. 22 v 16:16 Aidan Walton napsal(a): Hi, I've been chasing a problem now for a few weeks. I have a flaky SATA controller that fails unpredictably and upon doing so all drives attached are disconnected by the kernel. I have 2 discs on this controller which are the components of a RAID1

Re: [dm-devel] Thin pool performance when allocating lots of blocks

Dne 08. 02. 22 v 22:02 Demi Marie Obenour napsal(a): On 2/8/22 15:37, Zdenek Kabelac wrote: Dne 08. 02. 22 v 20:00 Demi Marie Obenour napsal(a): Are thin volumes (which start as snapshots of a blank volume) efficient for building virtual machine images? Given the nature of this workload

Re: [dm-devel] Thin pool performance when allocating lots of blocks

Dne 08. 02. 22 v 20:00 Demi Marie Obenour napsal(a): Are thin volumes (which start as snapshots of a blank volume) efficient for building virtual machine images? Given the nature of this workload (writing to lots of new, possibly-small files, then copying data from them to a huge disk image), I

Re: [dm-devel] [PATCH] udev: create symlinks and watch even in suspended state

Dne 01. 02. 22 v 9:40 Martin Wilck napsal(a): On Mon, 2022-01-31 at 14:33 +0100, Peter Rajnoha wrote: (just discussed this with Zdenek too) The patch makes sense to me! We added all the DM_UDEV_PRIMARY_SOURCE_FLAG and related for exactly such cases where we need to take the existing values

Re: [dm-devel] [PATCH] udev: create symlinks and watch even in suspended state

Dne 29. 01. 22 v 0:21 Martin Wilck napsal(a): On Fri, 2022-01-28 at 22:06 +0100, Zdenek Kabelac wrote: Dne 28. 01. 22 v 19:46 Martin Wilck napsal(a): On Fri, 2022-01-28 at 18:47 +0100, Zdenek Kabelac wrote: Dne 28. 01. 22 v 17:02 Martin Wilck napsal(a): On Fri, 2022-01-28 at 16:57 +0100

Re: [dm-devel] [PATCH] udev: create symlinks and watch even in suspended state

Dne 28. 01. 22 v 19:46 Martin Wilck napsal(a): On Fri, 2022-01-28 at 18:47 +0100, Zdenek Kabelac wrote: Dne 28. 01. 22 v 17:02 Martin Wilck napsal(a): On Fri, 2022-01-28 at 16:57 +0100, Martin Wilck wrote: It's a race condition. It probably happens while multipathd is reloading a map

Re: [dm-devel] [PATCH] udev: create symlinks and watch even in suspended state

Dne 28. 01. 22 v 17:02 Martin Wilck napsal(a): On Fri, 2022-01-28 at 16:57 +0100, Martin Wilck wrote: It's a race condition. It probably happens while multipathd is reloading a map (*), suspending it during the table reload. The device will be resumed a few fractions of a second later (so yes,

Re: [dm-devel] [PATCH] udev: create symlinks and watch even in suspended state

Dne 28. 01. 22 v 14:42 mwi...@suse.com napsal(a): From: Martin Wilck If a dm device is suspended, we can't run blkid on it. But earlier rules (e.g. 11-dm-parts.rules) might have imported previously scanned properties from the udev db, in particular if the device had been correctly set up

Re: [dm-devel] Deadlock when swapping a table with a dm-era target

Dne 03. 12. 21 v 15:42 Nikos Tsironis napsal(a): On 12/2/21 5:41 PM, Zdenek Kabelac wrote: Dne 01. 12. 21 v 18:07 Nikos Tsironis napsal(a): Hello, Under certain conditions, swapping a table, that includes a dm-era target, with a new table, causes a deadlock. This happens when a status

Re: [dm-devel] Deadlock when swapping a table with a dm-era target

Dne 01. 12. 21 v 18:07 Nikos Tsironis napsal(a): Hello, Under certain conditions, swapping a table, that includes a dm-era target, with a new table, causes a deadlock. This happens when a status (STATUSTYPE_INFO) or message IOCTL is blocked in the suspended dm-era target. dm-era executes all

Re: [dm-devel] can we fix some dm snapshot crashes please? :)

Dne 07. 05. 21 v 12:31 Michael Tokarev napsal(a): Hi! I asked this 1.5 years ago, but go no replies. The thing is that we have a few bugs in kernel in snapshot-related area for years, maybe for decades, and the bugs are still there and it is still trivial to crash the kernel is you're not

Re: [dm-devel] [lvm-devel] master - multipathd: fix fd leak when iscsi device logs in

Dne 13. 07. 20 v 12:08 Martin Wilck napsal(a): Hi Zdenek, On Mon, 2020-07-13 at 11:56 +0200, Zdenek Kabelac wrote: Dne 13. 07. 20 v 11:21 Martin Wilck napsal(a): Hi Lixiaokeng, @Zdenek, do we have to protect every libdm call, or is it sufficient to protect only dm_task_run(), as lixiaokeng

Re: [dm-devel] [lvm-devel] master - multipathd: fix fd leak when iscsi device logs in

Dne 13. 07. 20 v 11:21 Martin Wilck napsal(a): Hi Lixiaokeng, @Zdenek, do we have to protect every libdm call, or is it sufficient to protect only dm_task_run(), as lixiaokeng suggested? Hi It's actually hard to answer it in a simple way. Several properties are held in library static

Re: [dm-devel] [git pull] device mapper fixes for 5.6-rc5

Dne 04. 03. 20 v 20:34 Linus Torvalds napsal(a): On Wed, Mar 4, 2020, 13:23 Mike Snitzer > wrote: These versions are for userspace's benefit (be it lvm2, cryptsetup, multipath-tools, etc).  But yes, these versions are bogus even for that -- primarily

Re: [dm-devel] dm-writecache: change config parameters using messages

Dne 07. 11. 19 v 20:50 Mikulas Patocka napsal(a): On Thu, 7 Nov 2019, Maged Mokhtar wrote: On 07/11/2019 21:09, Mike Snitzer wrote: On Thu, Nov 07 2019 at 1:55pm -0500, Maged Mokhtar wrote: On 06/11/2019 17:08, Mike Snitzer wrote: On Tue, Nov 05 2019 at 4:19pm -0500, Maged Mokhtar

Re: [dm-devel] Kernel error at a LVM snapshot creation

Dne 02. 09. 19 v 15:58 Dmitrij Gusev napsal(a): Hello. Please find answers below. Thank you. Dmitrij On 2019-09-02 11:32, Zdenek Kabelac wrote: Dne 02. 09. 19 v 3:04 Dmitrij Gusev napsal(a): Hello. I get a kernel error every time I create LVM snapshot - at the creation and at boot time

Re: [dm-devel] Kernel error at a LVM snapshot creation

Dne 02. 09. 19 v 3:04 Dmitrij Gusev napsal(a): Hello. I get a kernel error every time I create LVM snapshot - at the creation and at boot time, though the snapshot itself is working properly. Linux nexus 4.19.69 #2 SMP Thu Aug 29 16:33:35 CDT 2019 x86_64 Intel(R) Xeon(R) E-2174G CPU @

Re: [dm-devel] [PATCH v12] dm: add support to directly boot to a mapped device

Dne 04. 06. 19 v 21:35 Stephen Boyd napsal(a): Quoting Helen Koike (2019-06-04 10:38:59) On 6/3/19 8:02 PM, Stephen Boyd wrote: I'm trying to boot a mainline linux kernel on a chromeos device with dm verity and a USB stick but it's not working for me even with this patch. I've had to hack

Re: [dm-devel] max_sectors_kb limitations with VDO and dm-thin

Dne 19. 04. 19 v 16:40 Ryan Norwood napsal(a): We have been using dm-thin layered above VDO and have noticed that our performance is not optimal for large sequential writes as max_sectors_kb and max_hw_sectors_kb for all thin devices are set to 4k due to the VDO layer beneath. This

Re: [dm-devel] Possible bug in mirror target

Dne 13. 02. 19 v 16:01 Bryn M. Reeves napsal(a): On Wed, Feb 13, 2019 at 03:21:52PM +0100, Zdenek Kabelac wrote: If you have this free space it's surely not a bad thing - but there are many cases, you can get any free space - majority of filesystems does not support shrinking - so the only

Re: [dm-devel] Possible bug in mirror target

Hi Dne 12. 02. 19 v 23:36 John Stoffel napsal(a): "Zdenek" == Zdenek Kabelac writes: Zdenek> Dne 10. 02. 19 v 22:58 John Stoffel napsal(a): Zdenek> The old dm mirror works differently then new dm raid - so if Zdenek> you have an old one present/running (i.e. LVM mirr

Re: [dm-devel] Possible bug in mirror target

Dne 10. 02. 19 v 22:58 John Stoffel napsal(a): "Zdenek" == Zdenek Kabelac writes: Zdenek> Dne 05. 02. 19 v 1:47 Drew Hastings napsal(a): Hi, I'm assuming all user space code is expected to use the handle_errors feature, so this isn't that big of a deal. I'm also using 4.19.13,

Re: [dm-devel] Possible bug in mirror target

Dne 05. 02. 19 v 1:47 Drew Hastings napsal(a): Hi, I'm assuming all user space code is expected to use the handle_errors feature, so this isn't that big of a deal. I'm also using 4.19.13, which I think is more recent than the latest update to dm-raid1.c That said, there may be a bug that

Re: [dm-devel] dm thin pool discarding

Dne 10. 01. 19 v 16:23 Martin Wilck napsal(a): On Thu, 2019-01-10 at 16:08 +0100, Zdenek Kabelac wrote: Dne 10. 01. 19 v 14:41 Martin Wilck napsal(a): I for one would find it very attractive if dm-thin had a mode supporting fast zeroout. I believe '/sys/block/*/queue/discard_zeroes_data

Re: [dm-devel] dm thin pool discarding

Dne 10. 01. 19 v 12:40 Martin Wilck napsal(a): On Thu, 2019-01-10 at 10:18 +0100, Zdenek Kabelac wrote: Dne 10. 01. 19 v 1:39 james harvey napsal(a): Q3 - Does a LVM thin volume zero out the bytes that are discarded? At least for me, queue/discard_zeroes_data is 0. I see

Re: [dm-devel] dm thin pool discarding

Dne 10. 01. 19 v 1:39 james harvey napsal(a): I've been talking with ntfs-3g developers, and they're updating their discard code to work when an NTFS volume is within an LVM thin volume. It turns out their code was refusing to discard if discard_granularity was > the NTFS cluster size. By

Re: [dm-devel] device-mapper: ioctl: ioctl interface mismatch: kernel(4.37.0), user(4.39.0), cmd(16)

Dne 19.9.2018 v 17:30 Özkan Göksu napsal(a): Hello. After your mail I tried something; I just curious what will happen when I downgrade multipath-tools package and the rest was latest. lvm2 2.02.181-1 device-mapper 2.02.181-1 I just downgrade to: multipath-tools 0.7.6-1 Everything works

Re: [dm-devel] device-mapper: ioctl: ioctl interface mismatch: kernel(4.37.0), user(4.39.0), cmd(16)

Dne 19.9.2018 v 12:35 Özkan Göksu napsal(a): Hello. I just upgraded my Kernel to: 4.14.70-1-lts | device-mapper 2.02.181-1 | multipath-tools 0.7.7-1 After that multipathd started to giving the log: // device-mapper: ioctl: ioctl interface mismatch: kernel(4.37.0), user(4.39.0), cmd(16) It was

Re: [dm-devel] [RESEND PATCH v2] configure: Introduce --enable-symvers option

Dne 31.8.2018 v 16:48 Marcin Niestroj napsal(a): Only few libc (e.g. glibc) libraries support full symbol version resolution in runtime. There are lot of standard libraries that do not support that, such as dietlibc, musl and uclibc. Hence there is no reason to generate symbol versions when

Re: [dm-devel] dmsetup create linear with 4 devices not possible?

Dne 20.8.2018 v 11:06 Sverd Johnsen napsal(a): [40309.478954] device-mapper: table: 254:15: linear: Invalid argument count root@bar /tmp # vgchange -ay looptest Logging initialised at Mon Aug 20 11:00:05 2018 Activating logical volume looptest/testing. activation/volume_list

Re: [dm-devel] dmsetup create linear with 4 devices not possible?

Dne 20.8.2018 v 10:37 Sverd Johnsen napsal(a): hey how can i do the equivalent of making a lv across 4 pvs with plain dmsetup? i want this: # cat test.table 0 100 linear /dev/foo 0 100 100 linear /dev/bar 0 except with more than 2 devices..but it doesnt work. Have you checked reported

Re: [dm-devel] LVM snapshot broke between 4.14 and 4.16

Dne 3.8.2018 v 18:37 Linus Torvalds napsal(a): [ Dammit. I haven't had to shout and curse at people for a while, but this is ABSOLUTELY THE MOST IMPORTANT THING IN THE UNIVERSE WHEN IT COMES TO SOFTWARE DEVELOPMENT ] On Fri, Aug 3, 2018 at 6:31 AM Zdenek Kabelac wrote: IMHO (as the author

Re: [dm-devel] LVM snapshot broke between 4.14 and 4.16

Dne 2.8.2018 v 23:52 Linus Torvalds napsal(a): On Thu, Aug 2, 2018 at 2:39 PM WGH wrote: I've just found one public report of this bug, though: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900442 Yeah, it does sound like we should fix this issue. Hi IMHO (as the author of fixing

Re: [dm-devel] [PATCH 9/9] dm-integrity: recalculate checksums

Dne 3.7.2018 v 20:24 Mikulas Patocka napsal(a): On Tue, 3 Jul 2018, Milan Broz wrote: On 07/03/2018 03:21 PM, Mike Snitzer wrote: Should we even have the possibility to stop recalculating? If the device was recalculating and we activate it without the "recalculate" flag, what should it

Re: [dm-devel] dm-thin: Why is DATA_DEV_BLOCK_SIZE_MIN_SECTORS set to 64k?

Dne 9.6.2018 v 21:31 Eric Wheeler napsal(a): On Fri, 18 May 2018, Zdenek Kabelac wrote: Dne 18.5.2018 v 01:36 Eric Wheeler napsal(a): Hello all, Is there a technical reason that DATA_DEV_BLOCK_SIZE_MIN_SECTORS is limited to 64k? I realize that the metadata limits the maximum mappable pool

Re: [dm-devel] dm-thin: Why is DATA_DEV_BLOCK_SIZE_MIN_SECTORS set to 64k?

Dne 18.5.2018 v 01:36 Eric Wheeler napsal(a): Hello all, Is there a technical reason that DATA_DEV_BLOCK_SIZE_MIN_SECTORS is limited to 64k? I realize that the metadata limits the maximum mappable pool size, so it needs to be bigger for big pools---but it is also the minimum COW size. Looking

Re: [dm-devel] [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios

Dne 3.4.2018 v 06:07 Dennis Yang napsal(a): Hi, Recently we have came across an issue that dm-thin pool will be switched to READ_ONLY mode because dm_pool_alloc_data_block() returns -ENOSPC. AFAIK, this should not happen since alloc_data_block() will check if there is any free space (and commit

Re: [dm-devel] [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios

Dne 3.4.2018 v 11:31 Zdenek Kabelac napsal(a): Dne 3.4.2018 v 06:07 Dennis Yang napsal(a): Hi, Recently we have came across an issue that dm-thin pool will be switched to READ_ONLY mode because dm_pool_alloc_data_block() returns -ENOSPC. AFAIK, this should not happen since alloc_data_block

Re: [dm-devel] [BUG] dm-thin metadata operation failed due to -ENOSPC returned by dm_pool_alloc_data_block() after processing DISCARD bios

Dne 3.4.2018 v 06:07 Dennis Yang napsal(a): Hi, Recently we have came across an issue that dm-thin pool will be switched to READ_ONLY mode because dm_pool_alloc_data_block() returns -ENOSPC. AFAIK, this should not happen since alloc_data_block() will check if there is any free space (and commit

Re: [dm-devel] device mapper mapping across reboot

Dne 12.3.2018 v 12:09 Jitendra napsal(a): On Mon, Mar 12, 2018 at 10:49:02AM +0100, Zdenek Kabelac wrote: Dne 10.3.2018 v 11:47 Jitendra napsal(a): Once kernel is booted and 'ramdisk' is processed - you have plenty of time and lots of binaries there (typically with lvm2 built-in)  - so

Re: [dm-devel] device mapper mapping across reboot

Dne 10.3.2018 v 11:47 Jitendra napsal(a): lvm2 is exactly solving this problem as it maintains consistent 'metadata' on every device - so upon reboot devices are discovered and from their metadata dm tables are actived/restored. Got it. So  are you looking for recreation of all the lvm2

Re: [dm-devel] device mapper mapping across reboot

Dne 9.3.2018 v 10:58 jitendra kumar khasdev napsal(a): Hi All, I wrote the basic target using device mapper framework. Using dmsetup utility I am able to create device node under /dev/mapper/my_custom_mapper. But when I do reboot the system, it lost the mapping. Is there any way by which I

Re: [dm-devel] [PATCH 4/4] dm: convert table_device.count from atomic_t to refcount_t

Dne 20.10.2017 v 09:37 Elena Reshetova napsal(a): atomic_t variables are currently used to implement reference counters with the following properties: - counter is initialized to 1 using atomic_set() - a resource is freed upon counter reaching zero - once counter reaches zero, its further

Re: [dm-devel] Ideas to reuse filesystem's checksum to enhance dm-raid1/10/5/6?

Dne 16.11.2017 v 11:04 Qu Wenruo napsal(a): On 2017年11月16日 17:43, Zdenek Kabelac wrote: Dne 16.11.2017 v 09:08 Qu Wenruo napsal(a): [What we have] The nearest infrastructure I found in kernel is bio_integrity_payload. Hi We already have  dm-integrity target upstream. What's missing

Re: [dm-devel] Ideas to reuse filesystem's checksum to enhance dm-raid1/10/5/6?

Dne 16.11.2017 v 09:08 Qu Wenruo napsal(a): [What we have] The nearest infrastructure I found in kernel is bio_integrity_payload. Hi We already have dm-integrity target upstream. What's missing in this target ? Regards Zdenek -- dm-devel mailing list dm-devel@redhat.com

Re: [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

Re: [dm-devel] dm-thin chunk size

Dne 13.9.2017 v 21:18 Eivind Sarto napsal(a): I am considering using dm-thin for a project and have been running some performance tests. After a snapshot has been taken, writes to the existing blocks in the original volume appears to take a severe performance hit unless the blocks written are

Re: [dm-devel] dm-cache: ensuring cache is flushed in timely manner

Dne 5.7.2017 v 17:21 Thanos Makatos napsal(a): Occasionally I need to flush a writeback cache in order to execute some other operation (e.g. take a back up). I do this by first setting the policy to cleaner, then wait for the number of dirty blocks to reach 0, and finally set the mode to

Re: [dm-devel] [PATCH] dm mirror: fix crash caused by NULL-pointer dereference

Dne 26.6.2017 v 12:55 Eric Ren napsal(a): Hi Zdenek, On 06/26/2017 05:46 PM, Zdenek Kabelac wrote: Dne 26.6.2017 v 11:08 Eric Ren napsal(a): [... snip...] Hi Which kernel version is this ? I'd thought we've already fixed this BZ for old mirrors: https://bugzilla.redhat.com/show_bug.cgi

Re: [dm-devel] [PATCH] dm thin: fix a memory leak when passing discard bio down

Dne 18.4.2017 v 09:27 Dennis Yang napsal(a): dm-thin does not free the discard_parent bio after all chained sub bios finished. The following kmemleak report could be observed after pool with discard_passdown option processes discard bios in linux v4.11-rc7. To fix this, we drop the

Re: [dm-devel] Question about merge performance

Dne 24.3.2017 v 03:29 Michael McCarthy napsal(a): I appreciate the insight. Are there any plans to enhance the code to allow more parallel execution and/or allow users to experiment with QD? Nope there are no plans to enhance old snapshot target - it would essentially means to write

Re: [dm-devel] trouble with generic/081

Dne 9.1.2017 v 15:54 Eric Sandeen napsal(a): On 1/9/17 8:22 AM, Zdenek Kabelac wrote: But could anyone from XFS specify - why umount is causing some 'more' damage, then no umount at all ? Please reread this thread... it /started/ with problems /caused by unmount/ for Christoph. It's

Re: [dm-devel] trouble with generic/081

Dne 9.1.2017 v 14:39 Christoph Hellwig napsal(a): On Fri, Jan 06, 2017 at 09:46:00AM +1100, Dave Chinner wrote: And my 2c worth on the "lvm unmounting filesystems on error" - stop it, now. It's the wrong thing to do, and it makes it impossible for filesystems to handle the error and recover

Re: [dm-devel] trouble with generic/081

Dne 5.1.2017 v 20:29 Eric Sandeen napsal(a): On 1/5/17 1:13 PM, Zdenek Kabelac wrote: Anyway, at this point I'm not convinced that anything but the filesystem should be making decisions based on storage error conditions. So far I'm not convinced doing nothing is better then trying at least

Re: [dm-devel] trouble with generic/081

Dne 5.1.2017 v 19:24 Eric Sandeen napsal(a): (dropping fstests list) On 1/5/17 4:35 AM, Zdenek Kabelac wrote: Dne 5.1.2017 v 00:03 Eric Sandeen napsal(a): On 12/16/16 2:15 AM, Christoph Hellwig wrote: On Thu, Dec 15, 2016 at 10:16:23AM +0100, Zdenek Kabelac wrote: ... What XFS did

Re: [dm-devel] trouble with generic/081

Dne 5.1.2017 v 00:03 Eric Sandeen napsal(a): On 12/16/16 2:15 AM, Christoph Hellwig wrote: On Thu, Dec 15, 2016 at 10:16:23AM +0100, Zdenek Kabelac wrote: So let me explain the logic behind this 'amazingly stupid' idea. And that logic doesn't make any sense at all. invibly unmounting

Re: [dm-devel] dm-cache: please check/repair metadata

Dne 18.12.2016 v 16:51 Ian Pilcher napsal(a): I'm not exactly sure what are you doing, are you maintaining your own dm cache volumes ? (Writing your own volume manager and not using lvm2 - what is lvm2 missing/doing wrong ?) Yup. I've continuing to use my "zodcache" system for assembling

Re: [dm-devel] dm-cache: please check/repair metadata

Dne 18.12.2016 v 01:34 Ian Pilcher napsal(a): On 12/08/2016 08:53 AM, Ian Pilcher wrote: Running cache_repair against the metadata device gives me this error: transaction_manager::new_block() couldn't allocate new block I strongly suspect that my metadata device is too small. It was sized

Re: [dm-devel] trouble with generic/081

Dne 16.12.2016 v 09:15 Christoph Hellwig napsal(a): On Thu, Dec 15, 2016 at 10:16:23AM +0100, Zdenek Kabelac wrote: So let me explain the logic behind this 'amazingly stupid' idea. And that logic doesn't make any sense at all. invibly unmounting a file system behind the users back

Re: [dm-devel] trouble with generic/081

Dne 15.12.2016 v 09:42 Christoph Hellwig napsal(a): On Thu, Dec 15, 2016 at 05:36:50PM +1100, Dave Chinner wrote: Yup, same here. My local patch is this: I have a sleep 1 before the unmount. To be honest this lvm behavior of auto-unmounting on error seems like a huge mess, I wonder if there

Re: [dm-devel] dm-cache: please check/repair metadata

Dne 8.12.2016 v 02:36 Ian Pilcher napsal(a): I have a dm-cache device that throws the following error when I try to create it: device-mapper: cache: 253:20: unable to switch cache to write mode until repaired. device-mapper: cache: 253:20: switching cache to read-only mode device-mapper:

Re: [dm-devel] how do i push my changes in dm layer to main stream

Dne 5.12.2016 v 07:29 muneendra kumar napsal(a): Hi, This is a general question. If i do any changes in both multipath tool and dm driver (kernel). How do i push my changes into main stream. Can someone explain me the process so that it will help me a lot. Hi You propose your changes here

Re: [dm-devel] Improve processing efficiency for addition and deletion of multipath devices

Dne 28.11.2016 v 18:22 Benjamin Marzinski napsal(a): On Mon, Nov 28, 2016 at 01:08:51PM +0100, Hannes Reinecke wrote: On 11/28/2016 12:51 PM, Zdenek Kabelac wrote: Dne 28.11.2016 v 11:42 Hannes Reinecke napsal(a): On 11/28/2016 11:06 AM, Zdenek Kabelac wrote: With multipath device - you

Re: [dm-devel] Improve processing efficiency for addition and deletion of multipath devices

Dne 23.11.2016 v 02:08 tang.jun...@zte.com.cn napsal(a): So, now we have at least 4 ways to improve mutliapth efficiency: 1) Filtering uevents; 2) Merger uevents; 3) Using separate locks for mpvec and pathvec; 4) Get rid of the gazillion waiter threads. This is exciting, but how do we

Re: [dm-devel] Improve processing efficiency for addition and deletion of multipath devices

Dne 29.11.2016 v 09:16 Martin Wilck napsal(a): On Tue, 2016-11-29 at 09:10 +0100, Zdenek Kabelac wrote: Dne 29.11.2016 v 09:02 Martin Wilck napsal(a): On Tue, 2016-11-29 at 07:47 +0100, Hannes Reinecke wrote: On 11/28/2016 07:46 PM, Benjamin Marzinski wrote: On Thu, Nov 24, 2016 at 10:21

Re: [dm-devel] Improve processing efficiency for addition and deletion of multipath devices

Dne 29.11.2016 v 09:02 Martin Wilck napsal(a): On Tue, 2016-11-29 at 07:47 +0100, Hannes Reinecke wrote: On 11/28/2016 07:46 PM, Benjamin Marzinski wrote: On Thu, Nov 24, 2016 at 10:21:10AM +0100, Martin Wilck wrote: On Fri, 2016-11-18 at 16:26 -0600, Benjamin Marzinski wrote: At any rate,

Re: [dm-devel] Improve processing efficiency for addition and deletion of multipath devices

Dne 28.11.2016 v 17:07 Benjamin Marzinski napsal(a): On Mon, Nov 28, 2016 at 11:05:29AM +0100, Hannes Reinecke wrote: Hi Junhui, Tricky bit would be to figure out _when_ to stop uevent processing and calling 'ev_add_path'. I guess we'd need to make 'ev_add_path' running in a separate thread;

Re: [dm-devel] Improve processing efficiency for addition and deletion of multipath devices

Dne 28.11.2016 v 11:42 Hannes Reinecke napsal(a): On 11/28/2016 11:06 AM, Zdenek Kabelac wrote: Dne 28.11.2016 v 03:19 tang.jun...@zte.com.cn napsal(a): Hello Christophe, Ben, Hannes, Martin, Bart, I am a member of host-side software development team of ZXUSP storage project in ZTE Corporation

Re: [dm-devel] Improve processing efficiency for addition and deletion of multipath devices

Dne 28.11.2016 v 03:19 tang.jun...@zte.com.cn napsal(a): Hello Christophe, Ben, Hannes, Martin, Bart, I am a member of host-side software development team of ZXUSP storage project in ZTE Corporation. Facing the market demand, our team decides to write code to promote multipath efficiency next

Re: [dm-devel] dm-cache issue

Dne 16.11.2016 v 14:45 Teodor Milkov napsal(a): On 16.11.2016 11:24, Zdenek Kabelac wrote: Dne 15.11.2016 v 13:38 Teodor Milkov napsal(a): On 14.11.2016 17:34, Zdenek Kabelac wrote: Dne 14.11.2016 v 16:02 Alexander Pashaliyski napsal(a): The server is booting for hours, because of IO load

Re: [dm-devel] dm-cache issue

Dne 15.11.2016 v 13:38 Teodor Milkov napsal(a): On 14.11.2016 17:34, Zdenek Kabelac wrote: Dne 14.11.2016 v 16:02 Alexander Pashaliyski napsal(a): The server is booting for hours, because of IO load. It seems is triggered a flush from SSD disk (that is used for a cache device) to the raid

Re: [dm-devel] dm-cache issue

Dne 14.11.2016 v 16:02 Alexander Pashaliyski napsal(a): Hi guys, I am in a process of evaluating dm-cache for our backup system. Currently I have an issue when restart the backup server. The server is booting for hours, because of IO load. It seems is triggered a flush from SSD disk (that is

Re: [dm-devel] how to refresh LV to apply fstrim online

Dne 20.10.2016 v 10:52 Gianluca Cecchi napsal(a): Hello, I have a cluster in RH EL 6.5 (I also have a case open fwiw...) where I'm using HA-LVM. I made an upgrade of the storage array Netappp -> Netapp. I was able to do it online without service disruption using pvmove. As a side effect the

Re: [dm-devel] Device-mapper target driver for Write tracking

Dne 19.10.2016 v 12:53 Daniel Armbruster napsal(a): Hi List, I'm looking for a device-mapper target driver giving me the possibility to track/log WRITE requests. The idea is to track those WRITE requests within a Bitmap e.g. 1:LV-EXTEND (for LVM2). I read already the device-mapper documentation

Re: [dm-devel] lvmetad doesn't terminate with SIGTERM if thin volume used

Dne 3.9.2016 v 05:17 james harvey napsal(a): On Tue, Aug 16, 2016 at 5:57 AM, Zdenek Kabelac <zkabe...@redhat.com> wrote: Dne 6.8.2016 v 04:08 james harvey napsal(a): Same problem and question about if an immediate SIGKILL is OK for dmeventd. On Thu, Aug 4, 2016 at 11:20 PM, james

Re: [dm-devel] During systemd/udev, device-mapper trying to work with non-LVM volumes

volumes just have some mappings.. --- If you are not going to run 'lvcreate -s' - why you talk about snapshots? Your emails are simply still too confusing... Regards Zdenek On Thu, Jul 28, 2016 at 10:12 AM, Zdenek Kabelac <zkabe...@redhat.com> wrote: Dne 28.7.2016 v 03:33 james harvey napsal(

Re: [dm-devel] write directly to device mapper snapshot origin device ?

Dne 15.7.2016 v 14:40 Navin P.S napsal(a): On Fri, Jul 15, 2016 at 6:05 PM, Zdenek Kabelac <zkabe...@redhat.com> wrote: Dne 15.7.2016 v 14:15 Navin P.S napsal(a): On Fri, Jul 15, 2016 at 5:21 PM, Mikulas Patocka <mpato...@redhat.com> wrote: On Fri, 15 Jul 2016, Navin P.S wro

Re: [dm-devel] write directly to device mapper snapshot origin device ?

Dne 15.7.2016 v 14:15 Navin P.S napsal(a): On Fri, Jul 15, 2016 at 5:21 PM, Mikulas Patocka wrote: On Fri, 15 Jul 2016, Navin P.S wrote: Resend .. On Thu, Jul 14, 2016 at 7:55 PM, Navin P.S wrote: Hi, Can i do dd if=/dev/zero

Re: [dm-devel] poor thin performance, relative to thick

Dne 11.7.2016 v 22:44 Jon Bernard napsal(a): Greetings, I have recently noticed a large difference in performance between thick and thin LVM volumes and I'm trying to understand why that it the case. In summary, for the same FIO test (attached), I'm seeing 560k iops on a thick volume vs. 200k

Re: [dm-devel] Possible data corruption with dm-thin

Dne 21.6.2016 v 09:56 Dennis Yang napsal(a): Hi, We have been dealing with a data corruption issue when we run out I/O test suite made by ourselves with multiple thin devices built on top of a thin-pool. In our test suites, we will create multiple thin devices and continually write to them,

Re: [dm-devel] multipath-0.5.0 still provides broken udev rules

On 26.4.2016 10:47, Hannes Reinecke wrote: On 04/26/2016 10:39 AM, Zdenek Kabelac wrote: On 26.4.2016 07:43, Hannes Reinecke wrote: On 04/25/2016 07:38 PM, Benjamin Marzinski wrote: On Mon, Apr 25, 2016 at 02:56:35PM +0200, Christophe Varoqui wrote: Hi, Those example udev rules

Re: [dm-devel] multipath-0.5.0 still provides broken udev rules

On 26.4.2016 07:43, Hannes Reinecke wrote: On 04/25/2016 07:38 PM, Benjamin Marzinski wrote: On Mon, Apr 25, 2016 at 02:56:35PM +0200, Christophe Varoqui wrote: Hi, Those example udev rules are indeed unmaintained and should be removed not to confuse distributors. Distributors

  1   2   >