Red Hat Bugzilla – Bug 160068
Tar hangs in D state on tape write.
Last modified: 2015-01-04 17:20:07 EST
Description of problem:
Tar hangs in D state on tape write, using Adaptec AHA-3960D SCSI card and Dell
PowerVault 122T. I can't kill the process and can't 'ls /proc/[it's pid]/fd/'
Version-Release number of selected component (if applicable):
I'm using an FC3 system with kernel 2.6.11-1.14_FC3smp.
Tar accepts a "-b" flag for the size of blocks to use in writing and reading.
If I don't first set the tape drive to use a corresponding block size, tar hangs
immediate on invocations for read or write. When I do set the corresponding
block sizes, the behavior becomes infrequent, but happens after about a day of
Steps to Reproduce:
1. tar cf /dev/tape files
*** Bug 160069 has been marked as a duplicate of this bug. ***
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
With a block size of 20 ("-b 20"), there is no hang. That is the default for
tar and possibly why this doesn't happen more often. Presumably the driver
doesn't wait for the I/O interrupt correctly, but assumes a fast return. A fast
return is more likely with a smaller block size, and so below a certain level
(e.g. around tar's default of 20), hangs are rare or don't happen. If this is
the case, it's a nice workaround but this is still a bug.
[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (18.104.22.168). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO_REPORTER state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.