Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

Error 0x80070299 copying file to ReFS

$
0
0

We're retiring a 2008r2 file server using NTFS and migrating the files to a Server 2016 server using ReFS.  Using robocopy to pre-seed the files, a small percentage of the files failed to copy.  The robocopy log reported:

ERROR 665 (0x00000299)...The requested operation could not be completed due to a file system limitation

Trying to manually copy the file generated the error:

Error 0x80070299 the requested operation could not be completed due to a file system limitation

The files copy correctly to NTFS volumes, but trying to copy to any ReFS volume on any server generates the error.  If I copied the file to a FAT32 partition (to strip the NTFS metadata), it would then copy to an ReFS volume with no error, but trying to strip the attributes by going to the file properties, Details tab, and using the "Remove properties and Personal Information" option had no effect (it still failed to copy).

I was able to narrow it down to the presence of a particular Alternate Data Stream (ADS).  All the files that failed have an ADS called "AFP_Resource", which is apparently for Mac compatibility (https://msdn.microsoft.com/en-us/library/dn392833.aspx).  If I remove that data stream or clear the contents of it, the file will then copy with no error.

However, we have a lot of files that also have that ADS that do copy successfully.  We have a fair number of Mac users, so I'd prefer not to remove that data stream from all the files that have it.  Ideally I'd like to remove whatever is problematic about the data stream and leave the rest intact.  Alternatively, it would also be helpful if anyone could re-assure me that removing that data stream won't negatively impact our Mac users.  I suspect it's not important, but I'd rather not find out by stripping the stream from thousands of files and end up getting a bunch of phone calls. ;)

I suspect I'm going to end up using robocopy to identify the problematic files and then script removing this ADS just from those files, but if anyone has more info on this I would love to hear it.

More info below for those who might also be struggling with this.  It took me a few hours to track this down, so hopefully this will save someone else some time.

You can see what alternate datastreams exist for a file using either of the following:
dir /w
get-item <filename> -stream * | select Stream,Length

Remove a data stream:
remove-item <filename> -stream <stream name>

Clear contents of a data stream:
clear-content <filename> -stream <stream name>

View contents of a data stream:
Clear-content <filename> -stream <stream name>

Decent blog post explaining NTFS attributes (particularly $DATA, but also $STANDARD_INFORMATION, $FILE_NAME, etc.):
https://blogs.technet.microsoft.com/askcore/2009/10/16/the-four-stages-of-ntfs-file-growth/





Viewing all articles
Browse latest Browse all 13565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>