From: Tilman Schmidt <tilman@imap.cc>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Regression: Bacula jobs fail with kernel 3.8-rc1
Date: Mon, 31 Dec 2012 16:07:19 +0100 [thread overview]
Message-ID: <50E1AA27.5000508@imap.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
With kernel 3.8-rc1, my nightly Bacula backup job reproducibly aborts
20 minutes into spooling with a "broken pipe" error on the network
socket connecting the file and storage daemons:
31-Dec 00:45 xenon-sd JobId 859: Spooling data ...
31-Dec 01:04 xenon-fd JobId 859: Error: bsock.c:429 Write error sending
65536 bytes to Storage daemon:xenon:9103: ERR=Broken pipe
31-Dec 01:04 xenon-fd JobId 859: Fatal error: backup.c:1200 Network send
error to SD. ERR=Broken pipe
31-Dec 01:04 xenon-dir JobId 859: Error: Director's comm line to SD dropped.
Returning to kernel 3.7.1 makes it work again. (Provided the crash
I reported in http://marc.info/?l=linux-kernel&m=135337052232021&w=2
doesn't hit, of course.)
Configuration:
Intel Pentium D, Intel DQ965GF mainboard, 6 GB RAM
onboard S-ATA controller driving two 500 GB S-ATA disks
and a Pioneer DVR-216D DVD-RW drive
Adaptec 29160B Ultra160 SCSI adapter driving a
Tandberg TS400 LTO-2 tape drive
openSUSE 11.4 userspace
Bacula 5.2.12, all daemons on the same machine, spooling to local disk
Regards,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next reply other threads:[~2012-12-31 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 15:07 Tilman Schmidt [this message]
2013-01-04 11:25 ` Regression: Bacula jobs fail with kernel 3.8-rc1 Tilman Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50E1AA27.5000508@imap.cc \
--to=tilman@imap.cc \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox