GNU bug report logs - #22768
Crash safety

Previous Next

Package: gzip;

Reported by: Yanyan Jiang <jiangyy <at> outlook.com>

Date: Mon, 22 Feb 2016 16:02:02 UTC

Severity: normal

Merged with 22770

Done: Paul Eggert <eggert <at> cs.ucla.edu>

Bug is archived. No further changes may be made.

Full log

Message #62 received at 22768 <at> debbugs.gnu.org (full text, mbox):

From: Antonio Diaz Diaz <antonio <at> gnu.org>
To: 22768 <at> debbugs.gnu.org
Cc: Yanyan Jiang <jiangyy <at> outlook.com>
Subject: Re: bug#22768: Crash safety
Date: Thu, 03 Mar 2016 14:08:09 +0100

Paul Eggert wrote:
> You may well be right that eventually file system designers will figure 
> this stuff out so that well-written POSIX applications will not lose 
> data even if they don't use fsync/fdatasync. However, if FSCQ is any 
> indication, we're many years away from that. In the meantime 
> fsync/fdatasync is all we have.

Thanks for the explanation. I have already started the last round of 
release candidates of the lzip family, but just after releasing 
lzip-1.18, in a month or so, i'll implement --synchronous in a way 
compatible with what you implement in gzip.


Best regards,
Antonio.
This bug report was last modified 9 years and 74 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.