From: "Kaj-Michael Lang" <milang@tal.org>
To: linux-lvm@sistina.com
Cc: linux-raid@vger.kernel.org
Subject: Re: [linux-lvm] Raid5 sync problem
Date: Fri, 25 May 2001 13:55:52 +0300 [thread overview]
Message-ID: <001501c0e509$45251b60$56dc10c3@tal.org> (raw)
In-Reply-To: Pine.LNX.4.33.0105241145560.1276-100000@UberGeek.coremetrics.com
> You are running off of parity. Until you get that drive fixed, it will
> hurt.
>
I *think* I've found out what happened (not sure, not tested), fsck was
trying to scan all of the LVs on the same raid5 at the same time. And as the
raid5 code had to calculate everything and trying to sync in the
background... instant high load. But I'm not sure.. and I really don't wan't
to test it..
Could that be it ?
next prev parent reply other threads:[~2001-05-25 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-24 11:24 [linux-lvm] Raid5 sync problem Kaj-Michael Lang
2001-05-24 16:46 ` Austin Gonyou
2001-05-25 10:55 ` Kaj-Michael Lang [this message]
2001-05-25 19:46 ` Andreas Dilger
2001-05-25 22:36 ` [linux-lvm] lvm_chr_ioctl Justin Booth
2001-05-25 23:00 ` Joe Harvell
2001-05-24 17:04 ` [linux-lvm] Raid5 sync problem Andreas Dilger
2001-05-24 18:28 ` Austin Gonyou
2001-05-24 20:00 ` Jos� Luis Domingo L�pez
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='001501c0e509$45251b60$56dc10c3@tal.org' \
--to=milang@tal.org \
--cc=linux-lvm@sistina.com \
--cc=linux-raid@vger.kernel.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.