search for: utime_now

guestmount.c: In function 'fg_utimens': guestmount.c:537: error: 'UTIME_NOW' undeclared (first use in this function) guestmount.c:537: error: (Each undeclared identifier is reported only once guestmount.c:537: error: for each function it appears in.) guestmount.c:539: error: 'UTIME_OMIT' undeclared (first use in this function) I'm not sure what's the b...

...deletions(-) diff --git a/fuse/guestmount.c b/fuse/guestmount.c index baf2b66..05cacef 100644 --- a/fuse/guestmount.c +++ b/fuse/guestmount.c @@ -534,14 +534,22 @@ fg_utimens (const char *path, const struct timespec ts[2]) time_t mtsecs = ts[1].tv_sec; long mtnsecs = ts[1].tv_nsec; +#ifdef UTIME_NOW if (atnsecs == UTIME_NOW) atnsecs = -1; +#endif +#ifdef UTIME_OMIT if (atnsecs == UTIME_OMIT) atnsecs = -2; +#endif +#ifdef UTIME_NOW if (mtnsecs == UTIME_NOW) mtnsecs = -1; +#endif +#ifdef UTIME_OMIT if (mtnsecs == UTIME_OMIT) mtnsecs = -2; +#endif r = guestfs_...

On Thu, 2016-10-13 at 20:08 -0400, Kevin Korb wrote: > I don't remember whether or not you said you were running rsync over > ssh but if you are you can also debug the ssh layer.  You can even do > it at both ends.... > > On the server run a debugging sshd on an alternate port with: > /usr/sbin/sshd -dDp222 > (note that this will only accept 1 connection, debug to the

This version doesn't crash or cause hung processes or stuck mountpoints, so that's an improvement. Rich.

This patch is just for review. It enables FUSE support in the API via two new calls, 'guestfs_mount_local' and 'guestfs_umount_local'. FUSE turns out to be very easy to deadlock (necessitating that the machine be rebooted). Running the test from the third patch is usually an effective way to demonstrate this. However I have not yet managed to produce a simple reproducer that

...ourse break the bogus nanosecond mtimes anyway. For a discussion, please refer to a following rsync lists message: https://lists.samba.org/archive/rsync/2017-April/031177.html , but in short -- nanosecond mtime values: (a) are not supposed to exist, since we need to define at least UTIME_OMIT and UTIME_NOW as long values, and have no other choice but to put these constants somewhere outside of 0 .. 1 000 000 000 interval ; (b) can still appear on a filesystem nevertheless due to some possible imperfections in the OS code or filesystem implemenation ; (c) are not really taken into account by rsync 3...

This changes the proposed API slightly. Previously 'mount-local' generating a 'mounted' event when the filesystem was ready, and from the 'mounted' event you had to effectively do a fork. Now, 'mount-local' just initializes the mountpoint and you have to call 'mount-local-run' to enter the FUSE main loop. Between these calls you can do a fork or whatever

...ents\0", 1024) = 27 7: 27251 lgetxattr("osd/0.6ed_head/DIR_D/DIR_E/DIR_6", "user.cephos.phash.contents", 0x0, 0) = -1 ENODATA (No data available) 8: 27253 <... lsetxattr resumed> ) = 0 9: 27253 utimensat(AT_FDCWD, "osd/0.6ed_head/DIR_D/DIR_E/DIR_6", {UTIME_NOW, {1407992261, 0}}, AT_SYMLINK_NOFOLLOW) = 0 a: 27251 write(2, "rsync: get_xattr_data: lgetxattr"..., 181) = 181 lines 0-2, 3-6 and 5-8, show concurrent access of both rsync processes to the same directory. This wouldn't be a problem, not even for replaying batches, for the lsetxattr...