I can confirm the bug has not been fixed in rsync 3.0.5 encfs 1.4.2
(Ubuntu Jaunty)
The patch still works with rsync 3.0.5
Download source from
http://www.samba.org/ftp/rsync/src/rsync-3.0.5.tar.gz
Extract to /tmp
cd /tmp
vi syscall.c
Search for do_rename. Apply patch save
./configure
make
I'm having the same problem on hardy.
It seems to only be a problem if External IV Chaining is turned on,
which it is in paranoia mode.
When creating the encfs filesystem to use with rsync, use standard mode
or in expert mode say no to Enable filename to IV header chaining? That
seems to work
I am afraid I am still affected by this issue , on hardy :
FYI:
LANG=C encfsctl /home/$USER/local/encfs/
Version 5 configuration; created by EncFS 1.3.2 (revision 20040813)
Filesystem cipher: ssl/aes, version 2:1:1
Filename encoding: nameio/block, version 3:0:1
Key Size: 256 bits
Block Size:
Ok, I got it working. It is though not because of Fuse which I updated from
version 2.7.2 to 2.7.3 but because I created the encfs folder with cryptkeeper
before which might have used the paranoia option by default, I'm not sure.
Creating with encfs folder folder and then selecting standard mode
just to followup on my original report:
i am no longer seeing the error messages I reported above in the latest
hardy 8.04
--
rsync timestamp bug on encfs/fuse
https://bugs.launchpad.net/bugs/81080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Ah, great, ubuntu still has 1.3.2 in hardy... And that means all files
get the current time which still makes rsync unusable. Did anybody try
to compile and use 1.4.2 ? I'll try it anyway...
--
rsync timestamp bug on encfs/fuse
https://bugs.launchpad.net/bugs/81080
You received this bug
I still get the same behaviour using debian packages with encfs 1.4.1.1
I created a new specific encfs dir. Copying files with rsync makes all files
have the current timestamp.
I'll try to compile encfs 1.4.2 from source.
--
rsync timestamp bug on encfs/fuse
I get the same issue with encfs 1.4.2. Is there something else I might
be missing? Flags when calling encfs?
--
rsync timestamp bug on encfs/fuse
https://bugs.launchpad.net/bugs/81080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You may want to try upgrading to a newer version of FUSE.
I cannot reproduce this behavior - I see exactly the same timestamps
when I rsync to an encfs filesystem as I do when syncing to an ext3
filesystem.
If you are still seeing this after upgrading FUSE and encfs, then please
provide the
Valient Gough,
When you state that this will be in the next release, are you talking
8.04? Or will an update be released for 7.10?
--
rsync timestamp bug on encfs/fuse
https://bugs.launchpad.net/bugs/81080
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Next release of encfs. I do not maintain the Ubuntu package, or have
any control over Ubuntu releases, or even Ubuntu packages of encfs.
As the previous mail said, the problem could not be reproduced with
encfs 1.4.0 release. The current release is 1.4.1.1.
--
rsync timestamp bug on
** Changed in: fuse (Ubuntu)
Status: New = Fix Released
--
rsync timestamp bug on encfs/fuse
https://bugs.launchpad.net/bugs/81080
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I haven't been able to reproduce this with encfs 1.4.0 on Ubuntu Gutsy
x86-64 install. Marking closed.
** Changed in: encfs
Status: Fix Committed = Fix Released
--
rsync timestamp bug on encfs/fuse
https://bugs.launchpad.net/bugs/81080
You received this bug notification because you are
This may be due to new time functions in FUSE not implemented in encfs..
It works on the development branch, tested on x86-64 Gutsy. Will be in
next release.
** Also affects: encfs
Importance: Undecided
Status: New
** Changed in: encfs
Assignee: (unassigned) = Valient Gough
I got tired of rebooting to run my backups once a week and so I
installed a 32bit chroot edgy (6.10) install as a workaround. The
backup appears to be running now with no ill effects. Just wanted to
leave a quick note here in case anyone needs/wants to do this. I
specifically installed fuse into
Sorry, this took a lot more than the 24 hours I promised.
So after doing the following, I am still seeing the error:
1. created encfs volume from scratch using default options
2. created one backup using 6.10 without issue
3. ran the backup in gutsy - seeing the error
A couple of lines from my
I finally figured this out and it turned out that you have to create the encfs
with a different option. I found it on the encfs mailing list. If i get time
i'll try to look again but in th meantime you should start there.
How did you create your encfs?
I believe picking the paranoia mode sets an
Hey,
I rebooted to my 6.10 (edgy?) install and was able to run my backups
without any problem. I used the default (non paranoia) settings to
create the encfs partition. I also experimented extensively with the
expert settings and was unable to find a combination that would not
result in the
In gutsy, I am seeing this problem when copying to an encfs partition.
I assume it is somehow related to this bug report:
rsync: failed to set times on
/media/usbbackup/backup/hoopy/inc-0711102037/etc/gtk/gtkrc.sr: No such
file or directory (2)
--
rsync timestamp bug on encfs/fuse
19 matches
Mail list logo
