LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 10-14-2006, 02:52 PM   #1
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Rep: Reputation: 32
Delayed write failure from winxp client writing to slackwarey 10.2


I am copying several hundred GB of files from a WinXP Pro box to a Slackware 10.2 box. Every now and then, the win client will show a "delayed write failure", and the bandwidth to the Slackware box stops. I can immediately continue the file copy. I'm trying to figure out of it's the win client, or the Slackware box causing this. The samba logs show nothing, and the win box event log only shows that the delayed write error occurred. Are there any other logs on the Slackware box that might give some more information?

I'm running a very small network - the boxes are connected via a Netgear GB switch, and there are only 4 wired boxes (plus 3 wireless boxes).
 
Old 10-14-2006, 03:23 PM   #2
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Original Poster
Rep: Reputation: 32
I am beginning to see a pattern here - I notice the failure keeps happening about halfway through a 4GB file. Is there a limit to the size of a file that can be copied/stored on an ext2 partition? Or might this be a Samba limitation?
 
Old 10-14-2006, 04:54 PM   #3
chadl
Member
 
Registered: Sep 2005
Location: US
Distribution: Gentoo AMD64 Testing
Posts: 129

Rep: Reputation: 16
The maximum file size for ext2 is 2tb, so that will not be a problem unless you have files much, much larger then 4gb. Some old kernels had problems with files larger then 2gb, but kernels that old are not very common any more.

One thing you could try is to copy the file using samba on the slackware box to the slackware box... and see if the file makes it OK. That would be able to show if there is a problem with the network or the slackware box. This will not come up with the answer right away, but will at least reduce the possibilities of the cause.
 
Old 10-14-2006, 09:14 PM   #4
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Original Poster
Rep: Reputation: 32
I tried it from the linux box, and it got about halfway there and failed with "File size limit exceeded". And I just realized that I'm copying it to a fat32 partition on the linux box, not an ext2 partition. So I tried to copy it to an ext2 partition, and it worked. I know fat32 can have files larger then 2GB, so my next question is, how do I get a 4GB file onto a fat32 partition that is on my linux box? I'm not quite sure where the restriction is
 
Old 10-14-2006, 10:52 PM   #5
chadl
Member
 
Registered: Sep 2005
Location: US
Distribution: Gentoo AMD64 Testing
Posts: 129

Rep: Reputation: 16
You will not be able to get a 4gb file onto a Fat32 partition. The maximum file size for fat32 is 4gb - 2 bytes.

As to why it fails half way through, I have no idea, as it should not run into a problem before it gets near the maximum file size for fat32. It could be that Samba is reserving the disk space for the file before the actually copying takes place or something, but that seems unlikely. I also don't know if the Kernel driver for fat32 has some odd problem with files that large, but seeing as the driver has been around for a while, it too seems unlikely.

I guess my next question would be: Do you have the same problem if you use Samba to save the 4gb file to an ext2 partition?
 
Old 10-15-2006, 12:26 AM   #6
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Original Poster
Rep: Reputation: 32
Quote:
Originally Posted by chadl
You will not be able to get a 4gb file onto a Fat32 partition. The maximum file size for fat32 is 4gb - 2 bytes.

As to why it fails half way through, I have no idea, as it should not run into a problem before it gets near the maximum file size for fat32. It could be that Samba is reserving the disk space for the file before the actually copying takes place or something, but that seems unlikely. I also don't know if the Kernel driver for fat32 has some odd problem with files that large, but seeing as the driver has been around for a while, it too seems unlikely.

I guess my next question would be: Do you have the same problem if you use Samba to save the 4gb file to an ext2 partition?
The file is actually 3.7GB, and currently resides on a fat32 partition. I can boot to Win98 and copy the file over, so I don't think it's a file system restriction. The failure occurs at 2GB - I've done this several times, and it's very consistent. It works fine copying to an ext2 partition.

I logged into the box and copied it from the ext2 partition to the fat32 partition, both on the same box. Same failure "File size limit exceeded" at 2GB, so I don't think it's a Samba limitation since I'm not going through Samba in this case. Could it be a kernel driver for fat32 limitation? That seems the next likely culprit, but I'm guessing as this is outside of my area of expertise.
 
Old 10-20-2006, 11:40 PM   #7
Ook
Member
 
Registered: Apr 2004
Location: Hell, Arizona
Distribution: Slackware 14.1
Posts: 359

Original Poster
Rep: Reputation: 32
Anyone have any ideas how to get around this? AFAICT, you just can't copy a 2gb+ file to a fat32 partition on a Slackware 10.2 box.
 
Old 10-21-2006, 01:02 PM   #8
theoffset
Member
 
Registered: Aug 2005
Location: Guadalajara, Jal, Mexico
Distribution: Slackware Linux
Posts: 211

Rep: Reputation: 30
It looks as if you were using fat16 instead of fat32...

I'm just guessing here, but maybe in your fstab you have fat16 or vfat (which I'm not sure if would automagically detect a fat32) as filesystem...

If so, try changing to fat32 and see if that works*


*Captcha: I'm not under any linux right now, so I'm totally guessing here...
Edit: **Double captcha: I hope you won't have to mkfs before trying fat32...

Last edited by theoffset; 10-21-2006 at 01:03 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Why is fmask & dmask required to write to a WinXP share mounted on Mdrake SMB client ruscook_oz Linux - Networking 1 02-08-2007 06:50 PM
FTP: vsftpd 451 Failure writing to local file xrender Linux - Networking 4 07-14-2006 05:33 AM
cd rom write failure in Mandrake 10.1 jt1020 Linux - Hardware 0 12-11-2005 10:19 AM
write failure on transfer during install Juniper34 Linux - Newbie 1 08-13-2003 08:17 PM
delayed write buffer question aditya General 0 09-12-2002 06:24 AM


All times are GMT -5. The time now is 04:19 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration