From: Con Kolivas <kernel@kolivas.org>
To: Gergely Tamas <dice@mfa.kfki.hu>, Keith Lea <keith@cs.oswego.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11 data loss
Date: Thu, 25 Dec 2003 09:34:17 +1100 [thread overview]
Message-ID: <200312250934.17913.kernel@kolivas.org> (raw)
In-Reply-To: <20031224222217.GA3408@mfa.kfki.hu>
Hello
On Thu, 25 Dec 2003 09:22, Gergely Tamas wrote:
> I've been hit by the same problem but using 2.6.0 . As you described,
> garbage in files (eg. /etc/modules.conf, ...).
>
> 2.6.0, Slackware 9.1
>
> > The corruption happened on two separate partitions on a single IDE
> > laptop drive, and both were ReiserFS 3.6 partitions. I don't know if
> > this is a kernel bug or a Reiser bug or something else, but I thought
>
> I don't think this is a reiserfs bug. This was my first thought and
> after first hitting this bug, I've moved all my partitions from reiserfs
> to jfs. But I've also had this problem with it... Now I'm back to
> 2.4.23, and everything works fine.
Because of the numerous reboots and hangs I've seen with experimental patches
I've also seen this, but it's not reiserFS fault. The problem is that most
drives have write caching enabled and not all of them are safe with this. If
you disable it with hdparm (hdparm -W 0 /dev/hd*) you'll find that open files
during a hard reset or power outage will prevent those open files from being
corrupted.
Con
next prev parent reply other threads:[~2003-12-24 22:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 21:59 2.6.0-test11 data loss Keith Lea
2003-12-24 22:22 ` Gergely Tamas
2003-12-24 22:34 ` Con Kolivas [this message]
2003-12-25 2:07 ` Eric D. Mudama
2003-12-25 5:17 ` Con Kolivas
2003-12-25 6:15 ` Hans Reiser
2003-12-25 16:46 ` Tomas Szepe
2003-12-25 23:45 ` Hmamouche, Youssef
2003-12-25 1:21 ` Felipe Alfaro Solana
2003-12-25 6:11 ` Hans Reiser
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=200312250934.17913.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=dice@mfa.kfki.hu \
--cc=keith@cs.oswego.edu \
--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