saxy

FWIW, I get some of those errors when backing up my mac to a zfs pool, so, in general, something to do with apple's filesystem. Agreed. Whats strange is that I can't quite recreate this issue... If I have some files with this Apple quarantine attribute set on my Mac, when I copy them to the server, get don't have the problem like these files did... So I'm not sure how they got this way. Fyi I created a script to find any files with this extended attribute (with errors) and remove the extended attribute, however I had already fixed those files in the process of testing, so I can't fully test the script. I also created a script just to find files with this attribute that have the error. Both scripts attached if anyone is interested or this helps anyone else... Just need to change the file path in the first part of it to the path you want to search from (I had it set to /mnt/disk1). http://cloud.tapatalk.com/s/57607fc95d023/scripts_apple_attrs.zip Sent from my Redmi Note 2

further to this, the syslog is telling me: Jun 11 09:48:55 Unraid kernel: REISERFS warning (device md1): jdm-20002 reiserfs_xattr_get: Invalid hash for xattr (user.com.apple.quarantine) associated with [208735 300497 0x0 SD] So... I'm not sure what is going on - is it that there is an IO issue, or that message about 'invalid hash for the xattr' means that it cannot read the attribute detail for some reason... maybe one option is to remove that attribute (as it is a Mac OSX one only that I presumably dont really care about...)

Hi All, FYI I am getting some further status 23 errors now myself... looking into the logs, I'm getting the following error: rsync: get_xattr_data: lgetxattr(""/mnt/disk1/Other/dev section 3.webm"","user.com.apple.quarantine",67) failed: Input/output error (5) so now I need to figure out why there is an IO error trying to get the xattr data

rsync exit code 23 - Partial transfer due to error I found that I had permissions problems... You could try running the 'new permissions' function in unraid to see if that resolves it for you... Otherwise check the files/folders on source and target, see if anything is owned by root our any other user other than 'nobody'. Sent from my Redmi Note 2

Did you try that rsync without the leading slash? Did that finish yours up? Yep, fyi finished it off with manual rsync - all successfully... And now after replacing a drive, and updating to 1.70 I'm successfully doing some more unBalancing Sent from my Redmi Note 2 using Tapatalk

I'm pretty sure your problems now are the same as I noted earlier, in that the 'relative' path is wrong on source... which will need to have the unBalance author fix, unless you want to manually rsync via command line...

FYI I manually rsynced the remainder of my data across to the other drive... One thing I noticed is some permissions issues... unBalance is running as user nobody, but for some reason there are some folders owned by user 'root' (maybe due to some manual moves I've done via console). So perhaps part of my fix was when I updated the folder ownership back to 'nobody' (recursively), for both the source folders AND the target folders... Just in case that helps anyone else out there (maybe alternative would be to run the 'new permissions' fix in Unraid)

Seems like it is erroring with status 23 due to a leading slash in the relative path, and thus is cannot find the source path... ie. in the logs it has: rsync -avRX --partial "/Other/.AppleDB" /mnt/disk3/ but it should be: rsync -avRX --partial "Other/.AppleDB" /mnt/disk3/

I have the same 0 byte issue on 1.5.2...

Hi Guys, I have a failed disk which is now automatically disabled by UNRAID and I'm trying to move the contents to other disks using unbalance... most of the contents have moved, but there are now two folders which have not completed, two different status code errors: 1. MOVE: Move command (rsync -avX --partial "/mnt/disk2/Other/.AppleDB" "/mnt/disk3/Other/") was interrupted: exit status 23 2. MOVE: Move command (rsync -avX --partial "/mnt/disk2/Backup/Hostaccino" "/mnt/disk3/Backup/") was interrupted: exit status 13 obviously I only get these errors when I enable one or the other folder and re-run. also, I cant find the unbalance.log ... is it supposed to be in /var/log/ ?