From: Sebastian Hyrwall <sh@keff.org>
To: reiserfs-devel@vger.kernel.org
Subject: Negative blocks in rebuild-tree
Date: Sat, 08 Jan 2011 14:31:54 +0100 [thread overview]
Message-ID: <4D28674A.60603@keff.org> (raw)
Hi
I am getting a negative block-number with reiserfsck when doing
--rebuild-tree -S (or without -S). This causes a segmentation fault
later (pass 2) in the check because it tries to read a "non-existant
block". My rebuild takes 3 days and i didn't copy the stdout-info the
first time so I will post some more info as soon as it becomes available.
Pass 0:
####### Pass 0 #######
The whole partition (-710934672 blocks) is to be scanned
Skipping 117586 blocks (super block, journal, bitmaps) -711052258 blocks
will be read
Does anyone have any idea on how to fix this?
On a 64-bit system.
Sincerely,
Sebastian H
next reply other threads:[~2011-01-08 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-08 13:31 Sebastian Hyrwall [this message]
2011-01-09 0:58 ` Negative blocks in rebuild-tree Edward Shishkin
2011-01-09 2:09 ` Sebastian Hyrwall
2011-01-09 21:40 ` Jeff Mahoney
2011-01-11 19:27 ` sh
2011-01-11 19:30 ` Jeff Mahoney
2011-01-11 19:35 ` sh
2011-01-11 19:42 ` sh
2011-01-11 19:52 ` Jeff Mahoney
2011-01-11 21:04 ` Jeff Mahoney
2011-01-12 9:37 ` Sebastian Hyrwall
2011-01-17 9:59 ` Sebastian Hyrwall
2011-01-18 22:50 ` Jeff Mahoney
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=4D28674A.60603@keff.org \
--to=sh@keff.org \
--cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).