Package: mbuffer
Version: 20140310-3
Severity: important
Tags: upstream
Dear Maintainer,
I traced a failure in my homebrewed backup system to a bug in mbuffer.
Intermittely, a backup would hang; strace showed that mbuffer was
waiting forever printing the statistic
in @ 0.0 KiB/s, out @ 0.0 KiB/s, 0.0 KiB total, buffer 0% full
I eventually determined that the following command would reproduce the
problem almost every time:
$ echo | taskset -c 1 mbuffer -P50
In this case, mbuffer should exit essentally immediately.
I believe that the problem has something to do with the way mbuffer uses
threads. By not using "taskset -c 1", the problem manifests more
rarely, though still more than 1 in 50 times.
The bug seems to exist in unmodified upstream mbuffer-20141227 as well.
Curiously, the bug does not exist or does not manifest nearly as readily
on FreeBSD 9.2 with unmodified upstream mbuffer-20141227.
-- System Information:
Debian Release: 8.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mbuffer depends on:
ii libc6 2.19-13
ii libmhash2 0.9.9.9-7
mbuffer recommends no packages.
mbuffer suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
