From: nobody@nowhere.invalid (Unknown)
To: reiserfs-list@namesys.com
Subject: Bug in reiserfsck 3.6.1-pre1
Date: Mon, 16 Sep 2002 02:56:55 +0200 [thread overview]
Message-ID: <20020916025655.E22362@noris.de> (raw)
Pass 2:
# reiserfsck --rebuild-tree -S /dev/md0
...
0%..rewrite_file: 2 items of file [97373 97385] moved to [97373 1591], 207
/sec
..20%....40%..vpf-10260: The file we are inserting the new item (89 280
0x120001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format
new) into has not StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (89 280 0x514001 IND
(1), len 4048, location 48 entry count 0, fsck need 0, format new) into
has not StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (89 280 0x908001 IND
(1), len 4048, location 48 entry count 0, fsck need 0, format new) into
has not StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2035 3072665 0x10b001
IND (1), len 1060, location 3036 entry count 0, fsck need 0, format new)
into has not StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2035 3072665 0x10b001
IND (1), len 1060, location 3036 entry count 0, fsck need 0, format new)
into has not StatData, insertion was skipped
ufile.c 171 delete_N_items_after_key
delete_N_items_after_key: No directory item of [32340 32341] are expected
Aborted
I needed the rebuid because I had a multiple RAID disk death.
I restarted the check; if it dies again I'll append a core dump.
--
Matthias Urlichs | noris network AG | http://smurf.noris.de/
next reply other threads:[~2002-09-16 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-16 0:56 Unknown [this message]
2002-09-16 1:31 ` Bug in reiserfsck 3.6.1-pre1 Manuel Krause
2002-09-16 3:09 ` Matthias Urlichs
2002-09-16 5:19 ` Oleg Drokin
2002-09-16 7:35 ` Matthias Urlichs
2002-09-16 7:43 ` Oleg Drokin
2002-09-16 7:59 ` Matthias Urlichs
2002-09-16 8:05 ` Oleg Drokin
2002-09-16 8:13 ` Matthias Urlichs
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=20020916025655.E22362@noris.de \
--to=nobody@nowhere.invalid \
--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.