All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>
Cc: ReiserFS <reiserfs-list@namesys.com>
Subject: Re: ReiserFS is not suitable for a root FS.
Date: Mon, 19 May 2003 14:31:23 +0400	[thread overview]
Message-ID: <20030519103123.GA1122@namesys.com> (raw)
In-Reply-To: <3EC8B061.6050300@gmx.net>

Hello!

On Mon, May 19, 2003 at 12:22:25PM +0200, Carl-Daniel Hailfinger wrote:

> > BTW, were there any news on "reiserfs corruptions on crypto loop mounted devices" tests with 2.4.21-rc2?
> Unfortunately, I wasn't successful in reproducing the corruption. OTOH,
> I now use reiserfsprogs 3.6.7 instead of 3.6.4 before. Were there any
> fixes committed to resize_reiserfs in the meantime?

I do not see anything important, just some minor journal opening stuff.

> What strikes me as odd is the fact that vs-5150 errors seem to coincide
> with resizing when you look at past messages to the list.

Yes, this is strange.

> Do your data structures grow linearly or to next 2^n bytes with
> filesystem size? The last resize operations I tried did not cross any
> 2^n bytes boundary, while the ones before corruption crossed 512 MB,
> 1024 MB, 2048 MB boundary respectively.

No, the resize process only adds one more bitmap for every ~128M of disk space

> Another shot in the dark: maybe resize_reiserfs does not update/check
> the node level correctly, i.e. it checks against correct values before
> resize instead of after resize?

When you grow the filesystem, no tree nodes are touched at all.
Only size in superblock is updated and new bitmaps are added.

Bye,
    Oleg

  reply	other threads:[~2003-05-19 10:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-17 10:30 ReiserFS is not suitable for a root FS Russell Coker
2003-05-17 10:56 ` Oleg Drokin
2003-05-17 11:09   ` Russell Coker
2003-05-17 11:24     ` Oleg Drokin
2003-05-17 11:32       ` Russell Coker
2003-05-17 11:40         ` Oleg Drokin
2003-05-17 11:14 ` Carl-Daniel Hailfinger
2003-05-17 11:25   ` Russell Coker
2003-05-17 12:01     ` Carl-Daniel Hailfinger
2003-05-17 12:10       ` Oleg Drokin
2003-05-19 10:22         ` Carl-Daniel Hailfinger
2003-05-19 10:31           ` Oleg Drokin [this message]
2003-05-21 22:09         ` Newsmail
2003-09-18 11:50         ` Carl-Daniel Hailfinger
2003-09-18 14:05           ` Vitaly Fertman
2003-05-17 12:40       ` Russell Coker
2003-05-19 19:55 ` bscott
2003-05-19 20:42   ` Dieter Nützel

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=20030519103123.GA1122@namesys.com \
    --to=green@namesys.com \
    --cc=c-d.hailfinger.kernel.2003@gmx.net \
    --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.