linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <roman@rm.pp.ru>
To: linux-raid@vger.kernel.org
Subject: Re: mdadm freezes the system
Date: Fri, 11 Jun 2010 00:43:16 +0600	[thread overview]
Message-ID: <20100611004316.7d8ad74d@natsu> (raw)
In-Reply-To: <20100608222434.3f0fb637@natsu>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

Hello.

To provide some updates on my earlier questions (for future generations
googling through the archives).

> So, my question is, does anyone have an idea on what could cause this, and
> what would be the best way to diagnose/fix the lockup problem?  Thanks in
> advance.

Since then I have re-created the original 3-device RAID5, it synced without
lockups. Perhaps I should write them off as some hardware bug, especially
considering that the nForce chipsets aren't exactly known as the gold standard
of bug-free design.

> So why the same RAID5 to RAID6 conversion started so differently in these two
> cases? And is it even possible to reshape RAID5 to RAID6 while simultaneously
> adding a disk, without overwriting all the other disks' contents (it surely
> looked like this is what was happening in the first case)?

Yes it is possible; I should have read about the --layout=preserve option in
the mdadm man page.

-- 
With respect,
Roman

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-10 18:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-08  8:59 mdadm freezes the system Roman Mamedov
2010-06-08 16:24 ` Roman Mamedov
2010-06-10 18:43   ` Roman Mamedov [this message]
2010-06-16  7:03     ` Michael Evans
2010-06-16  7:16       ` Roman Mamedov
2010-06-16 11:47         ` Billy Crook

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=20100611004316.7d8ad74d@natsu \
    --to=roman@rm.pp.ru \
    --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).