Re: rsync, what the hey?

a <[email protected]>
Newsgroups gmane.org.user-groups.linux.nmglug
Message-ID <[email protected]>
Ls the -r you recommend included in "-Prvvac"

On 5/27/19 5:13 PM, ABQLUG wrote:
> To make your command work, just remove the --dry-run.
>
> I would probably add the -r for recursive.
>
> So this is what I recommend.
>
> First, start out in a empty backup folder. Create one if you don't 
> want to remove the /backup folder.
>
> Then run this :
>
> rsync -Prvvac /home/a/ 
> /media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>
> That's a safer option, as long as the destination is empty. It will 
> also look for subfolders. Includes the . files and doesn't delete 
> anything in destination.
>
> Why your original command didn't work is a simple typo.
>
> You had this
> /media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>
> When it should have been this:
> /media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>
> Notice the /a/ after /media
>
> Regards,
>
> Jared
>
>
>
> On 5/27/19 5:05 PM, a wrote:
>>
>> What would be the home path and the destination path. since it was a 
>> test run it did not transfer to backup folder. What was the fix or 
>> where was the error was it on my side or the online reference?
>>
>> RESULT IN PART YOUR FIX
>>
>> smartmontools-6.6/os_win32/versioninfo.rc.in
>> smartmontools-6.6/os_win32/wbemcli_small.h
>> smartmontools-6.6/os_win32/wmiquery.cpp
>> smartmontools-6.6/os_win32/wmiquery.h
>> smartmontools-6.6/os_win32/wtssendmsg.c
>> smartmontools-6.6/regex/
>> smartmontools-6.6/regex/regcomp.c
>> smartmontools-6.6/regex/regex.c
>> smartmontools-6.6/regex/regex.h
>> smartmontools-6.6/regex/regex_internal.c
>> smartmontools-6.6/regex/regex_internal.h
>> smartmontools-6.6/regex/regexec.c
>>
>> sent 521,855 bytes  received 45,434 bytes  1,134,578.00 bytes/sec
>> total size is 299,316,051,752  speedup is 527,625.34 (DRY RUN)
>>
>> On 5/27/19 4:53 PM, ABQLUG wrote:
>>> Hi a,
>>>
>>> Does this work?
>>>
>>> rsync -av --dry-run --delete --exclude=".*/" /home/a/ 
>>> /media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>>>
>>> I would probably run that as this.
>>>
>>> sudo rsync -Prvvac /home/path /desination/path
>>>
>>> I prefer to keep . files and I also like the progress. -r is 
>>> recursive. I wouldn't delete anything though, unless you are in fact 
>>> wanting to make a true 1:1 copy of that /path/ at the given time you 
>>> run the command.
>>>
>>> Regards,
>>>
>>> On 5/27/19 4:47 PM, a wrote:
>>>>
>>>> output
>>>>
>>>> a@alap:~$ ls -lAs /media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>>>> ls: cannot access 
>>>> '/media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup': No such file 
>>>> or directory
>>>>
>>>> On 5/27/19 4:42 PM, ABQLUG wrote:
>>>>> Hi a,
>>>>>
>>>>> What is the output of this:
>>>>>
>>>>> ls -lAs /media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>>>>>
>>>>> Regards,
>>>>>
>>>>> Jared
>>>>>
>>>>> On 5/27/19 4:25 PM, a wrote:
>>>>>>
>>>>>> This is the entire method as I understand it, my reference:
>>>>>>
>>>>>> https://justinsomnia.org/2009/03/how-to-rsync-your-ubuntu-home-directory-to-an-external-hard-drive/
>>>>>>
>>>>>> 1.) a@alap:~$ rsync -av --delete --exclude=".*/" /home/a/ 
>>>>>> /media/your_uuid/backup
>>>>>> sending incremental file lis
>>>>>>
>>>>>> 2.)  rsync -av --delete --exclude=".*/" /home/a/ 
>>>>>> /media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>>>>>>
>>>>>> 3.) a@alap:/media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec$ mkdir 
>>>>>> backup
>>>>>> mkdir: cannot create directory ‘backup’: File exists
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> On 5/27/19 4:10 PM, ABQLUG wrote:
>>>>>>> Hi a,
>>>>>>>
>>>>>>> I believe that error is saying you're rsyncing to a non-existing 
>>>>>>> folder. What is the command you are using?
>>>>>>>
>>>>>>> Also, what is the output of:
>>>>>>> lsblk
>>>>>>>
>>>>>>> Thanks,
>>>>>>>
>>>>>>> Jared
>>>>>>>
>>>>>>> On 5/27/19 3:57 PM, a wrote:
>>>>>>>>
>>>>>>>> Jared
>>>>>>>>
>>>>>>>> thanks for the reply I took the easy way out with permissions 
>>>>>>>> used sudo nautilius. although it did dredge up shadow of the 
>>>>>>>> past with chmod.
>>>>>>>>
>>>>>>>> If you have the inclination can you illustrate rsync 
>>>>>>>> suggestions by referring to the terminal output below in this 
>>>>>>>> email. I created a backup folder. but get the following"  "Can 
>>>>>>>> anyone explain, attachment .png of uuid info. error seems to be 
>>>>>>>> between  /media/a/uuid and a "switch" occurs /media/uuid, what 
>>>>>>>> the hey/"
>>>>>>>>
>>>>>>>> and this error message: "rsync error: error in file IO (code 
>>>>>>>> 11) at main.c(675) [Receiver=3.1.2] "
>>>>>>>>
>>>>>>>> If the problem is to messy to decipher I will concur. Then 
>>>>>>>> thanks all the same, congrats on the new club. Best, a
>>>>>>>>
>>>>>>>>
>>>>>>>> On 5/27/19 3:17 PM, ABQLUG wrote:
>>>>>>>>> Hi a,
>>>>>>>>>
>>>>>>>>> When using rsync, the destination and originating path needs 
>>>>>>>>> to exist.
>>>>>>>>>
>>>>>>>>> rsync -Prvvac /path/to/old/archive /path/to/new/archive
>>>>>>>>>
>>>>>>>>> If the destination path doesn't exist, you will need to mkdir 
>>>>>>>>> and mount accordingly.
>>>>>>>>>
>>>>>>>>> However, your original question is how to change folder/file 
>>>>>>>>> permissions.
>>>>>>>>>
>>>>>>>>> This is how to change which user and group can access/edit a file.
>>>>>>>>> sudo chown username:usergroup /path/to/file.txt
>>>>>>>>>
>>>>>>>>> This is how to change which user and group can access/edit a 
>>>>>>>>> folder and everything in that folder:
>>>>>>>>> sudo chown -R username:usergroup /path/to/folder
>>>>>>>>>
>>>>>>>>> This is how I would do it on my current system (to change user 
>>>>>>>>> access to a folder):
>>>>>>>>> sudo chown jr:jr /path/to/file
>>>>>>>>>
>>>>>>>>> I know to use jr:jr because I did this:
>>>>>>>>>
>>>>>>>>> ls -l .bash_history
>>>>>>>>> -rw------- 1 jr jr 69881 May 24 13:34 .bash_history
>>>>>>>>>
>>>>>>>>> To do this you will need to be in your user folder (or ls a 
>>>>>>>>> file you know that you own).
>>>>>>>>> pwd
>>>>>>>>> /home/jr
>>>>>>>>>
>>>>>>>>> I didn't cover chmod, so let us know if you still can't access 
>>>>>>>>> the folder you're trying to access.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Jared
>>>>>>>>>
>>>>>>>>> On 5/27/19 9:25 AM, a wrote:
>>>>>>>>>> Hi
>>>>>>>>>>
>>>>>>>>>> Can anyone explain, attachment .png of uuid info. error seems 
>>>>>>>>>> to be between  /media/a/uuid and a "switch"  occurs 
>>>>>>>>>> /media/uuid, what the hey/
>>>>>>>>>>
>>>>>>>>>> a@alap:~$ rsync -av --delete --exclude=".*/" /home/a/ 
>>>>>>>>>> /media/your_uuid/backup
>>>>>>>>>> sending incremental file list
>>>>>>>>>> rsync: mkdir "/media/your_uuid/backup" failed: No such file 
>>>>>>>>>> or directory (2)
>>>>>>>>>> rsync error: error in file IO (code 11) at main.c(675) 
>>>>>>>>>> [Receiver=3.1.2]
>>>>>>>>>> a@alap:~$ rsync -av --delete --exclude=".*/" /home/a/ 
>>>>>>>>>> /media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>>>>>>>>>> sending incremental file list
>>>>>>>>>> rsync: mkdir 
>>>>>>>>>> "/media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup" failed: 
>>>>>>>>>> No such file or directory (2)
>>>>>>>>>> rsync error: error in file IO (code 11) at main.c(675) 
>>>>>>>>>> [Receiver=3.1.2]
>>>>>>>>>> a@alap:~$ cd /media/0435f0ab-9dfd-4d9d-ae8b-53101d419ac8
>>>>>>>>>> bash: cd: /media/0435f0ab-9dfd-4d9d-ae8b-53101d419ac8: No 
>>>>>>>>>> such file or directory
>>>>>>>>>> a@alap:~$ mkdir backup
>>>>>>>>>> a@alap:~$ cd /media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec
>>>>>>>>>> a@alap:/media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec$ mkdir 
>>>>>>>>>> backup
>>>>>>>>>> mkdir: cannot create directory ‘backup’: File exists
>>>>>>>>>> a@alap:/media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec$
>>>>>>>>>> a@alap:/media/a/6fbdc743-fc0f-46e4-aea3-8160914c34ec$ cd
>>>>>>>>>> a@alap:~$  rsync -av --delete --exclude=".*/" /home/a/ 
>>>>>>>>>> /media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup
>>>>>>>>>> sending incremental file list
>>>>>>>>>> rsync: mkdir 
>>>>>>>>>> "/media/6fbdc743-fc0f-46e4-aea3-8160914c34ec/backup" failed: 
>>>>>>>>>> No such file or directory (2)
>>>>>>>>>> rsync error: error in file IO (code 11) at main.c(675) 
>>>>>>>>>> [Receiver=3.1.2]
>>>>>>>>>> a@alap:~$
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> nmglug mailing list
>>>>>>>>>> [email protected]
>>>>>>>>>> http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
>>>>>>>>>
>>>>>>>
>>>>>
>>>
>

_______________________________________________
nmglug mailing list
[email protected]
http://lists.nmglug.org/listinfo.cgi/nmglug-nmglug.org
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.