file transfer problem
Theodore Heise
Hi all,
This may be a samba question, but I thought I would start here.
I'm trying to transfer a 10 GB file from my linux server (running
Slackware 10.2) to an NTFS partition on a WinXP box on the LAN.
After mounting the partition as such:
mount -t smbfs -o username=*****,password=******* //hobbes/D /mnt/hobbes
I begin the transfer process thusly:
cp /bkp/hobbes/docs.03Jan2010 /mnt/hobbes/
The process craps out at 2 GB transferred with the following error
message:
File size limit exceeded
I've searched the web on this and found others with the same
problem, but not found any answers.
Interestingly, the file I want to transfer is a 10 GB backup file
that originated on the Windows box. I moved it to the Slackware
box with the following:
/bin/tar upvf /bkp/hobbes/docs\.$DATE /mnt/hobbes/docsandsettings.bkf
SHould I just be using tar to transfer it back to the Windows
computer?
What I really want is the Windows backup file renamed with the
date, so I can keep multiple backups on that partition. Suppose
it would be best just to rename the file on the windows partition
using the same script that tars it to the slack box.
--
Theodore (Ted) Heise <th...@heise.nu> Bloomington, IN, USA
Douglas Mayne
Slackware 10.2 is a bit dated at this point. In addition, the smbfs
kernel module is unmaintained (last time I checked- I am surprised it is
not yanked out of the kernel tree.) cifs replaced smbfs, and will most
likely not be subject to a signed 32-bit integer limit. Try mount.cifs,
but you may need something newer than 10.2.
--
Douglas Mayne
Theodore Heise
Douglas Mayne <do...@localhost.localnet> wrote:
> On Sun, 03 Jan 2010 11:52:44 -0500, Theodore Heise wrote:
>
>> Hi all,
>>
>> This may be a samba question, but I thought I would start here. I'm
>> trying to transfer a 10 GB file from my linux server (running Slackware
>> 10.2) to an NTFS partition on a WinXP box on the LAN. After mounting the
>> partition as such:
>>
>> mount -t smbfs -o username=*****,password=******* //hobbes/D
>> /mnt/hobbes
> Slackware 10.2 is a bit dated at this point. In addition, the
> smbfs kernel module is unmaintained (last time I checked- I am
> surprised it is not yanked out of the kernel tree.) cifs
> replaced smbfs, and will most likely not be subject to a signed
> 32-bit integer limit. Try mount.cifs, but you may need something
> newer than 10.2.
Looks like cifs is available, so I will give this a try, assuming
I can get things straightened out (see next)...
>> ...Suppose it would be best just to rename the file on the
>> windows partition using the same script that tars it to the
>> slack box.
I went ahead and tried this (mounting the smbfs share and running
mv), and it worked for 15 minutes or so--until the / partition
filled up. I'm not finding any files that have been created, any
help on this little problem would be *most* welcome.
Theodore Heise
Douglas Mayne <do...@localhost.localnet> wrote:
>
>> This may be a samba question, but I thought I would start here.
>> I'm trying to transfer a 10 GB file from my linux server
>> (running Slackware 10.2) to an NTFS partition on a WinXP box on
>> the LAN. After mounting the partition as such:
>>
>> mount -t smbfs -o username=*****,password=******* //hobbes/D
>> /mnt/hobbes
> Slackware 10.2 is a bit dated at this point. In addition, the
> smbfs kernel module is unmaintained (last time I checked- I am
> surprised it is not yanked out of the kernel tree.) cifs
> replaced smbfs, and will most likely not be subject to a signed
> 32-bit integer limit. Try mount.cifs, but you may need something
> newer than 10.2.
Looks like cifs is available, so I will give this a try. Thanks!
Theodore Heise
Theodore Heise <th...@heise.nu> wrote:
>> On Sun, 03 Jan 2010 11:52:44 -0500, Theodore Heise wrote:
>>
>>> ...Suppose it would be best just to rename the file on
>>> the windows partition using the same script that tars it to
>>> the slack box.
>
> I went ahead and tried this (mounting the smbfs share and
> created, any help on this little problem would be *most*
> welcome.
Sorry to follow up on my own post, but I thought this one had
failed. I got an error message from slrn, and apparently after I
got things cleaned up it went ahead and posted.
It turns out I goofed in the rename process, and inadvertantly was
moving the file to my root directory. Once I got this deleted,
everything was fine.
By the way, renaming the file directly on the smbfs mounted share
works just fine--with correct syntax, that is!