|
|
Post by itrice on Nov 16, 2007 23:53:21 GMT 7
I have set up nsync to back up to a remote ftp server and it seems to complete the backup but the status stays at "acl setting" and never changes. Since the status doesn't ever show complete it will not automatically start again. What does the "acl setting" message mean and any ideas on how to fix it?
|
|
|
|
Post by itrice on Nov 27, 2007 23:01:18 GMT 7
Has no one else had this problem?
|
|
|
|
Post by leebaldock on Sept 20, 2008 21:26:58 GMT 7
Hi, yep I am looking at it right now. It's the first test I have done with nsync. All the files appear to have copied successfully however it's stuck on "In Progress" with the Status "Acl Setting " Not sure how much longer it's going to be like that. Hope it's meant to be like that!  |
|
|
|
Post by minsik on Oct 8, 2008 18:00:53 GMT 7
YUP i had thAT when using nsync between 2 thecus 5200. Worked one way and not the other.. one 2.004 and one 20012 fw.
after update to fw 2..0012 on both it worked both ways without problem.
Just what i found.
minsik
|
|
|
|
Post by perplexed1 on Aug 21, 2009 4:46:11 GMT 7
I'm experiencing this "Acl setting" status hang right now (Aug 2009) for most of my nsync ftp transfers.
N4100PRO on the latest firmware: v2.01.09
I've found that a small nsync file set (~190 files) ftp's over fine... but any of the larger nsync transfers see their status hang at "Acl setting" step of the transfer. This requires a manual "Stop" click in the UI before the next scheduled nsync can occur.
Looking at a network trace of the ftp session... what I've noticed is that the files do seem to be copied over just fine, but for some reason the N4100PRO's nsync process is shutting down the ftp session before its written the .acl file for the backup set in the nsync target directory.
It works for my lower file count nsync, but isn't for the transfers where a good number of individual files have been sent over. For example, one folder has ~7000 files, and the ACL file isn't written before the ftp server sees the nsync process drop the ftp session (immediately after the last file is transferred).
I'm wondering if the nsync process is choking on the amount of ACL data associated with these larger file count transfers. I estimated, based on the successful nsync acl file content, that my failing 7000 file transfer would have produced an ACL file ~84,000 lines long (the ACL file uses ~12 lines per file to describe its permissions/ownership/etc.) and about 1.75MB in size. Could it be that at some point the nsync process doesn't have enough space allocated in an internal data structure to process the ACL data into a file to be copied over the the target ftp server?... The fact that the N4100PRO doesn't see a status update from the nsync process indicating "Failed", and the sudden drop of the ftp session to the target server, might be suggestive of an unexpected nsync process abort...
I have a ticket open with Thecus tech support, and am hoping it can be reproduced. If I can get the time, I'm also planning to experiment with different numbers of files in the nsync ftp backup set... to see if I can find roughly where the tipping point is... if it is indeed related to the number of files, rather than some other trigger.
I'd be interested to hear if anyone else is successfully ftp nsync'ing folders with file counts >=7000 files.
One of the folders I'm attempting to periodically nsync is my iTunes library, which has >9k files (one per track). I'd think others out there have media libraries with similarly large numbers of files to backup.
This thread is fairly old, so I'd be interested to find out if anyone experiencing this issue found a solution/cause.
|
|
|
|
Post by marspd on May 13, 2010 17:05:44 GMT 7
Hi there
Did this problem ever get resolved at all? I have the same issue and I am on version 02.00.16.
Regards
Paul
|
|
