From: Vitaly Fertman <vitaly@namesys.com>
To: Alex Zarochentsev <zam@namesys.com>,
Sebastian Kaps <seb-keyword-reiserfs.0462a0@toyland.sauerland.de>
Cc: reiserfs-list@namesys.com
Subject: Re: Linux 2.4 -> 2.6 migration
Date: Sat, 8 Nov 2003 14:09:50 +0300 [thread overview]
Message-ID: <200311081409.50425.vitaly@namesys.com> (raw)
In-Reply-To: <20031108101133.GS11516@backtop.namesys.com>
On Saturday 08 November 2003 13:11, Alex Zarochentsev wrote:
> On Fri, Nov 07, 2003 at 02:39:06PM +0100, Sebastian Kaps wrote:
> > Hi!
> >
> > Is there something concerning ReiserFS I should know when migrating from
> > Linux 2.4 to Linux 2.6?
> >
> > I'm asking because a few days ago I downloaded and compiled 2.6.0-test9
> > just for curiosity. It booted fine and I went back to my "standard"
> > kernel, which was 2.4.23-pre5 at that time. Right after booting the
> > 2.4.x kernel, I got lots of the following messages in my logs:
> > ,----
> >
> > | kernel: ide2(33,3):vs-4080: reiserfs_free_block: free_block
> > | (2103:463529)[dev:blocknr]: bit already cleared
>
> test-9/reiser3 works fine for us. Your problems could be due to a bug in
> updated IDE driver, for example. Do other filesystems (like ext2) work?
>
> Can you send a .config (from 2.6.0-test-9) and describe your hardware
> configuration to the reiserfs-dev@namesys.com mailing list?
>
> > `----
> > The block number always differed. Gladly, "reiserfsck --rebuild-tree"
> > helped to cure that, but there were lots of unusable files after that
> > (e.g. parts of files overwritten with parts of other files).
>
> I think that reiserfsck --rebuild-tree trusts the bitmap content, which is
> not good for your case. Vitaly will answer better.
Bitmaps do not say that this block belongs to some particular file,
so bitmaps have nothing to do with the described problem when
parts of files overwritten with parts of other files. But when there
are some blocks in use that have been already freed there could
be another problem -- parts of files are lost, there are just zeroes
in these parts, or some files are lost after fsck. Probably scanning
through all blocks of the partition with --scan-whole-partition
option would help here, but this option should be used with
extreme caution as you can run out of the partition space with it.
--
Thanks,
Vitaly Fertman
next prev parent reply other threads:[~2003-11-08 11:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 13:39 Linux 2.4 -> 2.6 migration Sebastian Kaps
2003-11-07 15:29 ` Eric Whiting
[not found] ` <3FABA80A.1090608@gmx.net>
2003-11-07 16:30 ` Sebastian Kaps
2003-11-07 17:10 ` Vince
2003-11-08 4:08 ` Quinn Harris
[not found] ` <20031107160935.3f02f334.pegasus@nerv.eu.org>
2003-11-07 16:33 ` Sebastian Kaps
2003-11-08 7:09 ` Soeren Sonnenburg
2003-11-08 10:11 ` Alex Zarochentsev
2003-11-08 11:09 ` Vitaly Fertman [this message]
2003-11-08 12:40 ` Sebastian Kaps
2003-11-08 12:21 ` Matthias Andree
[not found] ` <200311072107.50957.>
2003-11-08 12:32 ` Sebastian Kaps
2003-11-09 5:45 ` Alejandro Sanchez Acosta
2003-11-08 17:05 ` Marcelo Pacheco
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=200311081409.50425.vitaly@namesys.com \
--to=vitaly@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=seb-keyword-reiserfs.0462a0@toyland.sauerland.de \
--cc=zam@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.