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

Have you tried mounting with the lfs options?

Thanks
chuck

I am configuring it from the server side - and accessing it through windows
client, so passing lfs option to smbmount is not possible or i am not aware
of how to :)
Update on the bug: I compiled debian package with --enable-largefile - no
change.
Then created a custom patch which would always call ftruncate64() in
sys_ftruncate() - however client would still throw up error while copying
large files.

Thanks for the reply,

Regards,
Salil

On Fri, Sep 4, 2009 at 10:06 PM, Chuck Short <email address hidden>wrote:

> Have you tried mounting with the lfs options?
>
> Thanks
> chuck
>
> ** Changed in: samba (Ubuntu)
> Status: New => Incomplete
>
> --
> On samba of ubuntu-arm, large file copy fails
> https://bugs.launchpad.net/bugs/416313
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> 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.
>

Hi Salil,

I was wondering if you were still having this problem?

Regards
chuck

Hi Chuck,
Thanks for replying.

Unfortunately the bug is still observed - i did some additional triaging.
* The bug is seen only when the samba share exported is on a vfat file
system - for ext2 and ext3 the large sized copy succeeds without fail.
* I also tried using the samba package from debian-arm
repositories(lenny-stable) - but there also the problem is seen.
* Even if the error is thrown up - the file is still being copied in the
background - or ftruncate'ing in the background (I suspect it is only
ftruncating and filling the space with zeroes because of two reasons - one
the md5sums do not match afterwards and two the code seems to be doing the
same thing) - but as previously stated adding a patch to always call
ftruncate64() in sys_ftruncate() does not fix the problem.

Regards,
Salil

On Mon, Nov 30, 2009 at 7:17 PM, Chuck Short <email address hidden>wrote:

> Hi Salil,
>
> I was wondering if you were still having this problem?
>
> Regards
> chuck
>
> ** Changed in: samba (Ubuntu)
> Importance: Undecided => Low
>
> --
> On samba of ubuntu-arm, large file copy fails
> https://bugs.launchpad.net/bugs/416313
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> 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.
>

Setting back to new since this bug submitter responded

from teh last comment it is not really clear to me if thats a vfat or actually a samba issue, since it doesnt seem to happen with different other underlying filesystems but seems to only occur on vfat.

salil, if you use debians samba package, do you see the same behavior wrt ext2/3/4 vs vfat ?

Apologies for not being clear and informative in the previous comment.

Yes even in the debian samba package, the error is seen for vfat only - not
for ext2/3.

My preliminary opinion is that the issue is with respect to the way samba is
currently handling large file transfers for vfat file systems and hence not
necessarily a vfat issue.
But as it is seen only on ARM platform, maybe something going haywire while
handling large files because of some ARM specific peculiarities like
alignment issues etc.?

Regards,
Salil

On Wed, Dec 2, 2009 at 7:42 AM, Oliver Grawert <email address hidden> wrote:

> from teh last comment it is not really clear to me if thats a vfat or
> actually a samba issue, since it doesnt seem to happen with different
> other underlying filesystems but seems to only occur on vfat.
>
> salil, if you use debians samba package, do you see the same behavior
> wrt ext2/3/4 vs vfat ?
>
> --
> On samba of ubuntu-arm, large file copy fails
> https://bugs.launchpad.net/bugs/416313
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “samba” package in Ubuntu: Confirmed
>
> 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.
>

I started to having exactly the same problem on Synology NAS with Samba 3.2.14-1 from NSLU2 Linux. It actually works fine with Ubuntu 9.10, Windows XP and Windows Vista. The troubles started with Windows 7. I have tested copying files of various sizes. Up to ~200 MB was all fine, above that Windows 7 complain about access rights to the folder.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Salil, did you try newer version of Ubuntu ARM? Does the issue persist?

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.

[Expired for samba (Ubuntu) because there has been no activity for 60 days.]