All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chip Salzenberg <chip@valinux.com>
To: linux-mm@kvack.org
Subject: raid0 and buffers larger than PAGE_SIZE
Date: Wed, 7 Jun 2000 20:44:44 -0700	[thread overview]
Message-ID: <20000607204444.A453@perlsupport.com> (raw)

I'm using raid0 under 2.2.16pre4 and I've just started observing a new
failure mode that's completely preventing it from working: getblk(),
and therefore refill_freelist(), is being called with a size greater
than PAGE_SIZE.  This is triggered by e2fsck on the /dev/md0, and it's
probably been a while since the last e2fsck, so I don't know when the
was actually introduced.

I'm using an Intel CPU, so PAGE_SIZE is 4K, but getblk() is being
called with a size of 16K, which is (not coincidentally) my raid0
chunk size.  It ends up in an infinite loop, as getblk() calls
refill_freelist() forever until it succeeds, which it never does!

I'm not sure whether the bug is in raid0 (is setting a block device
block size greater than PAGE_SIZE legal?), refill_freelist (is
creating buffer heads that span multiple pages legal?), or something
else entirely....  Help?!

Clues, anyone?
-- 
Chip Salzenberg              - a.k.a. -              <chip@valinux.com>
"I wanted to play hopscotch with the impenetrable mystery of existence,
    but he stepped in a wormhole and had to go in early."  // MST3K
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/

             reply	other threads:[~2000-06-08  3:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-08  3:44 Chip Salzenberg [this message]
2000-06-08 14:08 ` raid0 and buffers larger than PAGE_SIZE Stephen C. Tweedie
2000-06-08 19:13   ` Chip Salzenberg
2000-06-08 19:24     ` Stephen C. Tweedie
2000-06-08 20:20   ` Chip Salzenberg

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=20000607204444.A453@perlsupport.com \
    --to=chip@valinux.com \
    --cc=linux-mm@kvack.org \
    /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.