Re: Truncation Data Loss

2009-11-11 Thread Ted Unangst
On Wed, Nov 11, 2009 at 7:08 PM, Nick Guenther wrote: > Okay, one last question: one of the original softdep papers > (http://www.usenix.org/publications/library/proceedings/bsdcon02/mckusick.html) > is all about how softdeps can avoid fsck, but I just set softdep on > all my filesystems, rebooted

Re: Truncation Data Loss

2009-11-11 Thread Theo de Raadt
> Okay, one last question: one of the original softdep papers > (http://www.usenix.org/publications/library/proceedings/bsdcon02/mckusick.htm > l) > is all about how softdeps can avoid fsck, but I just set softdep on > all my filesystems, rebooted (to start fresh), wrote some files, wrote > some mo

Re: Truncation Data Loss

2009-11-11 Thread David Vasek
On Wed, 11 Nov 2009, Nick Guenther wrote: On Wed, Nov 11, 2009 at 3:35 AM, David Vasek wrote: On Tue, 10 Nov 2009, Nick Guenther wrote: [ext3 data= / FFS] journal ~= sync (ensures consistency of both metadata and file data) ordered ~= softdep (ensures consistency of metadata both internally

Re: Truncation Data Loss

2009-11-11 Thread Nick Guenther
On Wed, Nov 11, 2009 at 1:16 PM, Ted Unangst wrote: > On Tue, Nov 10, 2009 at 10:50 PM, Nick Guenther wrote: >> See, since it seems that BSD doesn't have this file-data consistency >> guarantee, are Linus' worries about ext4's potential data loss just >> being alarmist? It seems to me that the ca

Re: Truncation Data Loss

2009-11-11 Thread Nick Guenther
On Wed, Nov 11, 2009 at 3:35 AM, David Vasek wrote: > On Tue, 10 Nov 2009, Nick Guenther wrote: > >> [ext3 data= / FFS] >> journal ~= sync (ensures consistency of both metadata and file data) >> ordered ~= softdep (ensures consistency of metadata both internally >> and with file data) >> writeback

Re: Truncation Data Loss

2009-11-11 Thread Ted Unangst
On Tue, Nov 10, 2009 at 10:50 PM, Nick Guenther wrote: > See, since it seems that BSD doesn't have this file-data consistency > guarantee, are Linus' worries about ext4's potential data loss just > being alarmist? It seems to me that the case described in > https://bugs.edge.launchpad.net/ubuntu/+

Re: Truncation Data Loss

2009-11-11 Thread Marco Peereboom
EXT was and still is a joke. I remember reading about the 2 minute drain and I almost peed my pants. EXT3 had the nice feature of randomly stopping to boot after enough reboots on enough machines. Thankfully I no longer run any volume of this crap. On Wed, Nov 11, 2009 at 11:55:30AM +, Russ

Re: Truncation Data Loss

2009-11-11 Thread Marco Peereboom
On Wed, Nov 11, 2009 at 12:24:25PM +0100, Janne Johansson wrote: > Nick Guenther wrote: > > So, as nicely summarized at > > > http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html > > , > ext4 is kind of broken. It won't honor fsync and, as a /feature/, will

Re: Truncation Data Loss

2009-11-11 Thread Russell Howe
Michal wrote, sometime around 11/11/09 11:40: I know this is a bit off topic, but storage devices have battery's on RAID cards for a reason. If you are worried about read/writes etc when a system dies, there are measures you can take Probably even more OT, but... Although some (most?) RAID ca

Re: Truncation Data Loss

2009-11-11 Thread Michal
Janne Johansson wrote: > Nick Guenther wrote: > > So, as nicely summarized at > >> http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html >> , > ext4 is kind of broken. It won't honor fsync and, as a /feature/, will > wait up to two minutes to write out data,

Re: Truncation Data Loss

2009-11-11 Thread Janne Johansson
Nick Guenther wrote: So, as nicely summarized at > http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html > , ext4 is kind of broken. It won't honor fsync and, as a /feature/, will wait up to two minutes to write out data, leading to lots of files em

Re: Truncation Data Loss

2009-11-11 Thread David Vasek
On Tue, 10 Nov 2009, Nick Guenther wrote: [ext3 data= / FFS] journal ~= sync (ensures consistency of both metadata and file data) ordered ~= softdep (ensures consistency of metadata both internally and with file data) writeback ~= default (ensures consistency of metadata internally but real file

Re: Truncation Data Loss

2009-11-10 Thread Daniel Ouellet
Bryan Irvine wrote: > I lost a picture of Bob Becks ass this same exact way. Very popular piece of art! And a collectors item these days, specially in Germany looks like! (;> Might be the next hot item on some stickers coming your way next release! (;> Probably would however need a disclaimer a

Re: Truncation Data Loss

2009-11-10 Thread Nick Guenther
On Tue, Nov 10, 2009 at 1:18 PM, Theo de Raadt wrote: >>On Tue, Nov 10, 2009 at 4:29 AM, Nick Guenther wrote: >>> So, as nicely summarized at >>> http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html , >>> ext4 is kind of broken. It won't honor fsync and, as a /feature/, w

Re: Truncation Data Loss

2009-11-10 Thread Brad Tilley
On Tue, Nov 10, 2009 at 5:25 PM, Bob Beck wrote: > 2009/11/10 Jussi Peltola : >> On Tue, Nov 10, 2009 at 11:18:57AM -0700, Theo de Raadt wrote: >>> If you want to never lose data, you have an option. B Make the filesystem >>> syncronous, using the -o sync option. >>> >>> If you can't accept the pe

Re: Truncation Data Loss

2009-11-10 Thread Bryan Irvine
I lost a picture of Bob Becks ass this same exact way. -B On Tue, Nov 10, 2009 at 1:29 AM, Nick Guenther wrote: > So, as nicely summarized at > http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html, > ext4 is kind of broken. It won't honor fsync and, as a /feature/, will

Re: Truncation Data Loss

2009-11-10 Thread Bob Beck
2009/11/10 Jussi Peltola : > On Tue, Nov 10, 2009 at 11:18:57AM -0700, Theo de Raadt wrote: >> If you want to never lose data, you have an option. Make the filesystem >> syncronous, using the -o sync option. >> >> If you can't accept the performance hit from that, then please accept >> that all th

Re: Truncation Data Loss

2009-11-10 Thread Jussi Peltola
On Tue, Nov 10, 2009 at 11:18:57AM -0700, Theo de Raadt wrote: > If you want to never lose data, you have an option. Make the filesystem > syncronous, using the -o sync option. > > If you can't accept the performance hit from that, then please accept > that all the work done over the ages is only

Re: Truncation Data Loss

2009-11-10 Thread Theo de Raadt
>On Tue, Nov 10, 2009 at 4:29 AM, Nick Guenther wrote: >> So, as nicely summarized at >> http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html, >> ext4 is kind of broken. It won't honor fsync and, as a /feature/, will >> wait up to two minutes to write out data, leading to

Re: Truncation Data Loss

2009-11-10 Thread Ted Unangst
On Tue, Nov 10, 2009 at 4:29 AM, Nick Guenther wrote: > So, as nicely summarized at > http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html, > ext4 is kind of broken. It won't honor fsync and, as a /feature/, will > wait up to two minutes to write out data, leading to lots

Truncation Data Loss

2009-11-10 Thread Nick Guenther
So, as nicely summarized at http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html, ext4 is kind of broken. It won't honor fsync and, as a /feature/, will wait up to two minutes to write out data, leading to lots of files emptied to the great bitbucket in the sky if the machi