On Sat, Oct 29, 2016 at 11:29:08PM +0200, Yuri D'Elia wrote:
> On Fri, Oct 28 2016, Theodore Ts'o wrote:
> > I could be confused, but I thought the original bug report involved
> > the journal containing unexpected zero bytes after a system crash?
>
> It can also happen (this is a laptop, and when the battery goes the fs
> is not synced), and from this instance it can be the case.
>
> But it's too frequent to be always the case. I'll collect one broken
> journal making sure the system didn't go down for some reason.
I propose to run strace in your cron job, to clarify whether corrupted
data is written by isync, i.e. change command to something like
strace -s128 -o /var/log/`date +%d%H%M%S`/isync.strace \
-e open,read,write -f timeout ... isync ...
Note that in crontab(5) each % should be escaped as \% and
complete command should be written on a single line.
--
Eugene Berdnikov
------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel
