mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Clemens Eisserer <linuxhippy@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Howto switch off ext4's delayed allocation?
Date: Wed, 16 Sep 2009 08:32:12 -0400	[thread overview]
Message-ID: <194f62550909160532q248cb45coee639a2da10292a@mail.gmail.com> (raw)
In-Reply-To: <194f62550909090403x16e61cc1g3a23593085de0b@mail.gmail.com>

Hi,

Just happend again to me.
After the intel driver crashed my system, the source-file I was
working on was empty. Fourtunatly eclipse has a history-log.

Isn't there a way to switch off the more "dangerous" optimizations in ext4?
I already searched howto do this, but from what I've seen there was
only discussion about providing a switch for disabling delayed
allocation, but it was never done?

Thanks, Clemens

2009/9/9 Clemens Eisserer <linuxhippy@gmail.com>:
> Hi,
>
> Every since switching to ext4, I suffer fromt he empty files problem
> after crashes.
> Since GEM/KMS was included, as well as the changes to the usb-serial
> subsystem I experience crashes from time to time.
>
> As far as I understand this is caused by delayed allocation.
> I really enjoy the performance benefits of ext4, and I know
> applications should be fixed - but having this problem seen with so
> many apps I doubt it will ever happen. (Kwrite, bash itself, umtsmon,
> ...).
>
> Is there any way to disable delayed allocation? (running 2.6.31rc8)
>
> Thank you in advance, Clemens
>

  reply	other threads:[~2009-09-16 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-09 11:03 Clemens Eisserer
2009-09-16 12:32 ` Clemens Eisserer [this message]
2009-09-16 16:38   ` Theodore Tso
2009-09-16 18:41     ` Clemens Eisserer
2009-09-17 13:34       ` Theodore Tso
2009-09-17 18:37         ` Clemens Eisserer
2009-09-16 13:29 Tomasz Chmielewski

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=194f62550909160532q248cb45coee639a2da10292a@mail.gmail.com \
    --to=linuxhippy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®