linux-ext4 - Re: EXT3 way too happy with write errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090103021516.GE9995@hostway.ca>
Date:	Fri, 2 Jan 2009 18:15:16 -0800
From:	Simon Kirby <sim@...nation.com>
To:	Michael Rubin <mrubin@...gle.com>
Cc:	Jan Kara <jack@...e.cz>,
	Hidehiro Kawai <hidehiro.kawai.ez@...achi.com>,
	Mike Snitzer <snitzer@...il.com>,
	Andreas Dilger <adilger@....com>, linux-ext4@...r.kernel.org
Subject: Re: EXT3 way too happy with write errors

> On Thu, Dec 18, 2008 at 9:49 AM, Simon Kirby <sim@...nation.com> wrote:
> > Not aborting on data write error: User loses data.  File system gets very
> > confused.
> >
> > What am I missing?
> 
> I can think of certain situations when companies may care about
> getting most of the data to disk and clean it up later.
> Datacenters may be replicating the data to many spindles and may
> sometimes care about throughput as much as possible. So lossy data
> could be preferred to complete data.
> 
> Not saying this is always preferred but I can see a use case.

Ok, fine, in this case they might know what they are doing.  Still, this
is not reason enough to default the case in point... ?

:)

Simon-
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html