linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michele Bonera <mbonera@gmail.com>
To: Jan Ceuleers <jan.ceuleers@computer.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Problems after reshaping of Raid5 array
Date: Mon, 29 Nov 2010 21:04:39 +0100	[thread overview]
Message-ID: <1291061079.5909.84.camel@bellatrix.morrisoft.local> (raw)
In-Reply-To: <4CF3FB20.2040100@computer.org>

Il giorno lun, 29/11/2010 alle 20.12 +0100, Jan Ceuleers ha scritto:

> I've had similar problems, which I resolved by changing the partition 
> type from fd (Linux RAID autodetect) to 83 (Linux), ensuring that the 
> initrd is able to assemble the RAID.
> Worth a shot.
> HTH, Jan

Thanks for the reply, Jan, but the problem is not at raid level, or
better, the raid just finished to reshape and now has 5/5 of his
components and is active:

root@mizar:~# cat /proc/mdstat 
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0]
[raid1] [raid10] 
md6 : active raid5 sdf1[2] sdb1[0] sda1[1] sdc[4] sde1[3]
      3438905344 blocks level 5, 128k chunk, algorithm 2 [5/5] [UUUUU]


The problem is that I added a device partition (sdc1) but after the
crash the array has sdc (the device) as one of his components. The
partition table on the disk was wiped-out.

The result is that the filesystem on it (dev/md6) is unreadable and
fsck.ext3 can't fix it.

Bye
--
Michele Bonera
linux user group brescia


  reply	other threads:[~2010-11-29 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 17:24 Problems after reshaping of Raid5 array Michele Bonera
2010-11-29 19:12 ` Jan Ceuleers
2010-11-29 20:04   ` Michele Bonera [this message]
2010-11-30 17:00     ` Jan Ceuleers
2010-11-29 21:45 ` Neil Brown
2010-11-30  7:23   ` Michele Bonera
2010-11-30 19:45     ` Jan Ceuleers
2010-12-03  7:03       ` Michele Bonera

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=1291061079.5909.84.camel@bellatrix.morrisoft.local \
    --to=mbonera@gmail.com \
    --cc=jan.ceuleers@computer.org \
    --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).