From: Tilman Schmidt <tilman@imap.cc>
To: LKML <linux-kernel@vger.kernel.org>
Subject: possible regression in kernel 3.6: system hangs during nightly tape backup
Date: Tue, 20 Nov 2012 01:14:54 +0100 [thread overview]
Message-ID: <50AACB7E.8060601@imap.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 2513 bytes --]
For the 4th time now after switching to kernel 3.6, my system became
unresponsive during the nightly Bacula backup run. It looks as if
all disk accesses are suddenly blocked:
- Desktop apps stop responding one after another, starting with
Firefox followed by other "heavy" apps, while Konsole windows
continue being usable for a while.
- "top" shows the load average steadily increasing with no process
actually consuming relevant quantities of CPU.
- I can do "dmesg > /root/dmesg.out" followed by "less /root/dmesg.out"
in a Konsole window just fine, but after the inevitable hard reset
the file /root/dmesg.out isn't there.
- The "sync" command hangs indefinitely.
- The "shutdown" command and ctrl/alt/Del emit "system going down"
broadcast messages but never get anywhere.
- Killing processes manually works for some (bacula-sd even ejects
the tape before exiting) but most remain in state D or Z.
- Eventually, all text consoles are blocked and a hardware reset is
the only remaining option.
- After the reboot, a Bacula spool file is left behind in
/var/spool/bacula, proof that the hang happened during the backup.
This does not happen during every backup run, but frequently enough
to be annoying. (About once per week.) It never happened with kernel
3.5. For comparison went back to kernel 3.5.7 for a week and it
never happened during that time. Last night I booted 3.6.7 and the
very next backup caused the hang again. The last kernel message that
made it to the syslog on disk was
Nov 19 23:05:04 xenon kernel: [73877.128546] st0: Block limits 256 -
524288 bytes.
triggered by the start of the backup. In dmesg the next message was
[74401.249091] INFO: task flush-253:2:1320 blocked for more than 120
seconds.
followed by a backtrace. I have photos of the remaining dmesg output
which I'll try to upload somewhere accessible tomorrow.
Hardware 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
Disk configuration: md RAID1, LVM, ext3 and ext4 volumes
Software: Opensuse 11.4 64 bit, vanilla kernel 3.5.7 and 3.6.7,
Bacula 5.2.12
HTH
T.
--
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-11-20 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 0:14 Tilman Schmidt [this message]
2012-11-20 15:49 ` possible regression in kernel 3.6: system hangs during nightly tape backup Tilman Schmidt
2012-11-24 19:17 ` Tilman Schmidt
2012-11-25 21:34 ` Borislav Petkov
2012-12-05 11:03 ` possible regression in kernel 3.6 and 3.7-rc: " 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=50AACB7E.8060601@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.