search

hjmangalam / parsyncfp

follow-on to parsync (parallel rsync) with better startup perf
Other
161 stars 19 forks source link

Failure to exit when empty directory detected #1

Closed caljess599 closed 7 years ago

caljess599 commented 7 years ago

Instead of exiting, it just hung, waiting for chunks to be written. I have a script that executes several parasyncfp in series... when it arrived at this one:

parsyncfp --nowait --maxload=6 --NP=6 --checkperiod='900' --startdir='/lustre/naasc' --rsyncopts='--whole-file --archive --prune-empty-dirs --safe-links --human-readable --delete' projects /.lustre/lard/

it simply hung because the directory is in fact empty...

parsyncing ../projects

  WARN: about to remove all the old cached chunkfiles from [/root/.parsyncfp/fpcache].
  ^C to stop this.

  Otherwise, hit [Enter] and I'll clear them.
  If you specified '--nowait', I'll continue in 5s regardless.

INFO: The fpart chunk files [/root/.parsyncfp/fpcache/fpc.*] are cleared.. continuing

INFO: Forking fpart..
Check [/root/.parsyncfp/fpcache/fpart.log.19.07.57_2017-05-24] for errors if it hangs.
INFO: Waiting [50647] s for chunk files to be written

At this point, I hit Ctrl + C... the error is logged but not passed through to cause parsyncfp to exit

[root@akebono ~]# cat /root/.parsyncfp/fpcache/fpart.log.19.07.57_2017-05-24
Examining filesystem...
0 file(s) found.
hjmangalam commented 7 years ago

fixed in the latest (June/06) set of patches.