Description of problem:
Host A exports a LVM logical volume (2GB) via iscsi, Host B mounts it.
When writing to the iscsi-mounted file system, host B lock-up.
Version-Release number of selected component (if applicable):
Host A: FC5, kernel 2.6.16-1.2096_FC5/x86_64,
Host B: FC5, kernel 2.6.16-1.2096_FC5/x86_64
Steps to Reproduce:
1. Mount the iscsi volume
2. do some large copy or writing on mounte volume
Client host hangs up
A well done copy or write
Created attachment 129001 [details]
Netconsole from a large copy ide to iscsi
Created attachment 129002 [details]
Netconsole dump with iscsi to iscsi copy, plus /dez/zero to iscsi write
Having Host A (client/initiator) as FC4, kernel 2.6.15-1.1831_FC4smp, i686, with
iscsi-initiator-utils-22.214.171.1246-0.1 rebuild from FC5 src rpm, no problem surfaces.
Have exact same problem with FC5 kernel 2.6.16-1.2111_FC5 as initiator and
Netapp (ontap 7.0.4) as target. Locks up solid when running bonnie++ benchmark
during large writes.
Sorry about the very very late response, I saw this BZ by accident while
searching for something else.
Could you try the upsteam code here
You can get it by doing
svn checkout svn://svn.berlios.de/open-iscsi
I was about to make a new release for the upstream code and Fedora.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
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 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.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
(this is a mass-close to kernel bugs in NEEDINFO state)
As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.
If you believe that this bug was closed in error, please feel free to reopen