All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Kirby <sim@netnation.com>
To: Michael Rubin <mrubin@google.com>
Cc: Jan Kara <jack@suse.cz>,
	Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
	Mike Snitzer <snitzer@gmail.com>,
	Andreas Dilger <adilger@sun.com>,
	linux-ext4@vger.kernel.org
Subject: Re: EXT3 way too happy with write errors
Date: Fri, 2 Jan 2009 18:15:16 -0800	[thread overview]
Message-ID: <20090103021516.GE9995@hostway.ca> (raw)
In-Reply-To: <532480950812181029k1baf8264y82fb6d9760fe05f8@mail.gmail.com>

> On Thu, Dec 18, 2008 at 9:49 AM, Simon Kirby <sim@netnation.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-

  reply	other threads:[~2009-01-03  2:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15  0:22 EXT3 way too happy with write errors Simon Kirby
2008-12-18 17:07 ` Jan Kara
2008-12-18 17:18   ` Simon Kirby
2008-12-18 17:27     ` Jan Kara
2008-12-18 17:49       ` Simon Kirby
2008-12-18 18:29         ` Michael Rubin
2009-01-03  2:15           ` Simon Kirby [this message]
2009-01-03  2:45             ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090103021516.GE9995@hostway.ca \
    --to=sim@netnation.com \
    --cc=adilger@sun.com \
    --cc=hidehiro.kawai.ez@hitachi.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=mrubin@google.com \
    --cc=snitzer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.