All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@namesys.com>
To: Newsmail <newsmail@satimex.tvnet.hu>
Cc: reiserfs-list@namesys.com
Subject: Re: old block allocator found in 2.4.19
Date: Fri, 24 Jan 2003 09:47:19 +0300	[thread overview]
Message-ID: <20030124094719.B5039@namesys.com> (raw)
In-Reply-To: <5.2.0.9.2.20030123232554.02004bd8@pop.tvnet.hu>

Hello!

On Thu, Jan 23, 2003 at 11:30:07PM +0100, Newsmail wrote:
> Hi Oleg, as you remember I mentioned you about my loop-aes+lvm+reiserfs 
> problem, that leaves hung processes after them, and only a cold reboot 

Yes. Unfortunatelly I only produced 2.4.20+crypto stuff kernel image and
now other more important bugs and problems divert me from looking at your
problem more, sorry.

> could save a solution. well these problems came (in my opinion) after the 
> introduction of the new block allocator in 2.4.20-preX. in the first 
> version the new block allocation wasnt the default one, we had to use some 
> preallocmin= etcetc flag in the mount process. well I would like to try 
> with a new 2.4.20 kernel the settings for the old allocator. is there a way 
> to use the old allocator with the new kernel? some mount option or any?

Well, you can specify "tails=large,alloc=old_way:concentrating_formatted_nodes=10".
This way it will resemble old block allocator pretty much.
Also you can remove the new block allocator patch from 2.4.20 (just apply it
(and later fixes) with -R patch option).
Also it would be interesting if your hangs go away if you apply
iput-deadlock fix: ftp://ftp.namesys.com/pub/reiserfs-for-2.4/2.4.20-pending/01-iput-deadlock-fix.diff

Thank you.

Bye,
    Oleg

      reply	other threads:[~2003-01-24  6:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 22:30 old block allocator found in 2.4.19 Newsmail
2003-01-24  6:47 ` 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=20030124094719.B5039@namesys.com \
    --to=green@namesys.com \
    --cc=newsmail@satimex.tvnet.hu \
    --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.