Re: [Ani-users] Re: Interrupted transfers from samba share
Status: Beta
Brought to you by:
substring-sfn
From: Till W. <t.w...@su...> - 2005-04-15 10:45:42
|
Alex Goller schrieb: >On Wed, Apr 13, 2005 at 03:58:17PM +0200, Till Wimmer wrote: > > > >>Have a look in /ani.log. Maybe there is a more verbose error message >>from the cp command... >> >> > >Ok, cp is setting errno $! and the exit code $? ($! = "Illegal seek", >$? = 256). That's all information i get. > > Did you find the ani.log file? It should contain the output from cp command, not the one of the perl script. Did you try to copy the share by hand? Maybe you find the reason for your troubles by that way... >One thing i found interesting is the smbfs bug you're mentioning in >the sourcecode of Ani.pm, could this cause the sort of problems i have? > > No i don't think so. The bug makes files on the mouted samba share disapear sometimes. Cp hasn't any problem with this, but winnt.exe does ;) Yes it's a awful thing.... (It's a bug in the smbfs-part of the kernel concerning the caching of the directory listing. It only appears when share with huge directories are mounted. I tried to fix this some years ago but i gave up because of bad cooperation between the samba and kernel team. Maybe that's different today?!) >(i found out that it happens when using my scsi box with a MPT Fusion >controller as well as a Fujitsu Siemens Celsius workstation with SATA >disks, 2.4.30 should handle those fine and probes the controller and >disks as ICH5-SATA, so i think this is not a SATA problem). >I still can't copy all the files over. Will provide a more verbose log >later or tomorrow. > > Yes please... We are very interested in that! >Another thing was pretty crazy this morning. I have changed file in >manix.bz2 and repacked the archive with tar cjvf manix.bz2 ><mymanixfiles>. The tar on the installroot couldn't create the block >and character devices in /mnt/tmp/dev, so the chroot failed >(prepare.sh). I wasn't aware of such tar incompatibilities and i still >need to find a tar that's working. Right now i'm copying the devices >over to the new root. > > I'm using tar (GNU tar) 1.13.25 at the moment without any problems. Does tar need some kernel headers to compile (file system or something)? Maybe there is some incompatibility... bg Till -- Where do you want to go today? - ANIwhere! http://ani.sourceforge.net |