Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am attempting to migrate an aging SMB shared folder to a new server via rsync. Most of the files transferred fine; but, many critical ones did not as they seem to be read-only. The origin location is a directory on the host machine's boot drive with 777 permissions. I have tried recursively CHMOD'ing the directory to add write permissions but the process fails just as the rsync does. file owner/group for all is the Samba nobody:nogroup. sudo chmod doesn't help.
If the original host is a Windows machine, that is where I would change the permissions.
If I could not, the next best way is to use a true backup or archive tool to grab an image to a *nix machine, change permissions there, and port that to the final destination( perhaps using rsync).
Windows will just fight you forever on some things, this may be one.
Both machines are linux...
Issue seems to be a drive that is dying. I had someone in the office connect a monitor to the suspect server (I SSH in remotely) and a reboot revealed drive errors that were recoverable. Looks like retiring that machine was a good idea after all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.