File Copying hangs
Can anyone help?
I have had this issue with file copying for some time now. I select either a large number of files or several large files to copy and the iscsi connection to the iscsi device (drobopro) stops. After that I cannot ping the ip address of the drobo either.
The system log repeats this message every few seconds but I can't locate exactly when the fault occurs:
29/05/2013 11:29:53 ubuntu NetworkManager[
29/05/2013 11:29:53 ubuntu kernel [ 9222.708142] sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control rx
29/05/2013 11:29:56 ubuntu iscsid connect to 192.168.2.80:3260 failed (No route to host)
Question information
- Language:
- English Edit question
- Status:
- Solved
- Assignee:
- No assignee Edit question
- Solved by:
- Thomas Krüger
- Solved:
- Last query:
- Last reply:
Revision history for this message
|
#1 |
I've just manage to catch it:
May 29 11:39:52 ubuntu kernel: [ 443.117696] sky2 0000:03:00.0: error interrupt status=0x80000000
May 29 11:39:52 ubuntu kernel: [ 443.117704] sky2 0000:03:00.0: PCI hardware error (0x2010)
May 29 11:40:01 ubuntu kernel: [ 451.669999] ------------[ cut here ]------------
May 29 11:40:01 ubuntu kernel: [ 451.670006] WARNING: at /home/apw/
May 29 11:40:01 ubuntu kernel: [ 451.670008] Hardware name: H67MA-UD2H-B3
May 29 11:40:01 ubuntu kernel: [ 451.670009] NETDEV WATCHDOG: eth0 (sky2): transmit queue 0 timed out
May 29 11:40:01 ubuntu kernel: [ 451.670011] Modules linked in: rfcomm bnep parport_pc bluetooth ppdev dm_crypt snd_hda_codec_hdmi snd_hda_
May 29 11:40:01 ubuntu kernel: [ 451.670041] Pid: 0, comm: swapper/0 Tainted: G C 3.3.8-030308-
May 29 11:40:01 ubuntu kernel: [ 451.670043] Call Trace:
May 29 11:40:01 ubuntu kernel: [ 451.670044] <IRQ> [<ffffffff8104f
May 29 11:40:01 ubuntu kernel: [ 451.670052] [<ffffffff8104f
May 29 11:40:01 ubuntu kernel: [ 451.670055] [<ffffffff8156b
May 29 11:40:01 ubuntu kernel: [ 451.670058] [<ffffffff8101a
May 29 11:40:01 ubuntu kernel: [ 451.670060] [<ffffffff8156a
May 29 11:40:01 ubuntu kernel: [ 451.670062] [<ffffffff8156a
May 29 11:40:01 ubuntu kernel: [ 451.670075] [<ffffffff8105e
May 29 11:40:01 ubuntu kernel: [ 451.670078] [<ffffffff81314
May 29 11:40:01 ubuntu kernel: [ 451.670080] [<ffffffff8156a
May 29 11:40:01 ubuntu kernel: [ 451.670081] [<ffffffff8105f
May 29 11:40:01 ubuntu kernel: [ 451.670084] [<ffffffff8109e
May 29 11:40:01 ubuntu kernel: [ 451.670086] [<ffffffff81056
May 29 11:40:01 ubuntu kernel: [ 451.670087] [<ffffffff8101a
May 29 11:40:01 ubuntu kernel: [ 451.670090] [<ffffffff810a5
May 29 11:40:01 ubuntu kernel: [ 451.670093] [<ffffffff8166e
May 29 11:40:01 ubuntu kernel: [ 451.670095] [<ffffffff81015
May 29 11:40:01 ubuntu kernel: [ 451.670097] [<ffffffff81056
May 29 11:40:01 ubuntu kernel: [ 451.670099] [<ffffffff8166f
May 29 11:40:01 ubuntu kernel: [ 451.670101] [<ffffffff8166e
May 29 11:40:01 ubuntu kernel: [ 451.670102] <EOI> [<ffffffff81373
May 29 11:40:01 ubuntu kernel: [ 451.670106] [<ffffffff81373
May 29 11:40:01 ubuntu kernel: [ 451.670109] [<ffffffff81502
May 29 11:40:01 ubuntu kernel: [ 451.670110] [<ffffffff81012
May 29 11:40:01 ubuntu kernel: [ 451.670113] [<ffffffff8162d
May 29 11:40:01 ubuntu kernel: [ 451.670116] [<ffffffff81ceb
May 29 11:40:01 ubuntu kernel: [ 451.670118] [<ffffffff81ceb
May 29 11:40:01 ubuntu kernel: [ 451.670119] [<ffffffff81ceb
May 29 11:40:01 ubuntu kernel: [ 451.670121] [<ffffffff81ceb
May 29 11:40:01 ubuntu kernel: [ 451.670122] ---[ end trace d106c6950b0717d5 ]---
May 29 11:40:01 ubuntu kernel: [ 451.670124] sky2 0000:03:00.0: eth0: tx timeout
May 29 11:40:01 ubuntu kernel: [ 451.670130] sky2 0000:03:00.0: eth0: transmit ring 14 .. 35 report=14 done=14
May 29 11:40:01 ubuntu NetworkManager[
May 29 11:40:02 ubuntu kernel: [ 453.089278] connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4295003358, last ping 4295004608, now 4295005860
May 29 11:40:02 ubuntu kernel: [ 453.089288] connection1:0: detected conn error (1011)
May 29 11:40:03 ubuntu iscsid: Kernel reported iSCSI connection 1:0 error (1011) state (3)
May 29 11:40:04 ubuntu NetworkManager[
May 29 11:40:04 ubuntu kernel: [ 454.493431] sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control rx
May 29 11:40:09 ubuntu NetworkManager[
May 29 11:40:09 ubuntu kernel: [ 459.595371] sky2 0000:03:00.0: eth0: tx timeout
May 29 11:40:09 ubuntu kernel: [ 459.595378] sky2 0000:03:00.0: eth0: transmit ring 4 .. 8 report=4 done=4
May 29 11:40:12 ubuntu NetworkManager[
May 29 11:40:12 ubuntu kernel: [ 462.604189] sky2 0000:03:00.0: eth0: Link is up at 1000 Mbps, full duplex, flow control rx
Revision history for this message
|
#2 |
Are you coping over wifi or wireless?
What sharing technology are you using?
What OS is the server and the client running?
Thanks
Revision history for this message
|
#3 |
Thanks as always, Actionparsnip.
I am using wired, not wireless.
Sharing is with Samba v 2:3.6.3-2ubuntu2.6
I have a Kubuntu 12.04 machine running open-iscsi v 2.0.871-
The this machine has 2 nics, one on a 192.168.0.xxx for the LAN and the drobo runs connected to the iscsi lan on 192.168.2.xx therefore samba shares can be set up using the Kubuntu machine as a server however the issue with copying seems to be between the Kubuntu machine directly to the drobo.
192.168.0.x LAN --NIC0-- Samba ---- Kubuntu --NIC1-- 192.168.2.x ISCSI -- Drobo
Revision history for this message
|
#4 |
apologies eth0 is 192.168.2.x and eth1 is 192.168.0.x
Revision history for this message
|
#5 |
As you are using Linux on both sides, have you tried installing openssh-server on the Kubuntu box and using SFTP using nautilus as a client. It is also secure so can be used over WAN.
Revision history for this message
|
#6 |
I can certainly try. Haven't set that up before but I can try it.
I'm just wondering if I've made it clear that files are being transferred directly across the iscsi connection from the drobo to the Kubuntu box, not thro' Samba?
Revision history for this message
|
#7 |
I would add that I'd like to find out where the issue is. Does the info from the log give any clues?
Revision history for this message
|
#8 |
There seems to be something wrong with a PCI device.
Can you check if the device 0000:03:00.0 is the network card.
If it is, there might be a driver problem.
If you feel yourself comfortable with compiling a kernel module on your own, you can try this driver instead:
http://
Revision history for this message
|
#9 |
Thank you I will check it out. Will respond in a couple of days.
Revision history for this message
|
#10 |
Well, there's a first time for everything. I think I've compiled the driver and it's installed. There was a warning message when I compiled it. I'll reboot and see what happens.
fred@ubuntu:
Installation script for sk98lin driver.
Version 10.93.3.3 (Aug-22-2012)
(C)Copyright 2003-2012 Marvell(R).
=======
Add to your trouble-report the logfile install.log
which is located in the DriverInstall directory.
=======
1) installation 3) generate makefile
2) generate patch 4) exit
Choose your favorite installation method: 1
Please read this carefully!
This script will automatically compile and load the sk98lin
driver on your host system. Before performing both compilation
and loading, it is necessary to shutdown any device using the
sk98lin kernel module and to unload the old sk98lin kernel
module. This script will do this automatically per default.
Please plug a card into your machine. Without a card we aren't
able to check the full driver functionality.
Do you want proceed? (y/N) y
IMPORTANT INFORMATION!
We found an alternative driver for your Marvell product on this system.
The alternative driver is _NOT_ directly supported by Marvell and does not
include all features provided by your device. If you want to use the
sk98lin driver developed by Marvell, you may choose either to deactivate
or remove the alternative driver.
[PRESS ANY KEY FOR FURTHER INSTRUCTIONS]
Do nothing:
- The sk98lin will be installed
NOTE: It may happen that the alternative driver will be loaded on
the next boot process. In this case the Marvell driver _WON'T_ be
loaded.
Deactivate driver:
- The alternative driver will be renamed to _skge.ko or _sky2.ko
- All references in the /etc/modprobe.conf file will be changed to
the sk98lin driver
- The alternative driver will be unloaded
- The sk98lin driver will be installed
Remove driver (recommended):
- The alternative driver will be removed from your system
- All references in the /etc/modprobe.conf file will be changed to
the sk98lin driver
- The alternative driver will be unloaded
- The sk98lin driver will be installed
1) Do nothing
2) Deactivate diver
3) Remove driver
Action: 3
Disconnect alternative devices: (done) [ OK ]
Unload alternative driver (done) [ OK ]
Create tmp dir (/tmp/Sk98IDbIS
Check user id (0) [ OK ]
Check kernel version (3.3.8-
Check kernel symbol file (/proc/kallsyms) [ OK ]
Check kernel type (SMP) [ OK ]
Check number of CPUs (8) [ OK ]
Check architecture (found) [ OK ]
Set architecture (x86_64) [ OK ]
Check compiler (/usr/bin/gcc) [ OK ]
Check mcmodel flags (kernel) [ OK ]
Check module support (/sbin/insmod) [ OK ]
Check make (/usr/bin/make) [ OK ]
Check kernel gcc version (4.6.3) (Kernel:4.6.3 == gcc:4.6.3) [ OK ]
Check sk98lin driver availability (not loaded) [ OK ]
Check kernel header files (/lib/modules/
Check driver location (/lib/modules/
Check sources for .config file (/lib/modules/
Copy and check .config file (done) [ OK ]
Check the mem address space (lowmem) [ OK ]
Change IOMMU (enabled) [ OK ]
Create new .config file (done) [ OK ]
Execute: make oldconfig (done) [ OK ]
Check modpost availability (available) [ OK ]
Unpack the sources (done) [ OK ]
Check firmware availability (done) [ OK ]
Check kernel header version (not recognized) [ warn ]
Check kernel functions (Changed: nothing) [ OK ]
Compile the kernel (done) [ OK ]
Copy driver man page into /usr/share/
Check the driver (done) [ OK ]
Delete old driver (done) [ OK ]
Copying driver (done) [ OK ]
Make dependency (done) [ OK ]
Delete temp directories (done) [ OK ]
All done. Driver installed and loaded.
To load the module manually, proceed as follows:
Enter "modprobe sk98lin"
Revision history for this message
|
#11 |
Well, that looks good thanks!
I've just copied >30GiB of files and it hasn't hung. I'm copying another 242GiB across the network so that'll give me confidence if it works.
Thanks for the help!
:)
Revision history for this message
|
#12 |
Thanks Thomas Krüger, that solved my question.
Revision history for this message
|
#13 |
Well, 250GiB copied fine so it looks to be reliable. Great stuff.