From: Helge Hafting <helge.hafting@broadpark.no>
To: akpm@zip.com.au, davej@suse.de
Cc: Helge Hafting <helgehaf@aitel.hist.no>,
linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au
Subject: Re: [Fwd: Re: 2.5.24-dj1,smp,ext2,raid0: I got random zero blocks in my files.]
Date: Mon, 01 Jul 2002 21:50:51 +0200 [thread overview]
Message-ID: <3D20B29B.ED186C3B@broadpark.no> (raw)
In-Reply-To: 3D20539F.C7D7A4C4@aitel.hist.no
Helge Hafting wrote:
>
> -------- Original Message --------
> Subject: Re: 2.5.24-dj1,smp,ext2,raid0: I got random zero blocks in my
> files.
> Date: Mon, 01 Jul 2002 01:18:20 -0700
> From: Andrew Morton <akpm@zip.com.au>
> To: Helge Hafting <helgehaf@aitel.hist.no>
> CC: linux-kernel@vger.kernel.org, neilb@cse.unsw.edu.au,davej@suse.de
> References: <3D200BF6.3A6D9B59@aitel.hist.no>
>
> Helge Hafting wrote:
> >
> > 2.5.24-dj1 gave me files with zeroed blocks inside.
[...]
> > The filesystems use 4k blocks.
> > I haven't seen any trouble on non-raid or raid-1
> > partitions.
>
> Yes, the large BIO stuff went into 2.5.19. RAID0 doesn't
> like those big BIOs. Jens is cooking up a fix for that.
>
> Just to confirm that this is the problem, could you please
> set MPAGE_BIO_MAX_SIZE in 32768 in fs/mpage.c and see if the
> failure goes away?
I tried that, and it didn't help. Could this be as simple
as non-aligned 32k requests? A size limit might not be
enough if the request starts in the middle of one stripe
extending into the next?
I got lots of these,
monster kernel: raid0_make_request bug: can't convert block across
chunks or bigger than 32k 2944376 32
and untarred files with strings of zeroes in them. One
file had several sets of zeroes.
Helge Hafting
next parent reply other threads:[~2002-07-01 19:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D20539F.C7D7A4C4@aitel.hist.no>
2002-07-01 19:50 ` Helge Hafting [this message]
2002-07-01 20:51 ` [Fwd: Re: 2.5.24-dj1,smp,ext2,raid0: I got random zero blocks in my files.] Andrew Morton
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=3D20B29B.ED186C3B@broadpark.no \
--to=helge.hafting@broadpark.no \
--cc=akpm@zip.com.au \
--cc=davej@suse.de \
--cc=helgehaf@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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