Error in script execution
in [Slackware]
|
Prev: Samsung ML-1610
Next: PAM
From: CL on 4 Mar 2006 07:47 richard wrote: > CL wrote: > >> Hi, >> Recently this message display during execution of my script. What does it >> mean? & how can I solve it? Thank you in advance. >> >> /root/bin/backup.sh: line 16: 20213 File size limit exceededcp >> ~backup/`date +%Y%m%d`/* /mnt/myserver/`date +%Y%m%d` >/dev/null > > What version of Slackware are you using? (10.2) > What shell is this script using? (BASH, TCSH) > What type are the filesystems that data is being copied from and to? (EXT2, > REISERFS) > > Does googling "File size limit exceeded cp" bring you any clues? > > Richard :) Hi, Thank for seriously trying to help. > What version of Slackware are you using? (10.2) 8.1 > What shell is this script using? (BASH, TCSH) BASH > What type are the filesystems that data is being copied from and to? (EXT2, REISERFS) REISERFS > Does googling "File size limit exceeded cp" bring you any clues? Oh. I try "20213 File size limit exceededcp" before posting & it has no hit.
From: Loki Harfagr on 4 Mar 2006 13:42 Le Sat, 04 Mar 2006 20:36:47 +0800, CL a ?crit?: > Loki Harfagr wrote: >> Le Sat, 04 Mar 2006 08:26:05 +0800, CL a ?crit : >> >>> Hi, >>> Recently this message display during execution of my script. What does it >>> mean? & how can I solve it? Thank you in advance. >>> >> >> Means that the target's filesys has limits on maximal size for a file >> and you happened to reach it. >> Filesys have limits on sizes for file and system, some are a bit >> small, are you trying and backup a big disk onto a VFAT partition ?-) >> >>> /root/bin/backup.sh: line 16: 20213 File size limit exceededcp ~backup/`date >>> +%Y%m%d`/* /mnt/myserver/`date +%Y%m%d` >/dev/null >> >> Maybe, tryoing the script again and not throwing the 1> messages would >> at least tell you on which file it happened, though if you have only >> one *big* file you know it, these are *your* files, and from here I can't >> see your tree :D) > > Thank Loki. I think this is the situation. But if I remember correctly, > it is NTFS. Have to check first. Thank for helping instead of acting up > just because you are trying to help. You're welcome ;-) I don't get it about the "it is NTFS" though you replied to Richard that the target filesys was Reiserfs ? What are your running versions of filesys ? (like # ntfsinfo -V # e2fsck -V and so on ?-) ) Is the target on a samba link ? If so, tell us about : # smbclient -V Though I'n not sure of the 2GB limit in Samba, I use it quite rarely since the scp, NFS and other means of giving to the poor are alive :-) Ah, and what is the size of the big file that causes the error ?
From: Henrik Carlqvist on 4 Mar 2006 13:59 Loki Harfagr <loki(a)DarkDesign.free.fr> wrote: > Is the target on a samba link ? > If so, tell us about : > # smbclient -V > > Though I'n not sure of the 2GB limit in Samba, I use it quite rarely > since the scp, NFS and other means of giving to the poor are alive :-) I have tried running both Slackware 9.1 (with kernel 2.4.22) and Slackware 10.2 (with kernel 2.4.31) in qemu which uses samba to export the host file system to the emulated computer. Smbmount with the 2.4.22 kernel is not able to handle files bigger than 2 GB, but the 2.4.31 kernel is able to handle those files. The OP was running Slackware 8.1 so I suppose that he is unable to handle files bigger than 2 GB on an smb mount. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc7(at)uthyres.com Examples of addresses which go to spammers: root(a)variousus.net root(a)localhost
From: Loki Harfagr on 4 Mar 2006 14:41 Le Sat, 04 Mar 2006 19:59:57 +0100, Henrik Carlqvist a ?crit?: > Loki Harfagr <loki(a)DarkDesign.free.fr> wrote: >> Is the target on a samba link ? >> If so, tell us about : >> # smbclient -V >> >> Though I'n not sure of the 2GB limit in Samba, I use it quite rarely >> since the scp, NFS and other means of giving to the poor are alive :-) > > I have tried running both Slackware 9.1 (with kernel 2.4.22) and Slackware > 10.2 (with kernel 2.4.31) in qemu which uses samba to export the host file > system to the emulated computer. Thanks for doing it, I was about to try it too but as I'm in a deep process of cleansing my home system because I only have a few GB free in all my approx 280 GB, (even have less than 200MB in /) I had to postpone the test :D) > Smbmount with the 2.4.22 kernel is not able to handle files bigger than 2 > GB, but the 2.4.31 kernel is able to handle those files. The OP was > running Slackware 8.1 so I suppose that he is unable to handle > files bigger than 2 GB on an smb mount. Agreed, that was the reason why I asked about SMB that time, though the filesys precision would also help in case there'd be a double bind case :-) The e2fs have had the 2GB limit bug sometime, now cured, the SMB had it until 3.0.2beta I think or so (*) ... Not sure, as I told I tend to use it barely except at work for some Wincaged servers and if so I mostly use 'scp' for the pushes, as the troubles with owners/rw in samba are at least boring :-) Now, you seem to say that SMB current still has the 32bits blockade, thanks for clarifying. To the OP, maybe, if that's the problem you're running in, would you try an NFS share, which has no file size limit. Other traps would be in some quota or /security/limits ? (*) Please, people that use it for real, and have knowledge on it correct and make precisions, what I say on SMB is mostly waist-shot :-)
From: richard on 4 Mar 2006 20:22
CL wrote: > richard wrote: >> CL wrote: >> >>> Hi, >>> Recently this message display during execution of my script. What does >>> it mean? & how can I solve it? Thank you in advance. >>> >>> /root/bin/backup.sh: line 16: 20213 File size limit exceededcp >>> ~backup/`date +%Y%m%d`/* /mnt/myserver/`date +%Y%m%d` >/dev/null > Hi, > Thank for seriously trying to help. > > > What version of Slackware are you using? (10.2) > 8.1 > > > What shell is this script using? (BASH, TCSH) > BASH > > > What type are the filesystems that data is being copied from and to? > (EXT2, REISERFS) > REISERFS from ReiserFS to NTFS through a SAMBA mount? > > Does googling "File size limit exceeded cp" bring you any clues? > Oh. I try "20213 File size limit exceededcp" before posting & it has no > hit. Upon googling for what I did I came across several different reasons for the error message. The main one being filesystem limits which is what I think is the problem here. Not sure of a solution off the top of my head yet. Mainly because I don't know what you are backing up (size) and to where (filesystem). Richard :) |