From: "Konstantin Münning" <konstantin@muenning.com>
To: reiserfs-list@namesys.com
Cc: Vitaly Fertman <vitaly@namesys.com>
Subject: Re: Strange problems/bugs with reiserfs and reiserfschk
Date: Tue, 23 Aug 2005 23:30:38 +0200 [thread overview]
Message-ID: <430B957E.4020004@muenning.com> (raw)
In-Reply-To: <200508151720.09411.vitaly@namesys.com>
Hi Vitaly!
Thank you for the reiserfsck 3.9.20. It in fact had different results on
that drive. I had it run in gdb (as I did with 3.6.19 to see what/where
the trouble may be) and the result is:
(***snip***)
vpf-10680: The file [641222 641239] has the wrong block count in the
StatData (1528) - corrected to (1520)
vpf-10680: The file [641222 641241] has the wrong block count in the
StatData (47192) - corrected to (47168)
vpf-10680: The file [641222 641242] has the wrong block count in the
StatData (16624) - corrected to (16528)
are_file_items_correct: All bytes we look for must be first items byte
(position 0).
Program received signal SIGABRT, Aborted.
0xffffe410 in __kernel_vsyscall ()
(***snip***)
Hmm... Ugly ;-).
Vitaly Fertman wrote:
> if some file item offsets are corrupted, fsck can work for too long on
> pass2. or it also can be a bug. I will send you a version of reiserfsprogs
> that has an optimization fix for former. if it fails email me and provide
> the metadata please:
> debugreiserfs -p <device> | bzip2 -c > <device>.bz2
Do you need the metadata or the full logfile or should I send you
something more/else for that?
Thanks and have a nice day,
Konstantin
next prev parent reply other threads:[~2005-08-23 21:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 22:02 Strange problems/bugs with reiserfs and reiserfschk Konstantin Münning
2005-08-08 13:18 ` Vitaly Fertman
[not found] ` <b14e81f0050807152830555213@mail.gmail.com>
2005-08-08 11:51 ` Konstantin Münning
2005-08-13 12:36 ` Konstantin Münning
2005-08-15 13:20 ` Vitaly Fertman
2005-08-23 21:30 ` Konstantin Münning [this message]
2005-08-24 10:47 ` Vitaly Fertman
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=430B957E.4020004@muenning.com \
--to=konstantin@muenning.com \
--cc=reiserfs-list@namesys.com \
--cc=vitaly@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.