On Thu, Jan 10, 2019 at 4:18 AM Zdenek Kabelac wrote:
>
> Dne 10. 01. 19 v 1:39 james harvey napsal(a):
> > Q1 - Is it correct that a filesystem's discard code needs to look for
> > an entire block of size discard_granularity to send to the block
> > device (dm/LVM)?
On Wed, Jan 9, 2019 at 7:39 PM james harvey wrote:
> Q2 - Is it correct that the blocks of size discard_granularity sent to
> dm/LVM need to be aligned from the start of the volume, rather than
> the start of the partition? ...
This is probably what discard_alignment is for.
# lvcrea
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 default, a LVM thick volume is giving
a
Same problem and question about if an immediate SIGKILL is OK for dmeventd.
On Thu, Aug 4, 2016 at 11:20 PM, james harvey <jamespharve...@gmail.com> wrote:
> Does it matter at all if lvmetad shuts down gracefully?
>
> Can I safely just have systemd right off the bat send a SI
Ok, we can put the BTRFS issues aside. I've reproduced using EXT4.
Below are close to the minimal steps I can use to create the problem.
If I remove some of the lvcreates that aren't being used, the problem
seems to happen less often. So I'm not sure if that has an affect on
the race condition,
PM, james harvey <jamespharve...@gmail.com> wrote:
> After upgrading to systemd v231, my shutdowns/reboots have a 90 second
> delay at the very end. Linux kvm 4.6.4-1.
>
> After I looked into it, I found it's due to lvmetad never terminating
> when receiving a SIGTERM,
On Wed, Aug 3, 2016 at 10:51 PM, james harvey <jamespharve...@gmail.com> wrote:
> After upgrading to systemd v231, my shutdowns/reboots have a 90 second
> delay at the very end. Linux kvm 4.6.4-1.
Ignore the "kvm" here, must have typed that into the wrong window.
This i
After upgrading to systemd v231, my shutdowns/reboots have a 90 second
delay at the very end. Linux kvm 4.6.4-1.
After I looked into it, I found it's due to lvmetad never terminating
when receiving a SIGTERM, and after 90 seconds, systemd performs a
SIGKILL.
systemd 231 (commit d4506129)
