Using rsync to backup to external USB drive of type msdos?
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I am trying to use rsync (on Linux Mint) to backup to an external USB drive of type msdos (as shown in the drive properties), using a command:
rsync -av ~/Documents/rsynctest/ /media/myname/PC/rsynctest --delete
However it is copying some files that have not been changed since I last run this command. What is going on here and is there a straight forward solution, without having to reformat the drive?
Adding the "i" flag causes the outputs of lines such as:
.f...p..... CBCTest/bin/Debug/CBCTest
usb rsync
asked Aug 23 at 19:21
tyebillion
19910
add a comment |Â
up vote
0
down vote
favorite
I am trying to use rsync (on Linux Mint) to backup to an external USB drive of type msdos (as shown in the drive properties), using a command:
rsync -av ~/Documents/rsynctest/ /media/myname/PC/rsynctest --delete
However it is copying some files that have not been changed since I last run this command. What is going on here and is there a straight forward solution, without having to reformat the drive?
Adding the "i" flag causes the outputs of lines such as:
.f...p..... CBCTest/bin/Debug/CBCTest
usb rsync
asked Aug 23 at 19:21
tyebillion
19910
1
were the files changes very recently, as-in 1 or 2 seconds?
– mjb2kmn
Aug 23 at 19:28
No, not recently changed.
– tyebillion
Aug 23 at 19:41
1
Try adding the-iflag. You'll get output with flags for every file it's copying. Can you add in some of the lines that it prints to your question?
– BowlOfRed
Aug 23 at 19:56
I updated my question.
– tyebillion
Aug 23 at 20:02
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to use rsync (on Linux Mint) to backup to an external USB drive of type msdos (as shown in the drive properties), using a command:
rsync -av ~/Documents/rsynctest/ /media/myname/PC/rsynctest --delete
However it is copying some files that have not been changed since I last run this command. What is going on here and is there a straight forward solution, without having to reformat the drive?
Adding the "i" flag causes the outputs of lines such as:
.f...p..... CBCTest/bin/Debug/CBCTest
usb rsync
asked Aug 23 at 19:21
tyebillion
19910
I am trying to use rsync (on Linux Mint) to backup to an external USB drive of type msdos (as shown in the drive properties), using a command:
rsync -av ~/Documents/rsynctest/ /media/myname/PC/rsynctest --delete
However it is copying some files that have not been changed since I last run this command. What is going on here and is there a straight forward solution, without having to reformat the drive?
Adding the "i" flag causes the outputs of lines such as:
.f...p..... CBCTest/bin/Debug/CBCTest
usb rsync
usb rsync
asked Aug 23 at 19:21
tyebillion
19910
asked Aug 23 at 19:21
tyebillion
19910
edited Aug 23 at 20:01
asked Aug 23 at 19:21
tyebillion
19910
asked Aug 23 at 19:21
tyebillion
19910
asked Aug 23 at 19:21
tyebillion
19910
19910
1
were the files changes very recently, as-in 1 or 2 seconds?
– mjb2kmn
Aug 23 at 19:28
No, not recently changed.
– tyebillion
Aug 23 at 19:41
1
Try adding the-iflag. You'll get output with flags for every file it's copying. Can you add in some of the lines that it prints to your question?
– BowlOfRed
Aug 23 at 19:56
I updated my question.
– tyebillion
Aug 23 at 20:02
add a comment |Â
1
were the files changes very recently, as-in 1 or 2 seconds?
– mjb2kmn
Aug 23 at 19:28
No, not recently changed.
– tyebillion
Aug 23 at 19:41
1
Try adding the-iflag. You'll get output with flags for every file it's copying. Can you add in some of the lines that it prints to your question?
– BowlOfRed
Aug 23 at 19:56
I updated my question.
– tyebillion
Aug 23 at 20:02
1
1
were the files changes very recently, as-in 1 or 2 seconds?
– mjb2kmn
Aug 23 at 19:28
were the files changes very recently, as-in 1 or 2 seconds?
– mjb2kmn
Aug 23 at 19:28
No, not recently changed.
– tyebillion
Aug 23 at 19:41
No, not recently changed.
– tyebillion
Aug 23 at 19:41
1
1
Try adding the
-i flag. You'll get output with flags for every file it's copying. Can you add in some of the lines that it prints to your question?– BowlOfRed
Aug 23 at 19:56
Try adding the
-i flag. You'll get output with flags for every file it's copying. Can you add in some of the lines that it prints to your question?– BowlOfRed
Aug 23 at 19:56
I updated my question.
– tyebillion
Aug 23 at 20:02
I updated my question.
– tyebillion
Aug 23 at 20:02
add a comment |Â
3 Answers
3
active
oldest
votes
up vote
1
down vote
You will need to workaround rsync with:
--size-only
But if the files are exactly the same size but differents, maybe it will be not upgraded.
Good Lucky!
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
add a comment |Â
up vote
1
down vote
Vfat filesystems (that I guess "type msdos" means) does not support user/group/permissions on files, so every file on an vfat filesystem will appear with some synthetic values (set at mount time) for the parameters. If those differ from the values that the files you're trying to sync has, rsync (called with -o/-g/-p - all are included in the meaning of -a) will think something has changed and re-copy the file.
answered Aug 23 at 20:27
Henrik
3,2791418
add a comment |Â
up vote
1
down vote
In your output
.f...p..... CBCTest/bin/Debug/CBCTest
The "p" means that it is updating the (p)ermissions of the destination file because it thinks they need to be.
(It's not actually copying the file since it's already in place, just updating the permissions).
Some filesystems may simply be incapable of matching the "correct" permissions. For instance if you are trying to rsync to a FAT filesystem that won't store permissions the same way. In such case you may just want to turn off permissions preservation. Either don't supply -p/--perms, or if they're being included through something like -a, give a --no-perms afterward.
Or, maybe the permissions really were changed. You'll have to investigate on your end.
answered Aug 23 at 21:52
BowlOfRed
2,370612
add a comment |Â
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
You will need to workaround rsync with:
--size-only
But if the files are exactly the same size but differents, maybe it will be not upgraded.
Good Lucky!
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
add a comment |Â
up vote
1
down vote
You will need to workaround rsync with:
--size-only
But if the files are exactly the same size but differents, maybe it will be not upgraded.
Good Lucky!
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
add a comment |Â
up vote
1
down vote
up vote
1
down vote
You will need to workaround rsync with:
--size-only
But if the files are exactly the same size but differents, maybe it will be not upgraded.
Good Lucky!
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
You will need to workaround rsync with:
--size-only
But if the files are exactly the same size but differents, maybe it will be not upgraded.
Good Lucky!
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
answered Aug 23 at 19:37
Luciano Andress Martini
3,153829
3,153829
add a comment |Â
add a comment |Â
up vote
1
down vote
Vfat filesystems (that I guess "type msdos" means) does not support user/group/permissions on files, so every file on an vfat filesystem will appear with some synthetic values (set at mount time) for the parameters. If those differ from the values that the files you're trying to sync has, rsync (called with -o/-g/-p - all are included in the meaning of -a) will think something has changed and re-copy the file.
answered Aug 23 at 20:27
Henrik
3,2791418
add a comment |Â
up vote
1
down vote
Vfat filesystems (that I guess "type msdos" means) does not support user/group/permissions on files, so every file on an vfat filesystem will appear with some synthetic values (set at mount time) for the parameters. If those differ from the values that the files you're trying to sync has, rsync (called with -o/-g/-p - all are included in the meaning of -a) will think something has changed and re-copy the file.
answered Aug 23 at 20:27
Henrik
3,2791418
add a comment |Â
up vote
1
down vote
up vote
1
down vote
Vfat filesystems (that I guess "type msdos" means) does not support user/group/permissions on files, so every file on an vfat filesystem will appear with some synthetic values (set at mount time) for the parameters. If those differ from the values that the files you're trying to sync has, rsync (called with -o/-g/-p - all are included in the meaning of -a) will think something has changed and re-copy the file.
answered Aug 23 at 20:27
Henrik
3,2791418
Vfat filesystems (that I guess "type msdos" means) does not support user/group/permissions on files, so every file on an vfat filesystem will appear with some synthetic values (set at mount time) for the parameters. If those differ from the values that the files you're trying to sync has, rsync (called with -o/-g/-p - all are included in the meaning of -a) will think something has changed and re-copy the file.
answered Aug 23 at 20:27
Henrik
3,2791418
answered Aug 23 at 20:27
Henrik
3,2791418
answered Aug 23 at 20:27
Henrik
3,2791418
answered Aug 23 at 20:27
Henrik
3,2791418
3,2791418
add a comment |Â
add a comment |Â
up vote
1
down vote
In your output
.f...p..... CBCTest/bin/Debug/CBCTest
The "p" means that it is updating the (p)ermissions of the destination file because it thinks they need to be.
(It's not actually copying the file since it's already in place, just updating the permissions).
Some filesystems may simply be incapable of matching the "correct" permissions. For instance if you are trying to rsync to a FAT filesystem that won't store permissions the same way. In such case you may just want to turn off permissions preservation. Either don't supply -p/--perms, or if they're being included through something like -a, give a --no-perms afterward.
Or, maybe the permissions really were changed. You'll have to investigate on your end.
answered Aug 23 at 21:52
BowlOfRed
2,370612
add a comment |Â
up vote
1
down vote
In your output
.f...p..... CBCTest/bin/Debug/CBCTest
The "p" means that it is updating the (p)ermissions of the destination file because it thinks they need to be.
(It's not actually copying the file since it's already in place, just updating the permissions).
Some filesystems may simply be incapable of matching the "correct" permissions. For instance if you are trying to rsync to a FAT filesystem that won't store permissions the same way. In such case you may just want to turn off permissions preservation. Either don't supply -p/--perms, or if they're being included through something like -a, give a --no-perms afterward.
Or, maybe the permissions really were changed. You'll have to investigate on your end.
answered Aug 23 at 21:52
BowlOfRed
2,370612
add a comment |Â
up vote
1
down vote
up vote
1
down vote
In your output
.f...p..... CBCTest/bin/Debug/CBCTest
The "p" means that it is updating the (p)ermissions of the destination file because it thinks they need to be.
(It's not actually copying the file since it's already in place, just updating the permissions).
Some filesystems may simply be incapable of matching the "correct" permissions. For instance if you are trying to rsync to a FAT filesystem that won't store permissions the same way. In such case you may just want to turn off permissions preservation. Either don't supply -p/--perms, or if they're being included through something like -a, give a --no-perms afterward.
Or, maybe the permissions really were changed. You'll have to investigate on your end.
answered Aug 23 at 21:52
BowlOfRed
2,370612
In your output
.f...p..... CBCTest/bin/Debug/CBCTest
The "p" means that it is updating the (p)ermissions of the destination file because it thinks they need to be.
(It's not actually copying the file since it's already in place, just updating the permissions).
Some filesystems may simply be incapable of matching the "correct" permissions. For instance if you are trying to rsync to a FAT filesystem that won't store permissions the same way. In such case you may just want to turn off permissions preservation. Either don't supply -p/--perms, or if they're being included through something like -a, give a --no-perms afterward.
Or, maybe the permissions really were changed. You'll have to investigate on your end.
answered Aug 23 at 21:52
BowlOfRed
2,370612
answered Aug 23 at 21:52
BowlOfRed
2,370612
answered Aug 23 at 21:52
BowlOfRed
2,370612
answered Aug 23 at 21:52
BowlOfRed
2,370612
2,370612
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f464486%2fusing-rsync-to-backup-to-external-usb-drive-of-type-msdos%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
were the files changes very recently, as-in 1 or 2 seconds?
– mjb2kmn
Aug 23 at 19:28
No, not recently changed.
– tyebillion
Aug 23 at 19:41
1
Try adding the
-iflag. You'll get output with flags for every file it's copying. Can you add in some of the lines that it prints to your question?– BowlOfRed
Aug 23 at 19:56
I updated my question.
– tyebillion
Aug 23 at 20:02