http://bugzilla.suse.com/show_bug.cgi?id=1099494 http://bugzilla.suse.com/show_bug.cgi?id=1099494#c8 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aschnell@suse.com | |) --- Comment #8 from Lukas Ocilka <locilka@suse.com> --- (In reply to Oliver Kurz from comment #6)
Well, the original issue is not about the system being slow due to snapshot handling but that the snapshot creation actually *failed*.
And that is the question: Did snapper really fail or did the caller (of snapper) give up and decided to time-out? As I can read in the desc: PluginScript.cc(~PluginDumpStderr):75 ! ERROR:root:creating snapshot failed: 2018-06-28 10:54:30 <2> linux-9akz(17693) [PLUGIN] PluginScript.cc(~PluginDumpStderr):75 ! ERROR:root: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. A.) If snapper failed, then we need to fix snapper B.) But if it just did not send a reply soon enough, we might need to extend timeouts or periodically check whether snapper is still doing something. Arvin? -- You are receiving this mail because: You are on the CC list for the bug.