Okay, as a reminder here is the error I get:
bmike1@PresarioLapTop1:~/Desktop$ ./Backup\ bmike1
building file list ... done
rsync: mkdir "/mnt/backup/bmike1" failed: Permission denied (13)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
bmike1@PresarioLapTop1:~/Desktop$ ls -la /mnt/backup
ls: reading directory /mnt/backup: Input/output error
total 0
I then figured I would look to see if the drive was accessible:
bmike1@PresarioLapTop1:~/Desktop$ cp Backup\ bmike1 /mnt/backup
cp: cannot create regular file `/mnt/backup/Backup bmike1': Permission denied
bmike1@PresarioLapTop1:~/Desktop$
I think this means I need to change the ownership of /mnt/backup . So first I checked to see the present ownership:
bmike1@PresarioLapTop1:~/Desktop$ ls -l /mnt/backup/
ls: reading directory /mnt/backup/: Input/output error
total 0
Why would I get an input/output error?
I then figured I would try ls -l from a level up:
bmike1@PresarioLapTop1:~/Desktop$ ls -l /mnt
total 8
drwxr-xr-x 4 root root 4096 Jul 5 19:06 backup
drwxr-xr-x 4 root root 4096 Jul 5 19:06 sdc
I could swear I chown it when you told me to. Let's try again:
bmike1@PresarioLapTop1:~/Desktop$ sudo chown bmike1 /mnt/backup
chown: changing ownership of `/mnt/backup': Input/output error
So then I remember reading man chown and remember the recursive option:
bmike1@PresarioLapTop1:~/Desktop$ sudo chown -R bmike1 /mnt/backup
bmike1@PresarioLapTop1:~/Desktop$
That worked! Why do I need the -R option?
...
I was so excited thinking that now it would work!
bmike1@PresarioLapTop1:~/Desktop$ ./Backup\ bmike1
building file list ... done
rsync: mkdir "/mnt/backup/bmike1" failed: Read-only file system (30)
rsync error: error in file IO (code 11) at main.c(605) [Receiver=3.0.9]
rsync: connection unexpectedly closed (9 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(605) [sender=3.0.9]
bummer!
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?
I just looked at the directory again and:
bmike1@PresarioLapTop1:~/Desktop$ ls -l /mnt
total 8
drwxr-xr-x 4 bmike1 root 4096 Jul 5 19:06 backup
drwxr-xr-x 4 bmike1 root 4096 Jul 5 19:06 sdc
bmike1@PresarioLapTop1:~/Desktop$
Is this looking as it should? What does the 4th place mean (the place that says 'root').
:-)~MIKE~(-:
On Thu, Jul 11, 2013 at 8:24 AM, Matt Graham
<danceswithcrows@usa.net> wrote:
From: James Dugger
> While I don't have hard links (mainly soft links) in my working
> directories, I am using hard links in my incremental backup strategy.
> I implement the following simple script to create a rotating backup
> using rsync's --link-dest=[filename].
[snip script]
> subdirectory with today's date under a directory called 'archive'
> and then proceeds to read changed files from the previous day's
> archive directory, copy and link any changed files from this
> directory to today's archive. It then proceeds to delete the
> directory that is 121 days old.
This should work and be useful to some extent. Keeping some sort of record of
"how did everything look on YYYY-MM-DD?" could be useful for various things.
However, using hard links like this means that your backup lives on the same
filesystem and same disk as the original data. If your filesystem ever gets
corrupt or the disk ever dies, you could easily lose both the original and the
backup. I've had filesystems and disks fail, so I would never use this as my
only backup strategy.