From: Dirk Mueller <dmuell@gmx.net>
To: reiserfs-list@namesys.com
Subject: 2.4.19-pre7 / corruption on unwanted reboot
Date: Sat, 4 May 2002 23:11:47 +0200 [thread overview]
Message-ID: <20020504211147.GA20092@matrix.wg> (raw)
Hi,
I've seen HEAVY file corruption on unwanted reboots (like pressing the reset
button accidently) on reiserfs with this kernel on 3 machines now.
The symptom is that it finds a LOT of files to "unlink" on journal replay,
which I find suspicious as those machines are lightly loaded.
I didn't follow the development too closely the last few weeks, but I
believe that something turned worse in this respect lately.
Note that reiserfsck doesn't find any error in the file system structure
before and after the journal replay on reboot,
still many files (especially those that were not touched for several hours
before the reboot) contain complete garbage after the journal replay.
Dirk
next reply other threads:[~2002-05-04 21:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 21:11 Dirk Mueller [this message]
2002-05-05 2:07 ` 2.4.19-pre7 / corruption on unwanted reboot Chris Mason
2002-05-06 12:36 ` Dirk Mueller
2002-05-06 12:54 ` Chris Mason
2002-05-06 13:59 ` Dirk Mueller
2002-05-06 14:26 ` Chris Mason
2002-05-06 18:37 ` Dirk Mueller
2002-05-05 8:09 ` Oleg Drokin
2002-05-06 10:59 ` 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=20020504211147.GA20092@matrix.wg \
--to=dmuell@gmx.net \
--cc=reiserfs-list@namesys.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.