Package: dar
Version: 2.2.1-1
Severity: normal

dar was writing to a file in a mounted samba filesystem.  The server died,
generating write errors in the client side.  As a consequence, dar went
crazy into a user-mode infinite loop.

  - A file descriptor is open for writing to a *.dar.1 file that formerly was
  in the samba mounted filesystem.

  - No syscalls are ever performed (checked with strace).

  - gdb backtrace (with symbols):

#0  0xb7df61ac in libdar::compressor::gzip_write (this=0x80b1e40, a=0x19000 
<Address 0x19000 out of bounds>, size=73158) at wrapperlib.hpp:86
#1  0xb7df73d4 in libdar::compressor::inherited_write (this=0x80b1e40, 
a=0xb7ee0520 "U\211�\203�X\211]�\213E\b\211u�\211}�\213P\004趿��\201ú&\a",
    size=3085829408) at compressor.hpp:86
#2  0xb7e4b3df in libdar::generic_file::write (this=0x82fe9f0, a=0xb7ee0520 
"U\211�\203�X\211]�\213E\b\211u�\211}�\213P\004趿��\201ú&\a", size=3085829408)
    at generic_file.cpp:112
#3  0xb7e4b7df in libdar::generic_file::copy_to (this=0x833c520, [EMAIL 
PROTECTED]) at generic_file.cpp:158
#4  0xb7e4b821 in libdar::generic_file::copy_to (this=0x833c520, [EMAIL 
PROTECTED], [EMAIL PROTECTED]) at generic_file.cpp:166
#5  0xb7e4687f in save_inode ([EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL 
PROTECTED], stock=0x80b1e40, info_details=32, [EMAIL PROTECTED],
    compr_used=3085829408, [EMAIL PROTECTED], alter_atime=false) at 
filtre.cpp:879
#6  0xb7e381e5 in libdar::filtre_sauvegarde ([EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED], stockage=0x80b1e40, [EMAIL PROTECTED],
    [EMAIL PROTECTED], [EMAIL PROTECTED], info_details=true, [EMAIL PROTECTED], 
make_empty_dir=true, save_ea_root=false, save_ea_user=false,
    [EMAIL PROTECTED], [EMAIL PROTECTED], nodump=false, [EMAIL PROTECTED], 
alter_atime=false, same_fs=false, ignore_owner=false)
    at defile.hpp:53
#7  0xb7eff102 in libdar::archive::op_create_in (this=0x809a318, [EMAIL 
PROTECTED], create_not_isolate=true, [EMAIL PROTECTED], [EMAIL PROTECTED],
    ref_arch=0x0, [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], 
[EMAIL PROTECTED], allow_over=true, warn_over=true,
    info_details=true, pause=false, empty_dir=true, algo=bzip2, 
compression_level=6, [EMAIL PROTECTED], [EMAIL PROTECTED], root_ea=false,
    user_ea=false, [EMAIL PROTECTED], crypto=crypto_blowfish, [EMAIL 
PROTECTED], crypto_size=10240, [EMAIL PROTECTED], [EMAIL PROTECTED],
    nodump=false, [EMAIL PROTECTED], empty=false, alter_atime=false, 
same_fs=false, ignore_owner=false) at archive.cpp:719
#8  0xb7ef2745 in archive (this=0x809a318, [EMAIL PROTECTED], [EMAIL 
PROTECTED], [EMAIL PROTECTED], ref_arch=0xb7ee0520, [EMAIL PROTECTED],
    [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], allow_over=true, 
warn_over=true, info_details=true, pause=false, empty_dir=true,
    algo=3085829408, compression_level=3085829408, [EMAIL PROTECTED], [EMAIL 
PROTECTED], root_ea=false, user_ea=false, [EMAIL PROTECTED],
    crypto=3085829408, [EMAIL PROTECTED], crypto_size=3085829408, [EMAIL 
PROTECTED], [EMAIL PROTECTED], nodump=false, ignore_owner=false,
    [EMAIL PROTECTED], empty=false, alter_atime=false, same_fs=false, [EMAIL 
PROTECTED]) at archive.cpp:140
#9  0x0806e2db in little_main ([EMAIL PROTECTED], argc=-1209137888, 
argv=0xb7ee0520, env=0xb7ee0520) at stl_alloc.h:652
#10 0x08076dc3 in dar_suite_global (argc=72, argv=0xbf8a4ce4, env=0xb7ee0520, 
call=0x806dbd0 <little_main>) at dar_suite.cpp:94
#11 0x0806dbcb in main (argc=-1209137888, argv=0xb7ee0520, env=0xb7ee0520) at 
dar.cpp:56

Sometimes the backtrace starts with this instead:

#0  0xb7c8d975 in BZ2_bzCompress () from /usr/lib/libbz2.so.1.0
#1  0xb7ee0d62 in libdar::wrapperlib::bz_compress (this=0x82fe9f0, 
flag=134997624) at wrapperlib.cpp:323

We can't reproduce the problem anymore, but the dar process is still running.
Let me know if you want me to poke for other information from it.

-- System Information:
<removed irrelevant information (the problem happens on a sarge i386)>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to