From: Vitaly Porotikov <vitaly.porotikov@nssmb.com>
To: reiserfs-list@namesys.com
Subject: Core dump in reiserfsck
Date: Wed, 15 Jan 2003 13:08:26 +0900 [thread overview]
Message-ID: <3E24DEBA.39AC1901@nssmb.com> (raw)
Folks,
Perhaps 3.x1c have not this bug, but I can't do any changes in my
system. I send it in hope to find some coding errors out (if this wasn't
before).
[root@tkprzbkup5 /root]# mount
/dev/rza1 on / type ext2 (rw)
none on /proc type proc (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/rze1 on /export type reiserfs (ro)
[root@tkprzbkup5 /root]# reiserfsck --check /dev/rze1
<-------------reiserfsck, 2002------------->
reiserfsprogs 3.x.1b
Will read-only check consistency of the filesystem on /dev/rze1
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes):Yes
###########
reiserfsck --check started at Wed Jan 15 10:41:40 2003
###########
Filesystem seems mounted read-only. Skipping journal replay..
Checking S+tree../ 72 (of 98)/101 (of 153)/124 (of
156)bad_indirect_item: block 1907661: item 7659550 76756x1 IND (1), len
8, location 3056 entry count 0, fsck need 0, format new has a pointer 0
to the block 1 whichin tree already
bad_indirect_item: block 1907661: item 7659550 7675670 0x1 IND (1), len
8, location 3056 entry count 0, fsckd 0, format new has a pointer 1 to
the block 500 which is in tree already
bit 2535358884, bitsize 314620004
reiserfsck: bitmap.c:160: reiserfs_bitmap_test_bit: Assertion
`bit_number < bm->bm_bit_size' failed.
Aborted (core dumped)
--
Best regards,
Vitaly
next reply other threads:[~2003-01-15 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-15 4:08 Vitaly Porotikov [this message]
2003-01-15 6:54 ` Core dump in reiserfsck Oleg Drokin
2003-01-15 10:16 ` Yury Umanets
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=3E24DEBA.39AC1901@nssmb.com \
--to=vitaly.porotikov@nssmb.com \
--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.