Yes I am using samba to connect to the XP box as you suggested. The error report arrived via mail from a cron, prehaps the garbling of the message occured there?
Anyway thanks again for responses, I usually clean up /tmp after the script runs so I made the assumption later on that the error was at the point of creation of the file and not during the cp, so as a way of confirming this I have set it off again to make the very large tgz and then try too cp it via samba transport to the XP box. [will run overnight now] If it works ie. if the full file is created [waiting in /tmp] then it is samba or if not then a post back to the shell limit. Should know by morning. An interesting chase regardless and if it is samba then will have to split the tgz. Many thanks for the responses stu ps. Apologies for the blogish nature of my emails but I try to make it as clear as possible for myself to if nothing else help me to understand next year when I have forgotten :) and with luck others will get a tip here or there. On 9/13/05, Willie Wong <[EMAIL PROTECTED]> wrote: > On Mon, Sep 12, 2005 at 11:40:05PM +0200, Stuart Howard wrote: > > Further reading further problem, > > > > I have been through the reiserfs FAQ and discovered that with 2.4 - > > 2.6 kernels that the file size limit I have posted below should not be > > an issue ie. I should be version 3.6 and therefore file size is well > > ... biG > > > > So I now need to discover where the fault lies, the error message was > > "File size limit exceededcp" > > no google, dogpile or yahoo search admits to ever knowing this error > > however I suppose the clue is in "-cp" ? > > the cp is from your command: cp /tmp/fullsysbackupusr.tgz ... > The error message is NOT File size limit exceededcp. The error message > should be > .... line 30: cp /tmp/fullsysbackupusr.tgz ... File size limit exceeded > I am not quite sure why the error message got jumbled up the way it > did in your case. > > > To recap the commands I am calling are > > tar -czf /tmp/fullsysbackupusr.tgz /usr > > cp /tmp/fullsysbackupusr.tgz /mnt/NEWSTU/genstubackup/fullsysbackup > > The source is Gentoo box 2.6.11.5 on a reiserfs partition, the file is > > created but will not exceed 2Gb or 2,147,483,647. Once created [though > > the file should be larger] it is dutifully transfered to the XP box > > via cp. > > The problem is here. The kernel code used to access smbfs (I presume > that is how you mount your XP box to /mnt/NEWSTU?) has a file size > limit of 2/4GB (I am not quite sure about the number). > > http://lists.suse.com/archive/suse-amd64/2004-May/0058.html > > W > -- > Thesaurus: ancient reptile with an excellent vocabulary. > Sortir en Pantoufles: up 32 days, 1:31 > -- > [email protected] mailing list > > -- "There are 10 types of people in this world: those who understand binary, those who don't" --Unknown -- [email protected] mailing list
