Hello Everyone!

 

I have been a longtime user and have received a lot of helpful information from this forum so I'm hoping you can help me out again.  Thanks in advance.

 

I recently upgraded to 6.3.1 and ever since, the mover does not work on my media files.  I should also say that after I updated, my cache pool was shown as 'unmountable' but I was able to get it back by running a btrfs check.  When it came back, my cache still had all the docker file structure in place but the dockers needed to be reinstalled.  I used my existing templates so from what I can tell the configuration for them has not changed.  I then ran a Scrub and Balance on my cache pool and all seemed to be working except for the Mover.

 

The files aren't moving from the Cache to the Array and the log is showing some kind of errors with extended attributes but I can't track down the cause.  I have included a snap shot of the error and the diagnostics from my server.

 

Any help is greatly appreciated even if anyone can at least point me in the direction I should be looking.

noahsarc-diagnostics-20170215-0829.zip

Another person with the same problem here: https://lime-technology.com/forum/index.php?topic=56652.0

 

ReiserFS is the thing you have in common. It would be best to consider changing to XFS.

 

Yes, that may be the final solution.  I'm a little concerned with doing that with 5TB worth of data over 4 drives.  I'll read the manual to see what the process looks like but in your opinion, is this a significant undertaking?

 

In the meantime, can you think of anything that would fix this?  Does it have anything to do with .DS_Store, .AppleDouble and other hidden files that are created from a Mac for AFP shares?

 

Thanks!

Personally I'd seriously consider it seeing that ReiserFS isn't supported as much as it used to and I would at switch all your future drives to XFS so you can make the transition eventually.

 

As for your Mac files I'm not sure. I haven't upgraded to 6.3.1 as of yet or used my Mac on that version.

It's time consuming, but not particularly daunting if you're clear in your mind what you're about to do. You don't need to stand over your server while it's copying the files so you can get on with other things.

 

It seems that ReiserFS's handling of extended attributes has been broken. I use AFP but all my hard disks are XFS-formatted. I have a tip for AFP users, here.

 

If you're using macOS Sierra you might want to give SMB a try.

I guess I'll get started reading up on how to change the filesystem to XFS.

 

Thanks for the AFP tip, I'll try that.  I am running macOS Sierra and none of my shares except TimeMachine are exported as AFP.  The rest are all SMB.

 

I'm also going to add this to my SMB extra config

veto files = /._*/.DS_Store/.AppleDouble/.Trashes/.TemporaryItems/.Spotlight-V100/
delete veto files = yes

 

Do you know of a way to scan my shares for these files and delete them automatically?  I looked at the cached media directories in MC but don't see them so I'm still not sure if thats even a problem.  Installing Krusader now to see if they show up there.

 

Thanks for the advice so far.

You could use something like

 

find /mnt/user/Sharename -name ._* -exec rm '{}' \;
find /mnt/user/Sharename -name .DS_Store -exec rm '{}' \;

 

etc.

 

Once you've converted to XFS you'll want to re-enable those files and folders in order to get the complete macOS experience!!

Is the first line of code a wildcard so it just looks for any files starting with ._  ?

Yes, just as it is in your veto line.

 

I have scrubbed all the shares of any .* Apple related files and still no joy...

 

If netatalk is enabling some kind of extended attributes and is the cause of my issue is there a way to disable it to test?

 

Thanks!

Extended attributes are not the same as Apple resource forks. The dot-underscore sidecar files are a means of storing resource fork information on basic file systems. If you created your boot flash on a Mac you probably have them there too on its FAT file system. So I don't really see how deleting them is going to make any difference anyway, since they are merely ordinary files with slightly odd names and normally hidden content.

 

Your problem, as I understand it, is not that macOS is creating .DS_Store files and ._* files but that files with extended attributes are being created on your cache which the mover is then unable to move to the array because ReiserFS is broken. I think it's the fact that you are using macOS with SMB with ReiserFS that is causing your problem. You might find that using AFP will work better than SMB until such time as you are able to convert to XFS.