[Bug 416313] Re: [arm] large file copy fails from a vfat filesystem through samba

[Tobin Davis]

I have failed to reproduce this in precise using the following setup:

Samba server (Panda):
3 20G LVM partitions (vfat, ext4, ntfs)

Clients:
Windows XP Pro
Windows 7 Home Starter Edition.

I used a daily-preinstalled desktop omap4.img.gz as the payload file,
copying it to each of the above 3 samba share points.  I then ran md5sum
on the panda to verify the image files.  The only issue I have seen is
the vfat partition somehow was given a date stamp of Dec 31, 1969 (could
be a vfat or samba issue - unsure).  Other than that, I had no issues
copying the files.

** Changed in: samba (Ubuntu)
       Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/416313

Title:
  [arm] large file copy fails from a vfat filesystem through samba

Status in “samba” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: samba

  I am using ubuntu-arm on Sheevaplug platform - Jaunty-9.04 - A samba share is exported, I can access it fine from windows copy/paste  small sized files easily. But when I try to copy a larger sized file, greater than 100 M or so, the copy fails after a minute or so saying 'Network Name is no longer available'. Now the copying is still going on in the background - because I can see the size of the file increasing via console on the sheevaplug.  I have fair reason to believe that this might be the call to ftruncate() which is taking a lot of time. So a way out might be to compile samba again with 'enable large-file' support of something similar.
  Right now it appears to be broken.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/416313/+subscriptions