From: Jesper Juhl <jesper.juhl@gmail.com>
To: Redeeman <redeeman@metanurb.dk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hans Reiser <reiser@namesys.com>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: 2.6.18-rc3 - ReiserFS - warning: vs-8115: get_num_ver: not directory or indirect item
Date: Sun, 30 Jul 2006 16:53:43 +0200 [thread overview]
Message-ID: <200607301653.43919.jesper.juhl@gmail.com> (raw)
In-Reply-To: <1154266306.13635.28.camel@localhost>
On Sunday 30 July 2006 15:31, Redeeman wrote:
> On Sun, 2006-07-30 at 15:08 +0200, Jesper Juhl wrote:
> > I just got a warning message with 2.6.18-rc3 that I've never seen before :
> >
> > ReiserFS: sda4: warning: vs-8115: get_num_ver: not directory or indirect item
> >
> > The message showed up twice in dmesg during two parallel "make -j3"
> > builds of the 2.6.18-rc3 kernel source in two sepperate directories.
> > I've tried to reproduce it but without luck.
> >
> > It would be nice if someone could tell me what the message means and
> > wether or not I should be worried about it.
> by default i would suggest worried mode.
>
> what does fsck.reiserfs say?
> >
nothing much :
root@dragon:~# fsck.reiserfs /dev/sda4
reiserfsck 3.6.19 (2003 www.namesys.com)
*************************************************************
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************
Will read-only check consistency of the filesystem on /dev/sda4
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Sun Jul 30 16:03:39 2006
###########
Replaying journal..
Reiserfs journal '/dev/sda4' in blocks [18..8211]: 0 transactions replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 139587
Internal nodes 937
Directories 33870
Other files 516740
Data block pointers 3875183 (1397 of them are zero)
Safe links 0
###########
reiserfsck finished at Sun Jul 30 16:18:47 2006
###########
root@dragon:~#
--
Jesper Juhl <jesper.juhl@gmail.com>
next prev parent reply other threads:[~2006-07-30 14:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 13:08 2.6.18-rc3 - ReiserFS - warning: vs-8115: get_num_ver: not directory or indirect item Jesper Juhl
2006-07-30 13:31 ` Redeeman
2006-07-30 14:53 ` Jesper Juhl [this message]
2006-07-30 17:28 ` Andi Kleen
2006-07-30 17:39 ` Jesper Juhl
2006-07-30 20:37 ` Philippe Gramoullé
2006-07-31 19:02 ` Vladimir V. Saveliev
2006-07-30 18:22 ` Jan Engelhardt
2006-08-03 19:11 ` Josef Sipek
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=200607301653.43919.jesper.juhl@gmail.com \
--to=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=redeeman@metanurb.dk \
--cc=reiser@namesys.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.