From: Szabolcs Illes <illes@cpc.wmin.ac.uk>
To: Alex Zarochentsev <zam@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 bug
Date: Tue, 01 Mar 2005 12:31:19 +0000 [thread overview]
Message-ID: <42246097.4000009@cpc.wmin.ac.uk> (raw)
In-Reply-To: <20050228144518.GK8161@backtop.namesys.com>
Alex Zarochentsev wrote:
>On Sun, Feb 27, 2005 at 07:34:11PM +0000, Szabolcs Illes wrote:
>
>
>>Hi All,
>>
>>I have been using reiser4fs for 4 months without any problem since
>>today. After tryinig to open a movie with mplayer a have this in my log:
>>
>>
>
>no other reiser4 messages in the log for 4 months?
>
I have checked my logs. I was not able to find anything from reiserfs.
But I have uploaded my syslog since feb 27 (this is when the bug occured):
http://nuk.teteny.elte.hu/~selli/syslog.1.bz2 ( 1.8 compressed, 300M
uncompresed )
It may has more information about the bug, you should check it. For
example the very first message from reiser4 is:
Feb 27 12:59:38 sunset kernel: WARNING: Wrong level found in node: 1 != 95
Feb 27 12:59:38 sunset kernel: reiser4[cupsd(3296)]: parse_node40
(fs/reiser4/plugin/node/node40.c:767)[nikita-494]:
> like delimitingkey
>mismatch reports?
>
>there was wrong bitmap checksum. actually I haven't seen such reports until
>now. are you sure your computer's disk/ram work well?
>
>
My machine (seems to be) is fun, I have run some tests.
Another info:
I was using an extrenal usb2 disk (120Gb/ reiser4) when this affair
occurd. After rebooting I had to repair all my reiser4 partitions. ( /
hda2, /home hda5/, /mnt/Movies sda1).
For the "/" I had to use --build-sb, then --build-fs, then --fix
For /home, and the external /mnt/Movies just the --build-sb
>
>
>>Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]:
>>write_sd_by_inode_common (fs/reiser4/plugin/object.c:480)[nikita-2221]:
>>Feb 27 14:00:22 sunset kernel: WARNING: Failed to save sd for 1599330: -5
>>Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: create_child_common
>>(fs/reiser4/plugin/dir/dir.c:501)[nikita-2219]:
>>Feb 27 14:00:22 sunset kernel: WARNING: Failed to create sd for 1599330
>>Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40
>>(fs/reiser4/plugin/node/node40.c:767)[nikita-494]:
>>Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95
>>Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40
>>(fs/reiser4/plugin/node/node40.c:767)[nikita-494]:
>>Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95
>>Feb 27 14:00:24 sunset kernel: reiser4[cupsd(3296)]: parse_node40
>>(fs/reiser4/plugin/node/node40.c:767)[nikita-494]:
>>Feb 27 14:00:24 sunset kernel: WARNING: Wrong level found in node: 1 != 95
>>......
>>1000x times
>>
>>
>
>were there unclear reboots?
>
I had some crash ( I think it was because of my bug ethernet driver, I
have no crash since I replaced it)
> That shouldn't be a problem unless disk write
>caching is disabled.
>
>
How can I chech this?
Szabolcs
>
>
>>After trying to reboot:
>>
>>http://nuk.teteny.elte.hu/~selli/dscf0437.jpg (using 2.6.9-cko3)
>>http://nuk.teteny.elte.hu/~selli/dscf0438.jpg
>>http://nuk.teteny.elte.hu/~selli/dscf0439.jpg
>>
>>I had to install a new root filesystem, and using that I was able to fix
>>the filesystem. ( --build-sb, build-fs, and fix )
>>I have lost some file but fortunatly I was able to use my system again.
>>
>>The affair happend when I was using 2.6.10 with reiser4 patch(from
>>namesys.com). I tried to reboot with my previos kernel (2.6.9-cko3) but
>>had the some bug (see screenshots). Sorry but I forgot to save the
>>outout of the fsck prog :(.
>>
>>If U need any information do not hesitate contacting me.( I am not on
>>the mailing list)
>>
>>Some info in advanve:
>>Hardware: Dell Inpiron 8600c (1600Mhz Centrion processor)
>>
>>Kernel config:
>>
>>
>[...]
>
>
>
next prev parent reply other threads:[~2005-03-01 12:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 19:34 reiser4 bug Szabolcs Illes
2005-02-28 14:45 ` Alex Zarochentsev
2005-03-01 12:31 ` Szabolcs Illes [this message]
2005-03-04 13:48 ` Alex Zarochentsev
2005-03-04 14:38 ` Szabolcs Illes
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 8:58 Matt Eaton
2006-04-11 5:28 Matt Eaton
2006-04-11 5:54 ` Alexander Zarochentsev
2006-04-11 8:27 ` Michael Weissenbacher
2006-04-11 8:54 ` Avuton Olrich
2006-04-11 12:22 ` Alexander Zarochentsev
2006-04-11 6:35 ` Jake Maciejewski
2006-03-28 16:16 Reiser4 bug Alexander Gran
2006-03-28 16:37 ` Alexander Gran
2005-11-30 10:40 reiser4 bug Thomas Kuther
2004-09-05 14:25 Scheduler experiences Markus Törnqvist
2004-09-05 15:55 ` Scheduler experiences (with Reiser4 bug report) mjt
2004-09-05 16:07 ` Reiser4 bug mjt
2004-09-05 16:07 ` Markus Törnqvist
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=42246097.4000009@cpc.wmin.ac.uk \
--to=illes@cpc.wmin.ac.uk \
--cc=reiserfs-list@namesys.com \
--cc=zam@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.