On Fri, Oct 28, 2016 at 02:36:42PM -0400, Theodore Ts'o wrote: > On Fri, Oct 28, 2016 at 07:21:58PM +0300, Evgeniy Berdnikov wrote: ... > > Oswald is right, process completion (by exit() or interrupt by signal) > > can only truncate data, but can not corrupt. Only system crash can > > lead to data corruption. > > I could be confused, but I thought the original bug report involved > the journal containing unexpected zero bytes after a system crash?
Original mail stated that isync is started as cron job under "timeout" utility (designed to spawn a command and then terminate it by signal if command run too much time). Sometimes journal file gets truncated records with trailing zeros. Looks like a result of system crash, yes, but crashes were not mentioned. -- 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
