FTP/samba woes...
 

I have some data which I need to move from my Linux (RH7) server over to one of my hard disks on my Windows2K machine.
Now prior to my Linux days, this would be done in an hour or so, simply by copying the files over the network.

Since using Linux, I have been using samba, and although I have had a few problems in the past, nothing like this.

In the past the problems have been limited to a few corrupt files, and possibly having to try 3 or 4 times in order to complete the transfer. I would like to stress though that this operation between the Linux and Windows mahcines took a good deal more time to complete, from what it used to with 2 Windows machines.

Anyway, this time, to avoid the problems from the past, I decided to try transferring the files via FTP, been at it for 17 hours now, and only 10% done. It is only 6Gb of data, and during this time, I've stopped some of the other services on the box to try and minimise any issues.

Surly this should not take that long...

Comments appreciated, as always!

Re: FTP/samba woes...
 

How did you do it? Did you mount a linux smb share and copy using widows, mount a windows smb share and copy using linux, or what? I would mount the windows smb share (see "man smbmount") and copy from linux. If you have to resume from somewhere in the middle, something like mirrordir could be useful.

How fast is your ethernet? What ftp program are you using? Other services shouldn't interfere.

I used to copy by mounting a Linux share. ie copying using "drag and drop" on the Windows machine.

Currently I am using WS_FTP Pro in Windows and ftp version 0.17-6 defualt install on RH7

My Network is all 100Mbs, except for a Sparc station which is currently not connected.

Command line tools might be more dependable.

That's strange how slow it is. Are you getting any error messages in /var/log/messages?

There are a lot of errors in here...

typically:

kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }

kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=104698583, sector=102545810

kernel: end_request: I/O error, dev 03:06 (hda), sector 102545810

I am assuming that the above is NOT normal...

Yeah, looks like you might have some bad blocks on hda. Is that the one you're copying data from? You'll probably need to run fsck from a rescue disk, or at least verify that e2fsprogs isn't corrupt by doing "rpm --verify e2fsprogs".

to check for network errors run this

ifconfig

example...

[root@www root]# ifconfig
eth0 Link encap:Ethernet HWaddr xxxxxxxxxxxxxxxxx
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:29050222 errors:0 dropped:0 overruns:0 frame:0
TX packets:31519321 errors:0 dropped:0 overruns:10 carrier:0
collisions:0 txqueuelen:100
RX bytes:3319663576 (3165.8 Mb) TX bytes:3485113999 (3323.6 Mb)
Interrupt:11 Base address:0xf000





look for excessive errors

Runing the rpm verify command, simply returned the name and version, which I assume is fine.

There are no errors detected when ifconfig. as follows:

eth0 Link encap:Ethernet HWaddr 00:50:BF:42:8B:6C
inet addr:192.168.254.199 Bcast:192.168.254.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:8985052 errors:0 dropped:0 overruns:0 frame:0
TX packets:7949402 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:11 Base address:0xec00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:311 errors:0 dropped:0 overruns:0 frame:0
TX packets:311 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

Seems like it may be the hard drive, as I have had to run fsck a good number of times, after an uncontrolled shutdown.