Bug#766732: libc: Segfault in libc (from process "pool") accessing files shared via DAV across ethernet on another machine
Package: libc6
Version: 2.19-11
Severity: grave
File: libc
Justification: causes non-serious data loss
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Two computers, both amd64 systems, running Jessie (testing), both dist-upgraded
24 Oct 2014.
Attempting to copy a substantial dataset from one machine to the other.
I have not tried to find the problem from the command line but can reproduce it
from either machine
using Gnome (Nautilus).
* What exactly did you do (or not do) that was effective (or
ineffective)?
On one machine, (the Server) enable file sharing (via ~/Public in Nautilus)
Then expose a substantial quantity of data (0.3TB is enough here) in the Public
folder.
For example
cd ~/Public
mount --bind ../Music Music
(I have a lot of FLAC-encoded CDs in Music : you may need to substitute a
similarly large lump of data.
The example dataset has 14000 large files in 600 folders.)
On the other machine, (the Client) in Nautilus, mount "users shared files on
<Server hostname>"
display that folder
perform operations on e.g. Music.
Right-click/Properties exhibits the problem
Copy/Paste (to a local folder on the Client - which DOES have enough space) -
also exhibits it, but it takes much longer to manifest.
This suggests to me that the problem is in handling directory or file stats
rather than simply the file sizes themselves.
* What was the outcome of this action?
The operation runs for a while, then stops (e.g. the Properties window shows
file size increasing, but stops at 253GB
(or 63GB when the Client and Server machines are interchanged; but always at
the same size)
dmesg on the Client machine reports:
[ 699.677988] pool[1873]: segfault at 0 ip 00007f5d88066a3a sp
00007f5d7d974cb8 error 4 in libc-2.19.so[7f5d87fe5000+19f000]
(on a subsequent run after a dist-upgrade and restart)
[ 303.568248] pool[1941]: segfault at 0 ip 00007f84f52e6a3a sp
00007f84f299ccb8 error 4 in libc-2.19.so[7f84f5265000+19f000]
* What outcome did you expect instead?
Successful operation without segfault...
I have not tried digging more info using gdb : given Gnome is in the way it's
not clear to me how one would go about it, e.g. which process to attach the
debugger to!
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: jessie/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libc6:amd64 depends on:
ii libgcc1 1:4.9.1-16
libc6:amd64 recommends no packages.
Versions of packages libc6:amd64 suggests:
ii debconf [debconf-2.0] 1.5.53
pn glibc-doc <none>
ii locales 2.19-11
-- debconf information:
* glibc/restart-services: exim4 cups cron
glibc/disable-screensaver:
* libraries/restart-without-asking: false
glibc/upgrade: true
glibc/restart-failed:
Reply to: