Hey, I'm running snapper on Arch Linux, using lvm thin provisioning for
the snapshots. It seems to be working fine (I can create, mount,
delete,... snapshots). However, after a command completes, some boost
thread seems to die:
[system log excerpt]
Feb 05 06:41:49 mammoth dbus-daemon[477]: dbus[477]: [system] Activating
service name='org.opensuse.Snapper' (using servicehelper)
Feb 05 06:41:49 mammoth dbus[477]: [system] Activating service
name='org.opensuse.Snapper' (using servicehelper)
Feb 05 06:41:49 mammoth dbus-daemon[477]: dbus[477]: [system] Successfully
activated service 'org.opensuse.Snapper'
Feb 05 06:41:49 mammoth dbus[477]: [system] Successfully activated service
'org.opensuse.Snapper'
Feb 05 06:41:50 mammoth dbus-daemon[477]: terminate called after throwing
an instance of
'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread
Feb 05 06:41:50 mammoth dbus-daemon[477]: what(): boost thread: thread
not joinable: Invalid argument
Feb 05 06:41:50 mammoth systemd-coredump[573]: Process 570 (snapperd)
dumped core.
mammoth ~ # pacman -Q snapper-git thin-provisioning-tools-git lvm2-thin
dbus boost systemd
snapper-git 20130205-1
thin-provisioning-tools-git 20130205-1
lvm2-thin 2.02.98-1
dbus 1.6.8-6
boost 1.52.0-1
systemd 197-4
mammoth ~ # /usr/sbin/snapperd -h
usage: snapperd [--options]
Options:
--stdout, -s Log to stdout.
--debug, -d Turn on debugging.
terminate called after throwing an instance of
'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::thread_resource_error>
>'
what(): boost thread: thread not joinable: Invalid argument
Aborted (core dumped)
If this is the wrong place for such a report, or, since it's not
suse-related, there is no general interest, please tell me. Otherwise, are
there other reports that might help identify the problem?
Regards,
Carsten Bohnens
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
