From: Oleg Drokin <green@namesys.com>
To: Sebastian Dr?ge <sebastian.droege@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Next "Problem" with ReiserFS: vs-825: reiserfs_get_block: [799572 866493 0x3001 UNKNOWN] should not be found
Date: Fri, 8 Feb 2002 09:43:01 +0300 [thread overview]
Message-ID: <20020208094301.A7197@namesys.com> (raw)
In-Reply-To: <20020207140745.52eebb57.sebastian.droege@gmx.de>
In-Reply-To: <20020207140745.52eebb57.sebastian.droege@gmx.de>
Hello!
On Thu, Feb 07, 2002 at 02:07:45PM +0100, Sebastian Dr?ge wrote:
> I'm currently running 2.5.3-dj3 with the "fix for inodes with wrong item versions" and got the following errors in dmesg:
> vs-825: reiserfs_get_block: [283508 198 0x19001 UNKNOWN] should not be found
> [many times]
> and after a while:
> vs-825: reiserfs_get_block: [799572 866493 0x3001 UNKNOWN] should not be found
> [many times]
This is very strange in fact.
What do you do to get these messages?
> What does this mean?
It means that when we are trying to insert a new block in list of file's blocks
(to fill a hole or something) we encountering that somebody have inserted
the block while we were doing other things.
This was the case with truncating file past its end and then mmap-writing there.
But this particular place was fixed by introducing "expanding truncate" patch.
And please CC reiserfs specific bugreports to reiserfs-list@namesys.com
Thank you.
Bye,
Oleg
prev parent reply other threads:[~2002-02-08 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 13:07 Next "Problem" with ReiserFS: vs-825: reiserfs_get_block: [799572 866493 0x3001 UNKNOWN] should not be found Sebastian Dröge
2002-02-08 6:43 ` Oleg Drokin [this message]
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=20020208094301.A7197@namesys.com \
--to=green@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.droege@gmx.de \
/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