re: How to rsync to a chromebook with linux?

rsync options [from] [to] If you are running it on the chromebook then the from will be your desktop rsynce -avH --progress 192.168.0.??:/home/joe/bin /home/upquick/bin or from the chromebook cd /home/upquick/bin scp -r joe@192.168.0.??:bin . Since its the first time then there won't be much

How to rsync to a chromebook with linux?

l I can do now with Linux on this Chromebook running *simultaneously* with the chrome os. However, I have not yet been able to find the magic syntax to rsync files from my current Linux system to this new Chromebook. When I tap on the Linux icon on the shelf the Chromebook opens to a bl

Re: rsync permission denied

is seagate mounted ? is it write protected ? On Wed, Jan 30, 2019, 7:52 AM > rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/Seagate > > rsync: mkdir "/media/bmike1/Seagate" failed: Permission denied (13) > Mike, this suggests that whatever user is logi

Re: rsync permission denied

rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/Seagate rsync: mkdir "/media/bmike1/Seagate" failed: Permission denied (13) Mike, this suggests that whatever user is login in to the remote box doesn't have the rights to 'mkdir /media/bmike1/Seagate' Login t

Re: rsync permission denied

is in the local box? What directories are you rsync(ing). Whatever the answer is, I'll bet you dollars to donuts that you have a 'user error'... ;-) ET Michael writes: I was trying to backup my system for the first time and rsync is throwing a permission denied error up. Did something change

Re: rsync permission denied

rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/Seagate rsync: mkdir "/media/bmike1/Seagate" failed: Permission denied (13) rsync error: error in file IO (code 11) at main.c(675) [Receiver=3.1.2] On Wed, Jan 30, 2019 at 8:25 AM Snyder, Alexander J < a...@mister

Re: rsync permission denied

What is the exact text of the error? What are the existing permissions of what you're trying to backup? Thanks, Alexander. Sent from my Samsung Galaxy S8+ On Wed, Jan 30, 2019, 05:28 Michael I was trying to backup my system for the first time and rsync is throwing > a permission denied er

rsync permission denied

I was trying to backup my system for the first time and rsync is throwing a permission denied error up. Did something change with rsync or is this a user error? How do I fix it? -- :-)~MIKE~(-: --- PLUG-discuss mailing list - PLUG-discuss

RE: sleep and rsync

and rsync there are two different things. screen saver and power management. power management will put the computer in suspend mode which will copy memory to a buffer then put the system into a very low power mode waiting to be woke up after wich it will copy the buffer back to memory and resume where

Re: sleep and rsync

aking up from suspend mode. > > hope this helps > > > On Tue, Jan 1, 2019, 5:34 PM Michael >> , doesn't work. Oh well, all use the media player because when that is >> playing it does not go off >> >> On Tue, Jan 1, 2019, 18:33 David Lopez > >>>

Re: sleep and rsync

that is > playing it does not go off > > On Tue, Jan 1, 2019, 18:33 David Lopez >> keep computer on by simply using the linux (ubuntu) timer on until rsync >> is finished. >> >>settings-->power-->power saving=="never" >> >> this is a time se

Re: sleep and rsync

, doesn't work. Oh well, all use the media player because when that is playing it does not go off On Tue, Jan 1, 2019, 18:33 David Lopez keep computer on by simply using the linux (ubuntu) timer on until rsync > is finished. > >settings-->power-->power saving=="never&quo

Re: sleep and rsync

keep computer on by simply using the linux (ubuntu) timer on until rsync is finished. settings-->power-->power saving=="never" this is a time set at 3 minutes - change it to an hour or more until rsync is done. david lopez On Tue, Jan 1, 2019 at 4:25 PM David Lopez wrote:

Re: sleep and rsync

keep computer on by simply using the linux (ubuntu) on until rsync is finished. settings-->power-->power saving==never this is a time set at 3 minutes - change it to an your or more until rsync is done. david lopez On Tue, Jan 1, 2019 at 1:33 PM Michael wrote: > how does one m

Re: sleep and rsync

how does one make it so the computer will not go to sleep? On Tue, Jan 1, 2019 at 1:26 PM der.hans wrote: > Am 01. Jan, 2019 schwätzte Michael so: > > moin moin, > > your computer effectively turns off when it goes to sleep. > > tcp connections such as rsync might

sleep and rsync

I run rsync and sometimes the computer goes to sleep while I'm running it (or at least the screen goes black and I need to reenter the pass word). What happens to rsync when it goes to sleep? Like does it continue to run or is it suspended? Do I need to ^C the thing and restart it or does it pick

Re: rsync problem

thanks Matt. I ignored the squirrel this time! disk not plugged in. there is a seagate expansion drive directory in /media. after further investigation it seems rsync backed the seagate expansion drive to /media and not to /media/Seagate\ Expansion\ Drive. Would you say rmdir and things should

ADD? NO! not me!!! (was RE: rsync problem)

Well, my Dr says I have ADD, but I think he's wrong because - HEY, look at that rabbit! -Original Message- Subject: Re: rsync problem ... (Sometimes, I think people don't read the stuff I write... is it horrible mail clients, spam filtering, short attention spans, or--SQUIRREL

Re: rsync problem

: what about running the rsync command [as] root? Bob, the problem as shown in the parts of the message above marked with >>> is that the automounter put the disk /dev/sdc1 on "/media/bmike1/Seagate Expansion Drive1" instead of "/media/bmike1/Seagate Expansion Drive".

Re: rsync problem

what about running the rsync command from root? if you know the root password, you can sudo to root and run the rsync command and it should be able to accomplish any reads and writes On Thu, Sep 27, 2018, 3:01 PM Matt Graham wrote: > >>>> /dev/sdc1 on /media/bmike1/Seagate E

Re: rsync problem

/dev/sdc1 on /media/bmike1/Seagate Expansion Drive1 type fuseblk bmike1@MikesBeast ~ $ ls -l /media/bmike1 drwxr-xr-x 3 root   root   4096 Sep 25 19:16 Seagate Expansion Drive drwxrwxrwx 1 bmike1 bmike1 4096 Sep 25 19:57 Seagate Expansion Drive1 Have a good look at the ls -l output and the

Re: rsync problem

mmend using a new drive to store backups on. >>> >>> >>> >>> On Wed, Sep 26, 2018, 3:04 PM Matt Graham wrote: >>> >>>> On 2018-09-26 14:41, Michael wrote: >>>> >> On Wed, Sep 26, 2018 at 5:27 PM Matt Graham >>

Re: rsync problem

gt; >> On Wed, Sep 26, 2018, 3:04 PM Matt Graham wrote: >> >>> On 2018-09-26 14:41, Michael wrote: >>> >> On Wed, Sep 26, 2018 at 5:27 PM Matt Graham >>> >> wrote: >>> >>>> On Tue, Sep 25, 2018 at 4:20 PM Michael wrote: >&

Re: rsync problem

new drive to store backups on. > > > > On Wed, Sep 26, 2018, 3:04 PM Matt Graham wrote: > >> On 2018-09-26 14:41, Michael wrote: >> >> On Wed, Sep 26, 2018 at 5:27 PM Matt Graham >> >> wrote: >> >>>> On Tue, Sep 25, 2018 at 4:20 PM Mi

Re: rsync problem

wrote: > >>>> On Tue, Sep 25, 2018 at 4:20 PM Michael wrote: > >>> bmike1@MikesBeast ~ $ rsync -aWuq --delete-before > >>> /home/bmike1/Documents /media/bmike1/"Seagate Expansion Drive" > >>> rsync: mkdir "/media/bmike1/Seagate Expa

Re: rsync problem

On 2018-09-26 14:41, Michael wrote: On Wed, Sep 26, 2018 at 5:27 PM Matt Graham wrote: On Tue, Sep 25, 2018 at 4:20 PM Michael wrote: bmike1@MikesBeast ~ $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/"Seagate Expansion Drive" rsync: mkdir "/media/bmike1/Se

Re: rsync problem

TTL=1 ID=0 PROTO=2 > [109961.270941] [UFW BLOCK] IN=enp2s0 OUT= > MAC=01:00:5e:00:00:01:b0:93:5b:2d:f4:28:08:00 SRC=192.168.2.1 DST=224.0.0.1 > LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=0 PROTO=2 > bmike1@MikesBeast ~ $ > > > On Wed, Sep 26, 2018 at 5:27 PM Matt Graham wrote: > >> &

Re: rsync problem

at 5:27 PM Matt Graham wrote: > > On Tue, Sep 25, 2018 at 4:20 PM Michael wrote: > >> bmike1@MikesBeast ~ $ rsync -aWuq --delete-before > >> /home/bmike1/Documents > >> /media/bmike1/"Seagate Expansion Drive" > >> rsync: mkdir "/media/bmike

Re: rsync problem

On Tue, Sep 25, 2018 at 4:20 PM Michael wrote: bmike1@MikesBeast ~ $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/"Seagate Expansion Drive" rsync: mkdir "/media/bmike1/Seagate Expansion Drive" failed: Permission denied (13) I never had this probl

Re: rsync problem

t; On Sep 25, 2018, at 5:20 PM, Michael wrote: >> >> I never had this problem before. What does it mean? >> >> bmike1@MikesBeast ~ $ rsync -aWuq --delete-before /home/bmike1/Documents >> /media/bmike1/"Seagate Expansion Drive" >> rsync: mkdir

Re: rsync problem

Probably means you dont have the permissions to do a delete on the source file Kevin ⁣Sent from BlueMail ​ On Sep 25, 2018, 5:20 PM, at 5:20 PM, Michael wrote: >I never had this problem before. What does it mean? > >bmike1@MikesBeast ~ $ rsync -aWuq --delete-before >/home/bmik

Re: rsync problem

es it mean? >> >> bmike1@MikesBeast ~ $ rsync -aWuq --delete-before /home/bmike1/Documents >> /media/bmike1/"Seagate Expansion Drive" >> rsync: mkdir "/media/bmike1/Seagate Expansion Drive" failed: Permission >> denied (13) >> >> >> -- &g

Re: rsync problem

could it mean my drive is dieing? On Tue, Sep 25, 2018 at 7:19 PM, Michael wrote: > I never had this problem before. What does it mean? > > bmike1@MikesBeast ~ $ rsync -aWuq --delete-before /home/bmike1/Documents > /media/bmike1/"Seagate Expansion Drive" > rsync: mkd

Re: rsync problem

Maybe the owner of the drive is root On Tue, Sep 25, 2018 at 4:20 PM Michael wrote: > I never had this problem before. What does it mean? > > bmike1@MikesBeast ~ $ rsync -aWuq --delete-before /home/bmike1/Documents > /media/bmike1/"Seagate Expansion Drive" > rsync: mkd

rsync problem

I never had this problem before. What does it mean? bmike1@MikesBeast ~ $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/"Seagate Expansion Drive" rsync: mkdir "/media/bmike1/Seagate Expansion Drive" failed: Permission denied

Re: rsync

ome >>> other stuff it won’t run the test, IIRC. >>> >>> >>> >>> *From:* PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] *On >>> Behalf Of *Michael >>> *Sent:* Friday, September 22, 2017 5:15 AM >>> *To:* Main PLUG di

Re: rsync

gt; > From: PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] On Behalf > Of Michael > Sent: Friday, September 22, 2017 5:15 AM > To: Main PLUG discussion list > Subject: Re: rsync > > > > $ sudo fsck /dev/sdc1 > > fsck from util-linux 2.27.1

Re: rsync

other stuff it won’t run the test, IIRC. >> >> >> >> *From:* PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] *On >> Behalf Of *Michael >> *Sent:* Friday, September 22, 2017 5:15 AM >> *To:* Main PLUG discussion list >> *Subject:* Re: rsyn

Re: rsync

e test, IIRC. > > > > *From:* PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] *On > Behalf Of *Michael > *Sent:* Friday, September 22, 2017 5:15 AM > *To:* Main PLUG discussion list > *Subject:* Re: rsync > > > > $ sudo fsck /dev/sdc1 > > fsck

RE: rsync

Try fsck –f (for force). If the filesystem is marked clean and some other stuff it won’t run the test, IIRC. From: PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] On Behalf Of Michael Sent: Friday, September 22, 2017 5:15 AM To: Main PLUG discussion list Subject: Re: rsync

Re: rsync

$ sudo fsck /dev/sdc1 fsck from util-linux 2.27.1 $ isn't it supposed to give a code of some sort? Here is a mall snippet of the errors it gives when trying to rsync to the drive: rsync: readlink_stat("/media/bmike1/Seagate Expansion Drive/Documents/Programs/file recovery/recup_dir.465/f464

Re: rsync

>>>>> >>>>> >>>>> On Thu, Sep 7, 2017 at 4:26 PM, Michael <bmi...@gmail.com> wrote: >>>>> >>>>>> interesting. I recovered some files using tesstdisk. I tried to >>>>>> delete th

Re: rsync

m> wrote: >>>> >>>>> interesting. I recovered some files using tesstdisk. I tried to >>>>> delete them and some of the wouldn't die (the ones I'm having problems >>>>> with). My google for the swolution suggested I chown but that ga

Re: rsync

recup_dir.465/ >>> chown: changing ownership of 'recup_dir.465/f46038464.elf': Input/output >>> error >>> >>> >>> >>> >>> On Thu, Sep 7, 2017 at 5:49 PM, Michael <bmi...@gmail.com> wrote: >>> >>>> I forgot to ment

Re: rsync

gt;> >> >> >> >> On Thu, Sep 7, 2017 at 5:49 PM, Michael <bmi...@gmail.com> wrote: >> >>> I forgot to mention I deleted those files on the source disk. This i the >>> command I'm issuing: >>> >>> rsync -aWuq --delete-before /h

Re: rsync

Thu, Sep 7, 2017 at 5:49 PM, Michael <bmi...@gmail.com> wrote: > >> I forgot to mention I deleted those files on the source disk. This i the >> command I'm issuing: >> >> rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/"Seagate >> Expansion Drive&qu

Re: rsync

of 'recup_dir.465/f46038464.elf': Input/output error On Thu, Sep 7, 2017 at 5:49 PM, Michael <bmi...@gmail.com> wrote: > I forgot to mention I deleted those files on the source disk. This i the > command I'm issuing: > > rsync -aWuq --delete-before /home/bmike1/Documents /med

Re: rsync

I forgot to mention I deleted those files on the source disk. This i the command I'm issuing: rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/"Seagate Expansion Drive" On Thu, Sep 7, 2017 at 5:36 PM, James Dugger <james.dug...@gmail.com> wrote: > You poten

Re: rsync

You potentially have corrupt files or problems with your disk. Use the fsck command to check files/file system and smartctl command to check the disk On Sep 7, 2017 4:52 AM, "Michael" <bmi...@gmail.com> wrote: > I get the following errors. How do I stop it? > $ rsync -aWuq

rsync

I get the following errors. How do I stop it? $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/"Seagate Expansion Drive" rsync: readlink_stat("/media/bmike1/Seagate Expansion Drive/Documents/Programs/file recovery/recup_dir.465/f46038464.elf") failed: Input/ou

rsync error

Last night I was backing up my system. It seemed to be taking a long time so I just went to bed. I got up in the morning and the drive wasn't flashing but the terminal wasn't waiting for a new command. so I pressed cntrl-c. Suddenly a bunch of errors printed up with the following error: rsync

Re: Rsync ran like 30-40 minutes

g e2fsck with an alternate >>>>>> superblock: >>>>>> e2fsck -b 8193 >>>>>> or >>>>>> e2fsck -b 32768 >>>>>> $ sudo fsck /dev/sdd1 >>>>>> fsck from util-linux 2.20.1 >

Re: Rsync ran like 30-40 minutes

-boun...@lists.phxlinux.org <mailto:plug-discuss-boun...@lists.phxlinux.org>] *On Behalf Of *Michael *Sent:* Friday, April 28, 2017 4:41 PM *To:* PLUG *Subject:* Rsync ran like 30-

Re: Rsync ran like 30-40 minutes

Can an admin of the mailing list please delete these posts with the personal private information. Anyone replying to this topic, please remove the quoted text with the private info. Michael, please be careful when you post things like this. As for the problem, I really think you would be better

Re: Rsync ran like 30-40 minutes

1 >>>> fsck.fat 3.0.26 (2014-03-07) >>>> 0x41: Dirty bit is set. Fs was not properly unmounted and some data may >>>> be corrupt. >>>> 1) Remove dirty bit >>>> 2) No action >>>> ? ^C >>>> >>>> bmike1@Mik

Re: Rsync ran like 30-40 minutes

;>> e2fsck 1.42.9 (4-Feb-2014) >>> fsck.ext2: No such file or directory while trying to open /dev/sdd1 >>> Possibly non-existent device? >>> >>> >>> On Fri, Apr 28, 2017 at 7:43 PM, Carruth, Rusty < >>> rusty.carr...@smartm.com> wrote: &

Re: Rsync ran like 30-40 minutes

ectory while trying to open /dev/sdd1 >> Possibly non-existent device? >> >> >> On Fri, Apr 28, 2017 at 7:43 PM, Carruth, Rusty <rusty.carr...@smartm.com >> > wrote: >> >>> What does fsck say? >>> >>> >>> >>> *From:*

Re: Rsync ran like 30-40 minutes

ssibly non-existent device? > > > On Fri, Apr 28, 2017 at 7:43 PM, Carruth, Rusty <rusty.carr...@smartm.com> > wrote: > >> What does fsck say? >> >> >> >> *From:* PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] *On >> Behalf Of *Mic

Re: Rsync ran like 30-40 minutes

, 2017 4:41 PM > *To:* PLUG > *Subject:* Rsync ran like 30-40 minutes > > > > this is what happened in that time: > > > > $ rsync -aWuq --delete-before --progress /home/bmike1/Documents > /media/bmike1/GORILLA64 > > ^C > > rsync error: received SIGINT,

RE: Rsync ran like 30-40 minutes

What does fsck say? From: PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] On Behalf Of Michael Sent: Friday, April 28, 2017 4:41 PM To: PLUG Subject: Rsync ran like 30-40 minutes this is what happened in that time: $ rsync -aWuq --delete-before --progress /home/bmike1/Documents

Rsync ran like 30-40 minutes

this is what happened in that time: $ rsync -aWuq --delete-before --progress /home/bmike1/Documents /media/bmike1/GORILLA64 ^C rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at rsync.c(632) [sender=3.1.0] rsync error: received SIGINT, SIGTERM, or SIGHUP (code 20) at io.c(521

Re: rsync

You have a permissions problem on your destination path. rsync errors will be reported regardless of where you redirect them too. PIPESTATUS will contain the exit code from rsync. If it is zero (0) GOOD will print, otherwise it will not. The question is what code is rsync exiting with. Regardless

Re: rsync

ot;Michael" <bmi...@gmail.com> wrote: >> >>> I was wondering if there was a way to see the progress of an rsync >>> command so I searched the man page and found '--progress'. So I included >>> that into my command and the output doesn't seem to look

Re: rsync

Try a - v or - - progress On Jan 15, 2017 8:01 AM, "Michael" <bmi...@gmail.com> wrote: > I was wondering if there was a way to see the progress of an rsync command > so I searched the man page and found '--progress'. So I included that into > my command and the output

rsync

I was wondering if there was a way to see the progress of an rsync command so I searched the man page and found '--progress'. So I included that into my command and the output doesn't seem to look like it is supposed to. Would someone look at my command and tell me if I messed up in some way

Re: More rsync

thanks Brian. On Mon, Jan 2, 2017 at 10:19 PM, Brian Cluff <br...@snaptek.com> wrote: > You should just have to run your rsync command as usual as long as the new > drive mounts as GORILLA64. Even if you didn't get it copied over there > correctly the rsync command will c

Re: More rsync

You should just have to run your rsync command as usual as long as the new drive mounts as GORILLA64. Even if you didn't get it copied over there correctly the rsync command will correct anything that isn't quite right, which it already should be. Brian Cluff On 01/02/2017 04:29 PM, Michael

More rsync

So I think that drive died on me.So I went out and bought a new one. I wasn't thinking and I just copied one of the folders I want to use rsync on to the new drive. My question is (which I don't think I'll need to do) will the following command just copy Documents to the gorilla drive or will I

Re: Problem with rsync

FAT16 or 32 what is the difference google it the maximum size is 32GB. So that is why I got the errors. Well apparently the ntfs format worked it was the ntfsck that balked. Any ideas on how to get it to work? --- PLUG-discuss mailing

Re: Problem with rsync

Bummer... that didn't work: $ sudo ntfsck /dev/sdc Boot sector: Bad jump. Boot sector: Bad NTFS magic. sectors_per_cluster (216) is not a power of 2. Attribute (0xbd58c437) is larger than FILE record at offset 21297264072 (0x4f56a75c8). Loading $MFT runlist failed. Trying $MFTMirr. Failed to read

Re: Problem with rsync

thanks. I no longer have access to the machine in question. I'll take care of it in the morning. Is installing ntfs-3g merely a simple apt command? On Sun, Jan 1, 2017 at 6:49 PM, Matt Graham wrote: > On 2017-01-01 16:34, Michael wrote: > >> $ sudo fsck.ntfs /dev/sdc

Re: Problem with rsync

On 2017-01-01 16:34, Michael wrote: $ sudo fsck.ntfs /dev/sdc sudo: fsck.ntfs: command not found $ sudo fsck.vfat /dev/sdc fsck.fat 3.0.26 (2014-03-07) Currently, only 1 or 2 FATs are supported, not 251. Provided that you have ntfs-3g installed, the fsck for ntfs is called ntfsck instead of

Re: Problem with rsync

, not 251. On Sun, Jan 1, 2017 at 5:55 PM, Michael <bmi...@gmail.com> wrote: > Thanks I decided to reformat it and rsync it all again. And it isn't > giving me any errors (yet). I am formatting it ntfs. Can I do fsck.ntfs or > would I just do ...vfat? What about for a remind

Re: Problem with rsync

Thanks I decided to reformat it and rsync it all again. And it isn't giving me any errors (yet). I am formatting it ntfs. Can I do fsck.ntfs or would I just do ...vfat? What about for a reminder? Could I put, "rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/SDULTRA64 *un

Re: Problem with rsync

Sun, Jan 1, 2017 at 5:07 PM, Matt Graham <mhgra...@crow202.org> wrote: >>>>>> On Jan 1, 2017, at 2:54 PM, Michael <bmi...@gmail.com> wrote: >>>>>> $ rsync -aWuq --delete-before /home/bmike1/Documents >>>>>> /media/bmike1/SDULTRA64 >

Re: Problem with rsync

On 2017-01-01 15:29, Michael wrote: sudo fsck -p /media/bmike1/SDULTRA64 This is not correct. You run fsck on the device, not the mount point. Find out what the device node is (probably /dev/sdX1 where X is a lowercase letter which is not a. Try "ls -l /dev/disk/by-label/" to get a

Re: Problem with rsync

I can still access them. Then when I back out of the directory >>> the lock is gone and then back in and the pictures are no longer locked. >>> >>> On Sun, Jan 1, 2017 at 5:07 PM, Matt Graham <mhgra...@crow202.org> >>> wrote: >>> >>>> O

Re: Problem with rsync

res are no longer locked. >> >> On Sun, Jan 1, 2017 at 5:07 PM, Matt Graham <mhgra...@crow202.org> wrote: >> >>> On Jan 1, 2017, at 2:54 PM, Michael <bmi...@gmail.com> wrote: >>>> >>>>> $ rsync -aWuq --delete-before /hom

Re: Problem with rsync

when I back out of the directory > the lock is gone and then back in and the pictures are no longer locked. > > On Sun, Jan 1, 2017 at 5:07 PM, Matt Graham <mhgra...@crow202.org> wrote: > >> On Jan 1, 2017, at 2:54 PM, Michael <bmi...@gmail.com> wrote: >>&

Re: Problem with rsync

wrote: > On Jan 1, 2017, at 2:54 PM, Michael <bmi...@gmail.com> wrote: >> >>> $ rsync -aWuq --delete-before /home/bmike1/Documents >>> /media/bmike1/SDULTRA64 >>> rsync: mkstemp "/media/bmike1/SDULTRA64/Documents/ComputerInstructions/. >>> R

Re: Problem with rsync

On Jan 1, 2017, at 2:54 PM, Michael <bmi...@gmail.com> wrote: $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/SDULTRA64 rsync: mkstemp "/media/bmike1/SDULTRA64/Documents/ComputerInstructions/. Reinstall-Desktop.txt.m7GSdf" failed: Read-only file system (30)

Re: Problem with rsync

Are they (rw)? > > Jason > > Sent from my iPhone > > On Jan 1, 2017, at 2:54 PM, Michael <bmi...@gmail.com> wrote: > > I run the command: > $ rsync -aWuq --delete-before /home/bmike1/Documents > /media/bmike1/SDULTRA64 > and Most everything on my system backed

Re: Problem with rsync

What are the outputs of the command "mount"? Are they (rw)? Jason Sent from my iPhone > On Jan 1, 2017, at 2:54 PM, Michael <bmi...@gmail.com> wrote: > > I run the command: > $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/SDULTRA64 > a

Problem with rsync

I run the command: $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/SDULTRA64 and Most everything on my system backed up but this is it's complaint: rsync: mkstemp "/media/bmike1/SDULTRA64/Documents/ComputerInstructions/.Reinstall-Desktop.txt.m7GSdf" failed: Read

Re: rsync`

It was mounted. I labled it as Kingston64 but mlabel turned it into KINGSTON64. My rsync command had it as Kingston until I realized mlabel had capitalized everything. On Tue, Oct 11, 2016 at 12:51 AM, Brien Dieterle <bri...@gmail.com> wrote: > Ah, so it wasn't mounted. . . where yo

Re: rsync`

t;> >> On Mon, Oct 10, 2016 at 10:54 PM, Michael <bmi...@gmail.com> wrote: >> >>> It's mounted. Otherwise the mlabel command would have failed. >>> >>> $ ls /media/bmike1 >>> KINGSTON64 >>> >>> >>> On Mon, Oct 10, 2016 at

Re: rsync`

com> wrote: > >> I don't think your sdcard is even mounted. Try this: >> http://www.pkill-9.com/mount-usb-micro-sd-card-linux-automount/ >> >> Also, until you are confident it is configured correctly, you should >> really use -n (or --dry-run) for rsync so you

Re: rsync`

ux-automount/ > > Also, until you are confident it is configured correctly, you should > really use -n (or --dry-run) for rsync so you don't accidentally... oh, > delete everything :-) > > On Mon, Oct 10, 2016 at 6:02 PM, Michael <bmi...@gmail.com> wrote: > >>

Re: rsync`

I don't think your sdcard is even mounted. Try this: http://www.pkill-9.com/mount-usb-micro-sd-card-linux-automount/ Also, until you are confident it is configured correctly, you should really use -n (or --dry-run) for rsync so you don't accidentally... oh, delete everything :-) On Mon, Oct 10

Re: rsync`

I found the solution and I labled my device but: $ sudo mlabel p:kingston64 $ rsync -aWuq --delete-before /home/bmike1/Documents /media/bmike1/Kingston64 rsync: mkdir "/media/bmike1/Kingston64" failed: Permission denied (13) rsync error: error in file IO (code 11) at main.c(674) [Rece

Re: rsync`

okay I googled and I searched and found the solution to my problem: http://www.pkill-9.com/label-ms-dos-flash-drive-micro-sd-card-mtools-linux/ On Mon, Oct 10, 2016 at 8:17 AM, Michael <bmi...@gmail.com> wrote: > I just got a 64gb card to rsync my hard drive on to How do I

rsync`

I just got a 64gb card to rsync my hard drive on to How do I see what the card is listed as? (/media/bmike1/) This is the command I use: rsync -aWuq --delete-before /home/bmike1/Documents\ /media/bmike1/ I have two questions. I want to retain the dos format so to name it would I

Re: rsync problem

Something to also pay attention to, some filesystems don't support all the options that rsync tries to set, like users and permissions. In that case, it's necessary to do rsync with a flag besides "-a" and pull the unsupported bits out of the "-rlptgoD". This is suboptimal,

Re: rsync problem

sesso.com> wrote: >>>>> >>>>>> Try using just --delete instead of --delete-before >>>>>> >>>>>> Sent from my iPhone >>>>>> >>>>>> On May 9, 2016, at 7:09 PM, Michael <bmi...@gmail.com> w

Re: rsync problem

hone >>>>> >>>>> On May 9, 2016, at 7:09 PM, Michael <bmi...@gmail.com> wrote: >>>>> >>>>> well, I just ran it with the trailing slash and it gave me the same >>>>> output as before except it happened immediately. The U

Re: rsync problem

gt;> On May 9, 2016, at 7:09 PM, Michael <bmi...@gmail.com> wrote: >>>> >>>> well, I just ran it with the trailing slash and it gave me the same >>>> output as before except it happened immediately. The USB drive wasn't >>>> accessd for five

Re: rsync problem

May 9, 2016, at 7:09 PM, Michael <bmi...@gmail.com> wrote: >>> >>> well, I just ran it with the trailing slash and it gave me the same >>> output as before except it happened immediately. The USB drive wasn't >>> accessd for five minutes. >

Re: rsync problem

t ran it with the trailing slash and it gave me the same >> output as before except it happened immediately. The USB drive wasn't >> accessd for five minutes. >> >> On Mon, May 9, 2016 at 10:04 PM, Bob Elzer <bob.el...@gmail.com> wrote: >> >>> My syncs look li

Re: rsync problem

nd it gave me the same >> output as before except it happened immediately. The USB drive wasn't >> accessd for five minutes. >> >> On Mon, May 9, 2016 at 10:04 PM, Bob Elzer <bob.el...@gmail.com> wrote: >> >>> My syncs look like this >>> >>&

Re: rsync problem

$ rsync -aWuq --delete /home/bmike1/Documents /media/bmike1/R edSanDisk rsync: mkstemp "/media/bmike1/RedSanDisk/Documents/Programs/PhotoSphereBundle/App/Lib/site-packages/pyopengl-3.1.0a1-py2.7.egg/OpenGL/raw/GL/APPLE/.float_pixels.pyc.egRAlx" failed: Read-only file system (30) etc..

  1   2   >