NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Amazon S3 not sync for ReadyNAS home directories
I have a ReadyNAS 2304 that has been syncing a share to an Amazon S3 bucket for a few years. This has worked well. I recently configured a second session on the ReadyNAS to sync the user home directo...
Home "directories" are actually BTRFS sub-volumes if properly created by the OS. They are only created automatically after the first time the user logs in. So if you created a user and then, not finding the home directories, manually created them as standard directories, that could be the issue. Once you created them, the OS could no longer create the sub-volumes because there would be a name conflict.
There is a command available via SSH to force creation of home directories, it's mkhomedir_helper.
See if btrft subvolume list /home shows them as subvolumes. If it doesn't, you can move the incorrectly created directories elsewhere, properly create hem, and then copy the contents of the old ones to the new ones.
akbeer wrote:
The only other thing that I can think of is that it is possible that I had created a some of the home directories manually / they may not have been created by the frontend webpage. The permissions appear to be the same on all of the home directories, at least, the home directories themselves.
Did you check the ACL?
How did you create them?
Home "directories" are actually BTRFS sub-volumes if properly created by the OS. They are only created automatically after the first time the user logs in. So if you created a user and then, not finding the home directories, manually created them as standard directories, that could be the issue. Once you created them, the OS could no longer create the sub-volumes because there would be a name conflict.
There is a command available via SSH to force creation of home directories, it's mkhomedir_helper.
See if btrft subvolume list /home shows them as subvolumes. If it doesn't, you can move the incorrectly created directories elsewhere, properly create hem, and then copy the contents of the old ones to the new ones.
Ahh, thank you for the information! Using the btrfs command I was able to determine that the only two home directories that were syncing were the two that I must have manually created. The ones that were created properly / by the system / with mkhomedir were the ones that were not syncing.
I found that I can solve the syncing problem by manually creating a syncing session for each home directory itself (/data/home/userxx) instead of the broader /data/home).One more question. I see in each home directory (including the ones that I manually created), the system creates an .ssh folder with an empty ssh_authorized_keys file, perhaps to keep users from logging in via ssh. I have been unable to delete this file which is preventing me from deleting the two manually created home directories (even after renaming them). As root I should have permissions and using getfacl I don't see a reason why I shouldn't be able to. If trying to do via the command line, I get an error 'rm: cannot remove 'ssh_authorized_keys': Operation not permitted'. If I delete via the web front end it just silently fails.
My NAS have no such files in the home folders. Perhaps they were created due to the S3 sync?
The file and .ssh directory exist in ALL home directories, even the ones that I haven't yet setup to sync with S3. I had even tried rebooting the NAS as well. Not a huge deal I guess, just a little messy.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
