From: Hans Reiser <reiser@namesys.com>
To: Paul Wagland <paul@wagland.net>
Cc: Linux mailing list SCSI <linux-scsi@vger.kernel.org>,
Linux mailing list kernel <linux-kernel@vger.kernel.org>,
Atul Mukker <atulm@lsil.com>
Subject: Re: reiser4 and megaraid problems with debian 2.6.5
Date: Wed, 14 Apr 2004 08:13:17 -0700 [thread overview]
Message-ID: <407D550D.5030003@namesys.com> (raw)
In-Reply-To: <36927C82-8DE0-11D8-A41D-000A95CD704C@wagland.net>
Paul Wagland wrote:
> Hi all,
>
> I would like to report on a problem that I am having. I am just
> testing out the new megaraid unified driver, and have been doing some
> baseline testing with bonnie++.
>
> My problem is that, although reiserfs, ext2, jfs and xfs all work,
> reiser4 fails with the following error:
> ---
> Can't write block.
> Bonnie: drastic I/O error (write(2)): No such file or directory
> ---
>
> I am using the debian prepared kernel with the debian reiser4 patch. I
> made a cursory examination of the patch, and it appears to correlate
> fairly closely with the patch from the namesys site.
In what way does it not correlate?
>
> Given that this works with reiserfs, ext2, jfs and xfs it would appear
> to be a reiser4 problem, however ext3 also fails, though with a
> different error, it claims that the disk is full, but it is trying to
> write a 2 1GB files onto a 2.5GB filesystem, so it should have enough
> room, and indeed it did even work two or three times out of about 10
> runs (lots of timing :-). This implies that it might be a megaraid
> problem. As you can tell, I really have no idea ;-)
>
> I will try playing around tonight with an official kernel and the
> official reiser4 patch to see if that makes any difference, but would
> just like to raise this potential problem sooner rather than later.
>
> If I can help debug this situation (I am probably the only person
> trying this combination :-) please let me know how I should go about it.
>
> Cheers,
> Paul
I don't have the hardware to test it, can you get the error without your
hardware?
--
Hans
next prev parent reply other threads:[~2004-04-14 15:12 UTC|newest]
Thread overview: 20+ 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 13:45 ` Vladimir Saveliev
2004-04-14 14:03 ` Paul Wagland
2004-04-14 23:59 ` Paul Wagland
2004-04-16 20:39 ` mjt
2004-04-17 7:38 ` Paul Wagland
2004-04-19 21:40 ` reiser4 and bonnie problems Paul Wagland
2004-04-20 7:51 ` Nikita Danilov
2004-04-20 8:54 ` Paul Wagland
2004-04-20 13:37 ` Nikita Danilov
2004-04-20 14:51 ` Alex Zarochentsev
2004-04-20 18:18 ` Paul Wagland
2004-04-21 7:03 ` Alex Zarochentsev
2004-04-18 22:36 ` reiser4 and megaraid problems with debian 2.6.5 (*solved*) Paul Wagland
2004-04-14 15:13 ` Hans Reiser [this message]
2004-04-14 15:37 ` reiser4 and megaraid problems with debian 2.6.5 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=407D550D.5030003@namesys.com \
--to=reiser@namesys.com \
--cc=atulm@lsil.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=paul@wagland.net \
/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.