From: Alex Riesen <riesen@synopsys.com>
To: Oleg Drokin <green@namesys.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [reiserfs-dev] 2.5.4-pre1: zero-filled files resiserfs
Date: Thu, 7 Feb 2002 23:02:35 +0100 [thread overview]
Message-ID: <20020207230235.A173@steel> (raw)
In-Reply-To: <20020207082348.A26413@riesen-pc.gr05.synopsys.com> <20020207104420.A6824@namesys.com>
In-Reply-To: <20020207104420.A6824@namesys.com>
Hi,
tried the patch. The problem looks gone, although i've placed
the system under even some more load than before (8.9, maybe not
impressive but first time for this one).
The reiserfsck showed up some nasty looking errors:
shrink_id_map: objectid map shrinked: used 4096, 5 blocks
grow_id_map: objectid map expanded: used 5120, 5 blocks
grow_id_map: objectid map expanded: used 10240, 10 blocks
bad_leaf: block 211482 has wrong order of items
...more of that...
free block count 1326452 mismatches with a correct one 1326458.
on-disk bitmap does not match to the correct one. 1 bytes differ
"reiserfsck --rebuild-tree" cured them without visible damages for now.
There were some messages about deleted blocks, expanded objectid map,
shrinked map and one "dir 1 2 has wrong sd_size 120, has to be 152".
I can send you logs, if needed.
Does the 2.5.4-pre2 contains this patch ?
-alex
On Thu, Feb 07, 2002 at 10:44:20AM +0300, Oleg Drokin wrote:
> Hello!
>
> On Thu, Feb 07, 2002 at 08:23:48AM +0100, Alex Riesen wrote:
>
>> There were no crashes or suspicious messages on the console.
>> Nothing special in logs, and sorry, reiserfs self-debugging
>> wasn't enabled.
> Can you try the patch attached? It may not fix the thing, but
> we want to be sure (and we'll try to reproduce locally atthe same time).
> Also try to run reiserfsck --check on your reiserfs partitions.
>
> Bye,
> Oleg
> --- linux-2.5.4-pre1/fs/reiserfs/inode.c.orig Wed Feb 6 11:18:35 2002
> +++ linux-2.5.4-pre1/fs/reiserfs/inode.c Wed Feb 6 11:12:08 2002
...
next prev parent reply other threads:[~2002-02-07 22:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 7:23 2.5.4-pre1: zero-filled files resiserfs Alex Riesen
2002-02-07 7:44 ` [reiserfs-dev] " Oleg Drokin
2002-02-07 22:02 ` Alex Riesen [this message]
2002-02-08 5:51 ` Oleg Drokin
2002-02-08 6:34 ` Oleg Drokin
2002-02-08 22:07 ` [reiserfs-dev] 2.5.4-pre1: zero-filled files reiserfs Alex Riesen
2002-02-11 5:51 ` Oleg Drokin
[not found] ` <Pine.LNX.4.44.0202111247270.21009-100000@Expansa.sns.it>
2002-02-11 12:17 ` Alex Riesen
2002-02-11 13:09 ` Oleg Drokin
[not found] ` <20020211141422.A16832@steel>
[not found] ` <20020211162743.A1282@namesys.com>
2002-02-11 14:03 ` Alex Riesen
2002-02-11 14:23 ` Luigi Genoni
2002-02-11 14:27 ` Oleg Drokin
2002-02-11 19:19 ` Luigi Genoni
2002-02-12 16:55 ` Luigi Genoni
2002-02-12 17:01 ` Oleg Drokin
2002-02-12 17:13 ` Luigi Genoni
2002-02-13 5:56 ` Oleg Drokin
2002-02-13 11:11 ` Luigi Genoni
2002-02-13 13:08 ` Oleg Drokin
2002-02-13 17:15 ` Luigi Genoni
2002-02-14 5:50 ` Oleg Drokin
2002-02-14 9:57 ` reiserfs oops with 2.5.5-pre1 (was: [reiserfs-dev] 2.5.4-pre1:)zero-filled " Luigi Genoni
2002-02-14 10:01 ` Oleg Drokin
2002-02-13 20:01 ` [reiserfs-dev] 2.5.4-pre1: zero-filled " Alex Riesen
2002-02-14 5:46 ` Oleg Drokin
2002-02-12 19:33 ` Alex Riesen
2002-02-11 14:20 ` Luigi Genoni
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=20020207230235.A173@steel \
--to=riesen@synopsys.com \
--cc=fork0@users.sourceforge.net \
--cc=green@namesys.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