public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Wagland <paul@wagland.net>
To: Nikita Danilov <Nikita@Namesys.COM>
Cc: reiserfs-list@Namesys.COM,
	Linux SCSI mailing list <linux-scsi@vger.kernel.org>,
	Atul Mukker <atulm@lsil.com>, Domenico Andreoli <cavok@libero.it>,
	Hans Reiser <reiser@Namesys.COM>,
	Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: reiser4 and megaraid problems with debian 2.6.5 (*solved*)
Date: Mon, 19 Apr 2004 00:36:16 +0200	[thread overview]
Message-ID: <1082327775.2003.5.camel@morsel.kungfoocoder.org> (raw)
In-Reply-To: <1081987184.11193.87.camel@morsel.kungfoocoder.org>

[-- Attachment #1: Type: text/plain, Size: 892 bytes --]

Hi all,

well partly solved anyway... I am just posting this so that if anyone
finds this thread later they can also find this conclusion... There is
still more work to be done before this problem can be properly closed,
but at least now I am certain that it has nothing to do with the
hardware :-)

It appears (my own unsupported theory) that the problem is that reiser4
is taking some time to free up the free blocks that are currently in use
by the wandering log. Since I was running a test that causes a lot of
wandering log to be created, and I was doing it on a filesystem with
very little free space, then I was running into the problem.

Rerunning the test with either a) more space, or b) a smaller data set
solved the problem. On the reiserfs-list we are now trying to find out
exactly why this is happening, and how to solve the problem properly.

Cheers,
Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-18 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14  6:51 reiser4 and megaraid problems with debian 2.6.5 Paul Wagland
2004-04-14  9:05 ` Domenico Andreoli
2004-04-14 12:36   ` Paul Wagland
2004-04-14 13:09     ` Nikita Danilov
2004-04-14 13:25       ` Paul Wagland
2004-04-14 23:59         ` Paul Wagland
2004-04-18 22:36           ` Paul Wagland [this message]
2004-04-14 15:13 ` Hans Reiser
2004-04-14 15:37   ` Paul Wagland

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=1082327775.2003.5.camel@morsel.kungfoocoder.org \
    --to=paul@wagland.net \
    --cc=Nikita@Namesys.COM \
    --cc=atulm@lsil.com \
    --cc=cavok@libero.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox