From: Oleg Drokin <green@namesys.com>
To: Dirk Mueller <dmuell@gmx.net>
Cc: reiserfs-list@namesys.com
Subject: Re: 2.4.19-pre7 / corruption on unwanted reboot
Date: Sun, 5 May 2002 12:09:03 +0400 [thread overview]
Message-ID: <20020505120903.A11812@namesys.com> (raw)
In-Reply-To: <20020504211147.GA20092@matrix.wg>
Hello!
On Sat, May 04, 2002 at 11:11:47PM +0200, Dirk Mueller wrote:
> I've seen HEAVY file corruption on unwanted reboots (like pressing the reset
> button accidently) on reiserfs with this kernel on 3 machines now.
This is bad. Does any earlier (but still relatively recent) kernel excibits
this same behavior?
> 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.
How much is this "a LOT"? I think that even 10+ files that are unlinked
after the unclean reboot/crash is pretty normal. Programs tend to use
deleted files after the deletion, so this number highly depends
on kind of programs you usually run.
> I didn't follow the development too closely the last few weeks, but I
> believe that something turned worse in this respect lately.
In fact nothing unexpected went into 2.4.19-pre7, that was not available in
our pending patches directory on our ftp site.
> 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.
I sthere any other pattern for damaged files besides these were not touched for
several hours prior to reboot?
Do their mtimes confirm they were modified long ago?
Thanks for the report.
Bye,
Oleg
next prev parent reply other threads:[~2002-05-05 8:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 21:11 2.4.19-pre7 / corruption on unwanted reboot Dirk Mueller
2002-05-05 2:07 ` 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 [this message]
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=20020505120903.A11812@namesys.com \
--to=green@namesys.com \
--cc=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.