linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: lists@xunil.at
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID5 reshape problems : SOLVED
Date: Fri, 27 Mar 2009 19:11:18 +0100	[thread overview]
Message-ID: <49CD16C6.301@xunil.at> (raw)
In-Reply-To: <49CB56F0.9030902@xunil.at>

Stefan G. Weichinger schrieb:
> I will wait until it isn't degraded anymore before I do the "pvresize".

Just for the records (maybe I need to google this myself someday ;) ):

The whole process finished this afternoon, with all 6 disks in the
raid5. The following pvresize worked without a problem as well.

So everything is fine again, it really seems that dust was the main
problem here ...

Thanks, Stefan

      reply	other threads:[~2009-03-27 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-25 18:31 RAID5 reshape problems Stefan G. Weichinger
2009-03-25 20:11 ` Stefan G. Weichinger
2009-03-25 22:13 ` Neil Brown
2009-03-25 22:43   ` Stefan G. Weichinger
2009-03-26  6:58     ` Stefan G. Weichinger
2009-03-26 10:20       ` Stefan G. Weichinger
2009-03-27 18:11         ` Stefan G. Weichinger [this message]

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=49CD16C6.301@xunil.at \
    --to=lists@xunil.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).