From: Oleg Drokin <green@namesys.com>
To: "Sebastian DrЖge" <sebastian.droege@gmx.de>
Cc: reiserfs-list@namesys.com, linux-kernel@vger.kernel.org
Subject: Re: Reiserfs Corruption with 2.5.5-pre1
Date: Thu, 14 Feb 2002 19:26:33 +0300 [thread overview]
Message-ID: <20020214192633.A2311@namesys.com> (raw)
In-Reply-To: <20020214155716.3b810a91.sebastian.droege@gmx.de> <20020214180501.A1755@namesys.com> <20020214162232.5e59193b.sebastian.droege@gmx.de> <20020214172421.5d8ae63c.sebastian.droege@gmx.de>
In-Reply-To: <20020214172421.5d8ae63c.sebastian.droege@gmx.de>
Hello!
On Thu, Feb 14, 2002 at 05:24:21PM +0100, Sebastian DrЖge wrote:
> reiserfsck --check said I have to do --rebuild-tree because of critical corruption (many "bad_leaf: block xxxxx has wrong order of items")...
these are 2.5.3 signs.
> after that I booted into 2.4.17. Everything works okay.
> Then I booted 2.5.5-pre1 and the mysterious files are there again after starting GNOME. I've copied one file to another location but when I reboot into 2.4.17 the files and the copy are gone again...
But GNOME is working, right?
> If you need one or two file names or the content of them just ask (They begin with an "^")... then I'll handcopy them ;)
I have a better approach.
Just recreate them (by running GNOME in 2.5.5-pre1?) and then tar them up ;)
Send the ersulting tar file to me.
> The format of the partition is 3.6 and another partition with 3.5 format had no errors... Maybe this helps
So now problem only is that there are strange files after GNOME start, right?
Do these files disa[[ear after you quit GNOME?
> I could build 2.5.5-pre1 without your patch from the last mail but for this try I have build the kernel with it
I just found this patch is only needed on SMP ;)
Bye,
Oleg
next prev parent reply other threads:[~2002-02-14 16:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-14 14:57 Reiserfs Corruption with 2.5.5-pre1 Sebastian Dröge
2002-02-14 15:05 ` Oleg Drokin
2002-02-14 15:22 ` Sebastian Dröge
2002-02-14 16:24 ` Sebastian Dröge
2002-02-14 16:26 ` Oleg Drokin [this message]
2002-02-15 12:52 ` Sebastian Dröge
2002-02-15 12:54 ` Oleg Drokin
2002-02-16 15:04 ` Sebastian Dröge
2002-02-16 17:22 ` [reiserfs-list] " system_lists
[not found] ` <20020216162503.270ab9cc.sebastian.droege@gmx.de>
2002-02-18 6:03 ` Oleg Drokin
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=20020214192633.A2311@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=sebastian.droege@gmx.de \
/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