I am trying to copy a backup on a usb hard drive. The usb partition is
ext4 as is the partition I am trying to back up
=20
mount
/dev/nvme0n1p8 on / type ext4 (rw,noatime)
/dev/sda2 on /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca
type ext4 (rw,nosuid,nodev,relatime,errors=3Dremount-ro,uhelper=3Dudisks2)
=20
/dev/sda2 is a usb drive. / is an internal ssh drive.
=20
I run
rsync -avxAHXp --link-dest ./crawler-root-aug12-2022 / ./crawler-root-nov6-2022
=20
while on the backup directory on the usb drive (mounted in
/run/media/unruh)
But for example
crawler:0[root]>ls -l crawler-root-*-2022/dead.letter =20
-rw------- 2 root root 7210272 Dec 12 2021 crawler-root-aug12-2022/dead.letter -rw------- 1 root root 7210272
Dec 12 2021 crawler-root-nov6-2022/dead.letter
=20
shows that dead.letter was copied over, not hard linked.
=20
diff on the two says there is no difference between the two files, so
they should have been hard linked not copied.
=20
I have also tried with
rsync -avxAHXp --link-dest=3D./crawler-root-aug12-2022 / ./crawler-root-nov6-2022 but the same thing happens (no hard link)
=20
(Note that the fact that crawler-root-aug12-2022/dead.letter has a
hard link, that is to a previous backup I made. Even if I erase all
of crawler-root-nov6-2022 its hard link status remains at 2)
=20
Can anyone offer me a clue as to what could be going wrong?
I am trying to copy a backup on a usb hard drive. The usb partition is
ext4 as is the partition I am trying to back up
mount
/dev/nvme0n1p8 on / type ext4 (rw,noatime)
/dev/sda2 on /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca
type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)
/dev/sda2 is a usb drive. / is an internal ssh drive.
I run
rsync -avxAHXp --link-dest ./crawler-root-aug12-2022 / ./crawler-root-nov6-2022
while on the backup directory on the usb drive (mounted in
/run/media/unruh)
But for example
crawler:0[root]>ls -l crawler-root-*-2022/dead.letter
-rw------- 2 root root 7210272 Dec 12 2021 crawler-root-aug12-2022/dead.letter
-rw------- 1 root root 7210272 Dec 12 2021 crawler-root-nov6-2022/dead.letter
shows that dead.letter was copied over, not hard linked.
diff on the two says there is no difference between the two files, so
they should have been hard linked not copied.
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / ./crawler-root-nov6-2022
but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter has a hard
link, that is to a previous backup I made. Even if I erase all of crawler-root-nov6-2022
its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
I am trying to copy a backup on a usb hard drive. The usb partition is
ext4 as is the partition I am trying to back up
mount
/dev/nvme0n1p8 on / type ext4 (rw,noatime)
/dev/sda2 on /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)
/dev/sda2 is a usb drive. / is an internal ssh drive.
I run
rsync -avxAHXp --link-dest ./crawler-root-aug12-2022 / ./crawler-root-nov6-2022
I am trying to copy a backup on a usb hard drive. The usb partition is
ext4 as is the partition I am trying to back up
mount
/dev/nvme0n1p8 on / type ext4 (rw,noatime)
/dev/sda2 on /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)
/dev/sda2 is a usb drive. / is an internal ssh drive.
I run
rsync -avxAHXp --link-dest ./crawler-root-aug12-2022 / ./crawler-root-nov6-2022
while on the backup directory on the usb drive (mounted in
/run/media/unruh)
But for example
crawler:0[root]>ls -l crawler-root-*-2022/dead.letter
-rw------- 2 root root 7210272 Dec 12 2021 crawler-root-aug12-2022/dead.letter
-rw------- 1 root root 7210272 Dec 12 2021 crawler-root-nov6-2022/dead.letter
shows that dead.letter was copied over, not hard linked.
diff on the two says there is no difference between the two files, so
they should have been hard linked not copied.
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / ./crawler-root-nov6-2022
but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter has a hard
link, that is to a previous backup I made. Even if I erase all of crawler-root-nov6-2022
its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
On 06.11.2022 at 17:14, William Unruh scribbled:.....
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 /
./crawler-root-nov6-2022 but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter has a
hard link, that is to a previous backup I made. Even if I erase all
of crawler-root-nov6-2022 its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
You forgot the "=". It should have been...
$ rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / \
./crawler-root-nov6-2022
↑
On 2022-11-06 18:14, William Unruh wrote:
I am trying to copy a backup on a usb hard drive. The usb partition is
ext4 as is the partition I am trying to back up
mount
/dev/nvme0n1p8 on / type ext4 (rw,noatime)
/dev/sda2 on /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca type ext4 (rw,nosuid,nodev,relatime,errors=remount-ro,uhelper=udisks2)
/dev/sda2 is a usb drive. / is an internal ssh drive.
I run
rsync -avxAHXp --link-dest ./crawler-root-aug12-2022 / ./crawler-root-nov6-2022
Doesn't the source include the destination?
On Sun, 06 Nov 2022 12:14:19 -0500, William Unruh <unruh@invalid.ca> wrote:
(Note that the fact that crawler-root-aug12-2022/dead.letter has a hard
link, that is to a previous backup I made. Even if I erase all of crawler-root-nov6-2022
its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
Please show the output of "ls -il crawler-root-*-2022/dead.letter" to confirm which inode each is pointing to.
Regards, Dave Hodgins
On 2022-11-06, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
On Sun, 06 Nov 2022 12:14:19 -0500, William Unruh <unruh@invalid.ca> wrote: >>
(Note that the fact that crawler-root-aug12-2022/dead.letter has a hard >>> link, that is to a previous backup I made. Even if I erase all of crawler-root-nov6-2022
its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
Please show the output of "ls -il crawler-root-*-2022/dead.letter" to confirm
which inode each is pointing to.
Regards, Dave Hodgins
crawler:0[unruh]>ls -il /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-*-2022/dead.letter
52429120 -rw------- 2 root root 7210272 Dec 12 2021 /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-root-aug12-2022/dead.letter
49152355 -rw------- 1 root root 7210272 Dec 12 2021 /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-root-nov6-2022/dead.letter
On 2022-11-06, Aragorn <telcontar@duck.com> wrote:
On 06.11.2022 at 17:14, William Unruh scribbled:....
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 /
./crawler-root-nov6-2022 but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter has a
hard link, that is to a previous backup I made. Even if I erase all
of crawler-root-nov6-2022 its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
You forgot the "=". It should have been...
$ rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / \
./crawler-root-nov6-2022
As I said, I tried that.
William Unruh wrote on 7/11/22 12:03 pm:
On 2022-11-06, Aragorn <telcontar@duck.com> wrote:
On 06.11.2022 at 17:14, William Unruh scribbled:....
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 /
./crawler-root-nov6-2022 but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter
has a hard link, that is to a previous backup I made. Even if I
erase all of crawler-root-nov6-2022 its hard link status remains
at 2)
Can anyone offer me a clue as to what could be going wrong?
You forgot the "=". It should have been...
$ rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / \
./crawler-root-nov6-2022
As I said, I tried that.
William, did you notice that the 'rsync' command you posted ended its
first line with *2022 /* and then continued on the next line whereas Aragon's command had *2022 / \* and then continued on the next line??
Is Aragon's extra *\* important??
William Unruh wrote on 7/11/22 12:03 pm:
On 2022-11-06, Aragorn <telcontar@duck.com> wrote:
On 06.11.2022 at 17:14, William Unruh scribbled:....
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 /
./crawler-root-nov6-2022 but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter has a
hard link, that is to a previous backup I made. Even if I erase all
of crawler-root-nov6-2022 its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
You forgot the "=". It should have been...
$ rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / \
./crawler-root-nov6-2022
As I said, I tried that.
William, did you notice that the 'rsync' command you posted ended its
first line with *2022 /* and then continued on the next line whereas Aragon's command had *2022 / \* and then continued on the next line??
Is Aragon's extra *\* important??
On Sun, 06 Nov 2022 20:09:22 -0500, William Unruh <unruh@invalid.ca> wrote:
On 2022-11-06, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
On Sun, 06 Nov 2022 12:14:19 -0500, William Unruh <unruh@invalid.ca> wrote: >>>
(Note that the fact that crawler-root-aug12-2022/dead.letter has a hard >>>> link, that is to a previous backup I made. Even if I erase all of crawler-root-nov6-2022
its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
Please show the output of "ls -il crawler-root-*-2022/dead.letter" to confirm
which inode each is pointing to.
Regards, Dave Hodgins
crawler:0[unruh]>ls -il /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-*-2022/dead.letter
52429120 -rw------- 2 root root 7210272 Dec 12 2021 /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-root-aug12-2022/dead.letter
49152355 -rw------- 1 root root 7210272 Dec 12 2021 /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-root-nov6-2022/dead.letter
Figured it out ...
[root@x3 /tmp]# ls -li source/* dest*/*
270 -rw-r--r-- 1 dave dave 5 Nov 7 00:41 dest1/datafile
269 -rw-r--r-- 1 dave dave 5 Nov 7 00:41 source/datafile
[root@x3 /tmp]# rsync -avxAHXp --link-dest=/tmp/dest1/ ./source/ /tmp/dest2/ sending incremental file list
./
sent 94 bytes received 19 bytes 226.00 bytes/sec
total size is 5 speedup is 0.04
[root@x3 /tmp]# ls -li source/* dest*/*
270 -rw-r--r-- 2 dave dave 5 Nov 7 00:41 dest1/datafile
270 -rw-r--r-- 2 dave dave 5 Nov 7 00:41 dest2/datafile
269 -rw-r--r-- 1 dave dave 5 Nov 7 00:41 source/datafile
The --link-dest= must be an absolute path, not a relative one. No idea why, but using ./dest2 instead of /tmp/dest2 in my testing does not work.
Regards, Dave Hodgins
On 2022-11-07, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
On Sun, 06 Nov 2022 20:09:22 -0500, William Unruh <unruh@invalid.ca> wrote: >>
On 2022-11-06, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
On Sun, 06 Nov 2022 12:14:19 -0500, William Unruh <unruh@invalid.ca> wrote:
(Note that the fact that crawler-root-aug12-2022/dead.letter has a hard >>>>> link, that is to a previous backup I made. Even if I erase all of crawler-root-nov6-2022
its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
Please show the output of "ls -il crawler-root-*-2022/dead.letter" to confirm
which inode each is pointing to.
Regards, Dave Hodgins
crawler:0[unruh]>ls -il /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-*-2022/dead.letter
52429120 -rw------- 2 root root 7210272 Dec 12 2021 /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-root-aug12-2022/dead.letter
49152355 -rw------- 1 root root 7210272 Dec 12 2021 /run/media/unruh/ab7c8370-e9d4-495f-a9fa-a18e803dd9ca/crawler-root-nov6-2022/dead.letter
Figured it out ...
[root@x3 /tmp]# ls -li source/* dest*/*
270 -rw-r--r-- 1 dave dave 5 Nov 7 00:41 dest1/datafile
269 -rw-r--r-- 1 dave dave 5 Nov 7 00:41 source/datafile
[root@x3 /tmp]# rsync -avxAHXp --link-dest=/tmp/dest1/ ./source/ /tmp/dest2/ >> sending incremental file list
./
sent 94 bytes received 19 bytes 226.00 bytes/sec
total size is 5 speedup is 0.04
[root@x3 /tmp]# ls -li source/* dest*/*
270 -rw-r--r-- 2 dave dave 5 Nov 7 00:41 dest1/datafile
270 -rw-r--r-- 2 dave dave 5 Nov 7 00:41 dest2/datafile
269 -rw-r--r-- 1 dave dave 5 Nov 7 00:41 source/datafile
The --link-dest= must be an absolute path, not a relative one. No idea why, >> but using ./dest2 instead of /tmp/dest2 in my testing does not work.
OK, I will try that. Weird. It needs to be documented in the man page.
Thanks for tracking this down.
I guess it should have been ../dest1 or as you say, /tmp/dest1
On 07.11.2022 at 19:50, Daniel65 scribbled:
William Unruh wrote on 7/11/22 12:03 pm:
On 2022-11-06, Aragorn <telcontar@duck.com> wrote:
On 06.11.2022 at 17:14, William Unruh scribbled:....
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 /
./crawler-root-nov6-2022 but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter
has a hard link, that is to a previous backup I made. Even if I
erase all of crawler-root-nov6-2022 its hard link status remains
at 2)
Can anyone offer me a clue as to what could be going wrong?
You forgot the "=". It should have been...
$ rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / \
./crawler-root-nov6-2022
As I said, I tried that.
William, did you notice that the 'rsync' command you posted ended its
first line with *2022 /* and then continued on the next line whereas
Aragon's command had *2022 / \* and then continued on the next line??
Is Aragon's extra *\* important??
I added the backslash because my newsreader wraps the lines at 72
characters, which broke up Bill's command in two lines. The backslash therefore escapes the newline character.
On 2022-11-07, Daniel65 <daniel47@nomail.afraid.org> wrote:
William Unruh wrote on 7/11/22 12:03 pm:
On 2022-11-06, Aragorn <telcontar@duck.com> wrote:
On 06.11.2022 at 17:14, William Unruh scribbled:....
I have also tried with
rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 /
./crawler-root-nov6-2022 but the same thing happens (no hard link)
(Note that the fact that crawler-root-aug12-2022/dead.letter has a >>>>> hard link, that is to a previous backup I made. Even if I erase all
of crawler-root-nov6-2022 its hard link status remains at 2)
Can anyone offer me a clue as to what could be going wrong?
You forgot the "=". It should have been...
$ rsync -avxAHXp --link-dest=./crawler-root-aug12-2022 / \
./crawler-root-nov6-2022
As I said, I tried that.
William, did you notice that the 'rsync' command you posted ended its
first line with *2022 /* and then continued on the next line whereas
Aragon's command had *2022 / \* and then continued on the next line??
Is Aragon's extra *\* important??
My linebreak cam about because the posting software put in a linebreak
into a long line. What was actually run had no line break.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 300 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 34:40:02 |
| Calls: | 6,707 |
| Files: | 12,239 |
| Messages: | 5,353,334 |