All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Wheeler <jwwstpete@gmail.com>
To: Gabor Gombas <gombasg@sztaki.hu>
Cc: NeilBrown <neilb@suse.de>, linux-raid@vger.kernel.org
Subject: Re: Random MD Raid resyncs?
Date: Tue, 3 Nov 2009 09:44:50 -0500	[thread overview]
Message-ID: <f1ef83020911030644j140c1cfft81540ddd769a46f7@mail.gmail.com> (raw)
In-Reply-To: <20091103100528.GG24791@boogie.lpds.sztaki.hu>

Hi Gabor:

> auto-read-only is an internal state of the RAID array, it has nothing to
> do with file systems. So you probably won't find anything in the
> locations you mention above; auto-read-only is only displayed in
> /proc/mdstat. Look at the mdadm man page and read the sections "Auto
> Assembly" and "INCREMENTAL MODE".

Interesting.  I just got done reading that section in the manpage; if
anything, I didn't know mdadm would process an array in that fashion.
However, I don't see this behavior listed in my /proc/mdstat output.
If it's there, I'm missing it:

-- SNIP --

# cat /proc/mdstat
Personalities : [raid10] [raid6] [raid5] [raid4]
md1 : active raid5 sda2[0] sdb1[1] sdc1[2] sdd1[3] sde1[4] sdf1[5]
      393230080 blocks level 5, 256k chunk, algorithm 2 [6/6] [UUUUUU]

md2 : active raid5 sda4[0] sdb4[1] sdc3[2] sdd3[3] sde3[4] sdf4[5]
      424034560 blocks level 5, 256k chunk, algorithm 2 [6/6] [UUUUUU]

md0 : active raid10 sdf2[5] sde2[4] sdd2[3] sdc2[2] sdb2[1] sda3[0]
      235938048 blocks 256K chunks 2 near-copies [6/6] [UUUUUU]

unused devices: <none>

-- END SNIP --

On Tue, Nov 3, 2009 at 5:05 AM, Gabor Gombas <gombasg@sztaki.hu> wrote:
> On Mon, Nov 02, 2009 at 06:40:59PM -0500, Jesse Wheeler wrote:
>
>> AFAIK, any of the RAID devices are not mounted 'auto-read-only' by the
>> kernel.  I'll double check /etc/fstab, /var/log/messages, and
>> /var/log/dmesg when I get back to the site.  Unless there was a change
>> by the upstream vendor, I wouldn't mount a production filesystem in
>> that manner.  Of course, I've been surprised before!
>
> auto-read-only is an internal state of the RAID array, it has nothing to
> do with file systems. So you probably won't find anything in the
> locations you mention above; auto-read-only is only displayed in
> /proc/mdstat. Look at the mdadm man page and read the sections "Auto
> Assembly" and "INCREMENTAL MODE".
>
> Gabor
>
> --
>     ---------------------------------------------------------
>     MTA SZTAKI Computer and Automation Research Institute
>                Hungarian Academy of Sciences
>     ---------------------------------------------------------
>
--
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

  reply	other threads:[~2009-11-03 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f1ef83020911020655kf8935c5icf9aea31edb03c57@mail.gmail.com>
2009-11-02 14:57 ` Random MD Raid resyncs? Jesse Wheeler
2009-11-02 22:23   ` NeilBrown
2009-11-02 23:40     ` Jesse Wheeler
2009-11-03 10:05       ` Gabor Gombas
2009-11-03 14:44         ` Jesse Wheeler [this message]
2009-11-03 15:45           ` Gabor Gombas
2009-11-03 18:25             ` Jesse Wheeler

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=f1ef83020911030644j140c1cfft81540ddd769a46f7@mail.gmail.com \
    --to=jwwstpete@gmail.com \
    --cc=gombasg@sztaki.hu \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.