linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Phillip Susi <psusi@ubuntu.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: Intel fakeraid working?
Date: Thu, 5 Apr 2012 11:13:17 +1000	[thread overview]
Message-ID: <20120405111317.2a5227b1@notabene.brown> (raw)
In-Reply-To: <4F7CEDD0.9080904@ubuntu.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 04 Apr 2012 20:56:48 -0400 Phillip Susi <psusi@ubuntu.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I was trying to use mdadm to activate an intel fakeraid last night and mdadm insisted on activating it as read-only.  I could not get it to switch to read-wrte.  Today I came across this bug:
> 
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972960

That bug is fixed by 

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=c744a65c1e2d59acc54333ce80a5b0702a98010b

and is not specific to Intel IMSM RAID.

(I personally don't like the term 'fakeraid' - there is nothing fake about
it.  Firmware RAID is a suitable term).

I believe Intel RAID works and it certainly works in my tests, but they are
fairly limited.  Intel do much broader testing and they seem to be reasonably
happy with it.

If the array was activated read-only, that suggests that 'mdmon' didn't run.
mdmon is a daemon which monitors the array and updates the metadata as
needed.  until it is running it is not safe for the array to be writable.
However it should be started automatically by mdadm.

How are you attempting to start the array?

NeilBrown


> 
> It seems that the kernel OOPSed here:
> 
> void md_write_start(struct mddev *mddev, struct bio *bi)
> {
> 	int did_change = 0;
> 	if (bio_data_dir(bi) != WRITE)
> 		return;
> 
> 	BUG_ON(mddev->ro == 1);
> 
> It appears this is because it wanted to update the metadata, but the array was read-only, so I thought this might be related to what I was seeing, and there is a bug that is preventing the array from correctly going read-write.
> 
> Is the Intel fakeraid support actually working yet, or still in development?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> 
> iQEcBAEBAgAGBQJPfO3QAAoJEJrBOlT6nu75IS4H/0nerXBIW6wnYrmZPbWZH+sr
> kVTVPDAqLCvbUATicLdwsJULWwqJmsyWnXTwnm7Ssug2phmcnK8cDFzNiLY/Q3ez
> A0YdMmVog74viMSfZTLVfeiPYnccuTYLeH/U3glJVJ2ISyoFQi0mH6Kd/1eEO153
> 4XazWr7pj/QFeBsPnYuVlojvlsHR6QwdjU3aAsObdCxWdITrnJLLRYC9S4cgqS9m
> Mdh1A4dbzeyj5SrNDAX1McQD+SQDnrPR6r17Tftr9eMcLCp6mzaxYkUu+GE1r8jr
> 9DRqGqe0sAdNjOn4cFMRZVOaHxMjGUXxxn8tuDNS2/p99P6kdCvQO280PFHByog=
> =H98J
> -----END PGP SIGNATURE-----
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)

iQIVAwUBT3zxrTnsnt1WYoG5AQJpCRAAuqqH17YGVY9VzLRoa2oQfEJNZ2XP4GFl
a+ICYLGtLHMGEkMJJcPKPMjmzkyU4F6hFUDWK7npASVeVKqWqlnmFV+Hs0JifEJv
aIeS47yLgjzQ5iluBaFkRXP8Dyb03RTZlBM9FVI+w/oXbmgU4h1Z8sBlOJnh3Pb1
4ET/wGioy0yQyZ3vi9VVj16ugKnQHYjnMShZoHvEd0zEySvFfy+5NSZY/kJF6ElM
+ZHQQc1xB83zSQ1sZ0P6meCIS3zbwNnRl5yUckgXI5yMXxBjP/QFbmu1Gd9M8Q25
omPtNeFxDCxk/u5fakP24jotoFZcA+5+iAdySzXAiVErNxIXfBRLp2KVHjboEMLz
pbZTTFK7by1xQ59Dm+s1As9AgA3NLXhcPocFkJq9UpI9INddqqC2SMi7k1HsuOyf
VkTY8Kh3UkHWj0aqeHGaEHh3EavKe8jdm8ER/g0QXlAAcZpUm9GUnkTvEraTrBnN
Wjki3cnx5tfRbqQ+1jY7W1L9zdlOTpdwIGMH8PfPeptrYKD1OhrupTsTGP0SuT6P
X2Lsaeeh4etk9m7nSo5UG7cCMDNxVOIElwXDw9O38tPRNeuk4+UuFmKL0IzgtnX9
MBzNNPSVvQGoYF8Mo+rMaeTDcYSfEhTuA4JsnBL9WcScLsQqYfhQoEjKtnI/l/fR
LQev2W+HASQ=
=N8QX
-----END PGP SIGNATURE-----

  reply	other threads:[~2012-04-05  1:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05  0:56 Intel fakeraid working? Phillip Susi
2012-04-05  1:13 ` NeilBrown [this message]
2012-04-05 18:20   ` Phillip Susi
2012-04-05 23:25     ` NeilBrown
2012-04-06 10:36     ` Jan Ceuleers
2012-04-05 18:23   ` Phillip Susi
2012-04-05 23:24     ` NeilBrown
2012-04-06  1:10       ` Phillip Susi
2012-04-09 23:43         ` NeilBrown
2012-04-10 13:14           ` Phillip Susi
2012-04-23  2:25             ` NeilBrown
2012-04-23  4:06               ` Phillip Susi

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=20120405111317.2a5227b1@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=psusi@ubuntu.com \
    /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).