site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com User-agent: Mutt/1.5.17 (2007-11-01) This is a known problem with a fix in the pipeline. It is quite unfortunate that the capability defined to indicate "large file support" (i.e. supports files >4GB) was misnamed/misdocumented as the capability of supporting files >=2TB. Combine that with an NFSv3 file server that reports a maximum file size less than 2TB and confusion ensues... Thanks --macko On Thu, Mar 20, 2008 at 11:30:31AM -0700, Doug Rudoff wrote:

...

From an OSX 10.5.2 system I have not been able to copy a file larger than 4Gb using drag-and-drop to an NFS server. The error message is "Sorry, the operation could not be completed because an unexpected error occurred (Error Code 0)"

I've confirmed the same problem with these NFS servers: - Linux CentOS 4.6 - FreeBSD 5.4 - FreeBSD 6.1 - Solaris 9

There has been no problem copying using the command line.

It seems likely that this is related to Quinn's message from November: http://lists.apple.com/archives/darwin-kernel/2007/Nov/msg00092.html

Quinn wrote:

...

At 15:01 +0400 20/9/07, Alexander Obuschenko wrote:

...

There is a problem when copying a file greater than 4 GB to partitions mounted by our fs-plugin (NTFS for Mac OS X driver) using the Finder application. ... After a bit of digging I've discovered that this error indicates that the file is too large for the destination volume. Specifically, the file is 'large' (4 GB or more) but the destination volume does not indicate that it supports large files. ... The kernel's getattrlist compatibility code sets this attribute based on the value you put in the f_capabilities attribute returned by your VFS plug-in's getattr VFS entry point. In your case you're stating that your volume understands the VOL_CAP_FMT_2TB_FILESIZE capability (the value is set in the "valid" field) but it does not support that capability (the value is clear in the "capabilities" field).

If your VFS plug-in does actually support files of 4 GB or larger on disk, I recommend that you claim to support this by returning the VOL_CAP_FMT_2TB_FILESIZE capability set.

...

From this I can infer that it appears that Apple's VFS plug-in for NFS doesn't have doesn't have the VOL_CAP_FMT_2TB_FILESIZE capability set.

My questions are: 1) Is there any way around this NFS 4Gb limitation now? 2) Is Apple aware of this problem? 3) Will this be fixed in an upcoming release?

Many thanks for any help.

Doug Rudoff | Software Engineer Isilon Systems P +1-206-315-7500 F +1-206-315-7485 www.isilon.com D +1-206-315-7674 How breakthroughs begin.(tm)

_______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/macko%40apple.com

This email sent to macko@apple.com

Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com