All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carsten Aulbert <Carsten.Aulbert@aei.mpg.de>
To: linux-raid@vger.kernel.org
Cc: "gerrit.kuehn@aei.mpg.de" <gerrit.kuehn@aei.mpg.de>
Subject: split brain mode after reboot
Date: Tue, 20 Nov 2012 15:08:45 +0100	[thread overview]
Message-ID: <50AB8EED.4000005@aei.mpg.de> (raw)

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

Hi all

a colleague of mine created a raid 1 on a fairly recent machine

Kernel 3.5.0-sabayon

mdadm - v3.2.3 - 23rd December 2011

During operation sda seemed to have been disconnected by the
system/motherboard/whatever but this was not detected before a reboot
was done, after the reboot, sda re-appeared but of course with a much
older version of the mirror:

Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5]
[raid4] [multipath] [faulty]
md126 : active raid1 sdb1[1]
      4194240 blocks [2/1] [_U]

md127 : active raid1 sdb3[1]
      235808704 blocks [2/1] [_U]

md0 : active raid1 sda1[0]
      4194240 blocks [2/1] [U_]

md1 : active raid0 sda2[0] sdb2[1]
      8387584 blocks 512k chunks

md2 : active raid1 sda3[0]
      235808704 blocks [2/1] [U_]

unused devices: <none>

As no vital information were on these disks, my question for the list is
just if this is an expected/wanted behavior after such an event and what
one could do to prevent this (besides monitoring via mdadm).

Cheers

Carsten

-- 
Dr. Carsten Aulbert - Max Planck Institute for Gravitational Physics
Callinstrasse 38, 30167 Hannover, Germany
phone/fax: +49 511 762-17185 / -17193
https://wiki.atlas.aei.uni-hannover.de/foswiki/bin/view/ATLAS/WebHome


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2044 bytes --]

             reply	other threads:[~2012-11-20 14:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 14:08 Carsten Aulbert [this message]
2012-11-20 21:22 ` split brain mode after reboot NeilBrown
2012-11-22  6:20   ` Carsten Aulbert

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=50AB8EED.4000005@aei.mpg.de \
    --to=carsten.aulbert@aei.mpg.de \
    --cc=gerrit.kuehn@aei.mpg.de \
    --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 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.