Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#774834: rdiff-backup: When backing up to a vfat partition on a remote host, rdiffbackup fails on case-sensitive dirnames
4 views
Skip to first unread message
Kasper Loopstra
Jan 8, 2015, 4:40:02 AM1/8/15
to
Package: rdiff-backup
Version: 1.2.8-7
Severity: normal
When backing up a folder with subfolders A and a, to a vfat filesystem on a remote host that is mounted auto in fstab, rdiffbackup fales with a 'File already exists'. The rdiff-backup manual seems to imply that this should work. Changing the remote filesystem to ext3 allows the backup to work as ecptected.
-- System Information:
Debian Release: 7.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rdiff-backup depends on:
ii libc6 2.13-38+deb7u6
ii librsync1 0.9.7-9
ii python 2.7.3-4+deb7u1
ii python2.6 2.6.8-1.1
ii python2.7 2.7.3-6+deb7u2
Versions of packages rdiff-backup recommends:
ii python-pylibacl 0.5.1-1.1
ii python-pyxattr 0.5.1-1.1
rdiff-backup suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Version: 1.2.8-7
Severity: normal
When backing up a folder with subfolders A and a, to a vfat filesystem on a remote host that is mounted auto in fstab, rdiffbackup fales with a 'File already exists'. The rdiff-backup manual seems to imply that this should work. Changing the remote filesystem to ext3 allows the backup to work as ecptected.
-- System Information:
Debian Release: 7.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages rdiff-backup depends on:
ii libc6 2.13-38+deb7u6
ii librsync1 0.9.7-9
ii python 2.7.3-4+deb7u1
ii python2.6 2.6.8-1.1
ii python2.7 2.7.3-6+deb7u2
Versions of packages rdiff-backup recommends:
ii python-pylibacl 0.5.1-1.1
ii python-pyxattr 0.5.1-1.1
rdiff-backup suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Pablo Mestre
Oct 14, 2020, 2:40:03 PM10/14/20
to
I think this behavior is more associated with the characteristics of the
remote host that vfat uses.
If you manually create a directory A and another with a name, what
result do you get?
--
⢀⣴⠾⠻⢶⣦⠀ Pablo Mestre Drake
⣾⠁⢠⠒⠀⣿⡁ --------------------------------------
⢿⡄⠘⠷⠚⠋ https://debian.org
⠈⠳⣄⠀⠀⠀⠀ Debian, the universal operating system.
remote host that vfat uses.
If you manually create a directory A and another with a name, what
result do you get?
--
⢀⣴⠾⠻⢶⣦⠀ Pablo Mestre Drake
⣾⠁⢠⠒⠀⣿⡁ --------------------------------------
⢿⡄⠘⠷⠚⠋ https://debian.org
⠈⠳⣄⠀⠀⠀⠀ Debian, the universal operating system.
Pablo Mestre
Sep 28, 2021, 11:00:03 PM9/28/21
to
Hi Kasper Loopstra
Thank you very much for reporting this error.
I would like to ask you if this error is still present in the most
recent versions of rdiff-backup. Currently after a series of
improvements and bug fixes, rdiff-backup is at version 2.0.5 [1]
It would be very helpful if you checked again if this bug is still present. Otherwise we can agree to close the bug,
[1] https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.0.5 <https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.0.5>
Thank you very much for reporting this error.
I would like to ask you if this error is still present in the most
recent versions of rdiff-backup. Currently after a series of
improvements and bug fixes, rdiff-backup is at version 2.0.5 [1]
It would be very helpful if you checked again if this bug is still present. Otherwise we can agree to close the bug,
[1] https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.0.5 <https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.0.5>
0 new messages