<div>Okay, as a reminder here is the error I get:</div><div><br></div><div> bmike1@PresarioLapTop1:~/Desktop$ ./Backup\ bmike1</div><div> building file list ... done</div><div> rsync: mkdir "/mnt/backup/bmike1" failed: Permission denied (13)</div>
<div> rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]</div><div> rsync: connection unexpectedly closed (9 bytes received so far) [sender]</div><div> rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9] </div>
<div> bmike1@PresarioLapTop1:~/Desktop$ ls -la /mnt/backup</div><div> ls: reading directory /mnt/backup: Input/output error</div><div> total 0</div><div><br></div><div>I then figured I would look to see if the drive was accessible:</div>
<div><br></div><div><div> bmike1@PresarioLapTop1:~/Desktop$ cp Backup\ bmike1 /mnt/backup</div><div> cp: cannot create regular file `/mnt/backup/Backup bmike1': Permission denied</div><div> bmike1@PresarioLapTop1:~/Desktop$ </div>
</div><div><br></div><div>I think this means I need to change the ownership of /mnt/backup . So first I checked to see the present ownership:</div><div><br></div><div><div> bmike1@PresarioLapTop1:~/Desktop$ ls -l /mnt/backup/</div>
<div> ls: reading directory /mnt/backup/: Input/output error</div><div> total 0</div></div><div><br></div><div>Why would I get an input/output error?</div><div>I then figured I would try ls -l from a level up:</div><div>
<br></div><div><div> bmike1@PresarioLapTop1:~/Desktop$ ls -l /mnt</div><div> total 8</div><div> drwxr-xr-x 4 root root 4096 Jul 5 19:06 backup</div><div> drwxr-xr-x 4 root root 4096 Jul 5 19:06 sdc</div></div><div>
<br>
</div><div>I could swear I chown it when you told me to. Let's try again:</div><div><br></div><div><div> bmike1@PresarioLapTop1:~/Desktop$ sudo chown bmike1 /mnt/backup</div><div> chown: changing ownership of `/mnt/backup': Input/output error</div>
</div><div><br></div><div>So then I remember reading man chown and remember the recursive option:</div><div><br></div><div> bmike1@PresarioLapTop1:~/Desktop$ sudo chown -R bmike1 /mnt/backup</div><div> bmike1@PresarioLapTop1:~/Desktop$</div>
<div><br></div><div>That worked! Why do I need the -R option?</div><div>...</div><div>I was so excited thinking that now it would work!</div><div><br></div><div><div> bmike1@PresarioLapTop1:~/Desktop$ ./Backup\ bmike1</div>
<div> building file list ... done</div><div> rsync: mkdir "/mnt/backup/bmike1" failed: Read-only file system (30)</div><div> rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]</div><div>
rsync: connection unexpectedly closed (9 bytes received so far) [sender]</div>
<div> rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]</div></div><div><br></div><div>bummer!</div><div>I just looked at the directory of /mnt/backup and there is nothing in it. Should I create /mnt/backup/bmike1 seeing as it rsyncs to /mnt/backup/bmike1 and for some reason the script won't make the file?</div>
<div>I just looked at the directory again and:</div><div><br></div><div><div> bmike1@PresarioLapTop1:~/Desktop$ ls -l /mnt</div><div> total 8</div><div> drwxr-xr-x 4 bmike1 root 4096 Jul 5 19:06 backup</div><div> drwxr-xr-x 4 bmike1 root 4096 Jul 5 19:06 sdc</div>
<div> bmike1@PresarioLapTop1:~/Desktop$ </div></div><div><br></div><div>Is this looking as it should? What does the 4th place mean (the place that says 'root').</div><div>:-)~MIKE~(-:</div><div><br></div><div><br>
</div><div><br></div>
<br><br><div class="gmail_quote">On Thu, Jul 11, 2013 at 8:24 AM, Matt Graham <span dir="ltr"><<a href="mailto:danceswithcrows@usa.net" target="_blank">danceswithcrows@usa.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
From: James Dugger<br>
<div>> While I don't have hard links (mainly soft links) in my working<br>
> directories, I am using hard links in my incremental backup strategy.<br>
> I implement the following simple script to create a rotating backup<br>
> using rsync's --link-dest=[filename].<br>
</div>[snip script]<br>
<div>> subdirectory with today's date under a directory called 'archive'<br>
> and then proceeds to read changed files from the previous day's<br>
> archive directory, copy and link any changed files from this<br>
> directory to today's archive. It then proceeds to delete the<br>
> directory that is 121 days old.<br>
<br>
</div>This should work and be useful to some extent. Keeping some sort of record of<br>
"how did everything look on YYYY-MM-DD?" could be useful for various things.<br>
<br>
However, using hard links like this means that your backup lives on the same<br>
filesystem and same disk as the original data. If your filesystem ever gets<br>
corrupt or the disk ever dies, you could easily lose both the original and the<br>
backup. I've had filesystems and disks fail, so I would never use this as my<br>
only backup strategy.<br>
<div><div><br>
--<br>
Matt G / Dances With Crows<br>
The Crow202 Blog: <a href="http://crow202.org/wordpress/" target="_blank">http://crow202.org/wordpress/</a><br>
There is no Darkness in Eternity/But only Light too dim for us to see<br>
<br>
---------------------------------------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
</div></div></blockquote></div><br>