Mailinglist Archive: opensuse-bugs (4250 mails)

< Previous Next >
[Bug 1011053] Rebooting takes a long time because dmeventd refuses to exit (LVM thin volume)
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 05 Jan 2017 11:16:05 +0000
  • Message-id: <bug-1011053-21960-zfK1FsQPhd@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1011053
http://bugzilla.suse.com/show_bug.cgi?id=1011053#c4

zhen ren <zren@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |IN_PROGRESS

--- Comment #4 from zhen ren <zren@xxxxxxxx> ---
Hi,

I am new to this issue. I want to confirm one thing meanwhile I am trying to
replicate your trouble on my side:


I think it does mean that snapper + LV thin-provisioned snapshots for ext4
should be enough to trigger it. Just make sure that dmeventd is running
before you try to reboot or shutdown. You may also note that dmeventd
refuses to exit with SIGTERM.


Does the problem happen every time when you shutdown or reboot? Or only
occurred when the system is happening to run "dmeventd" deamon?

What we need to known is what the lvm is doing there? We can imagine that
snapper (hourly according to you) tell lvm to take snapshot, after that, the
cleanup algorithm will also let lvm to cleanup the old snapshot. I don't know
how long each of the operations lvm will take, which decides how busy lvm is,
and the time window the shutdown meets a working lvm. It is reasonable if
shutdown happens during lvm is busy. Anyway, I will look into more when I get
time;-)



Probably not relevant, but note I have an extra volume mounted inside the
/home FS. It's a regular volume, also ext4, not being snapshotted.

it's fine;-)

Eric

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >