All of lore.kernel.org
 help / color / mirror / Atom feed
From: "MediaHost \(TM\)" <webmaster@startcom.org>
To: linux-raid@vger.kernel.org
Subject: Difference between faulty and non-fresh
Date: Sun, 8 Aug 2004 01:41:41 +0200	[thread overview]
Message-ID: <0d4901c47cd8$1a46e350$0200a8c0@internal.startcom.org> (raw)

Hi,

I had a multiple disk failure (so it seams) on raid 5 Kernel 4.20 RedHat 9.

When booting it shows:

Aug  7 21:32:20 apache-7 kernel: md: running: <hda2><hde1><hdg1>
Aug  7 21:32:20 apache-7 kernel: md: hda2's event counter: 0000009a
Aug  7 21:32:20 apache-7 kernel: md: hde1's event counter: 00000099
Aug  7 21:32:20 apache-7 kernel: md: hdg1's event counter: 00000096
Aug  7 21:32:20 apache-7 kernel: md: superblock update time inconsistency -- 
using the most recent one
Aug  7 21:32:20 apache-7 kernel: md: freshest: hda2
Aug  7 21:32:20 apache-7 kernel: md: kicking non-fresh hdg1 from array!
Aug  7 21:32:20 apache-7 kernel: md: unbind<hdg1,2>
Aug  7 21:32:20 apache-7 kernel: md: export_rdev(hdg1)
Aug  7 21:32:20 apache-7 kernel: md3: kicking faulty hde1!
Aug  7 21:32:20 apache-7 kernel: md: unbind<hde1,1>
Aug  7 21:32:20 apache-7 kernel: md: export_rdev(hde1)
Aug  7 21:32:20 apache-7 kernel: md: md3: raid array is not clean -- 
starting background reconstruction
Aug  7 21:32:20 apache-7 kernel: md3: max total readahead window set to 512k
Aug  7 21:32:20 apache-7 kernel: md3: 2 data-disks, max readahead per
data-disk: 256k
Aug  7 21:32:20 apache-7 kernel: raid5: device hda2 operational as raid disk
0
Aug  7 21:32:20 apache-7 kernel: raid5: not enough operational devices for
md3 (2/3 failed)
Aug  7 21:32:20 apache-7 kernel: RAID5 conf printout:
Aug  7 21:32:20 apache-7 kernel:  --- rd:3 wd:1 fd:2
Aug  7 21:32:20 apache-7 kernel:  disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hda2
Aug  7 21:32:20 apache-7 kernel:  disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev
00:00]
Aug  7 21:32:20 apache-7 kernel:  disk 2, s:0, o:0, n:2 rd:2 us:1 dev:[dev
00:00]

What is the difference between non-fresh and faulty? Also when I run lsraid,
it shows /dev/hdg1 as /dev/null...

How do I recover the raid, which one should I mark failed-disk? Very
unclear, after googeling for a few hours now...

Thanks!

Regards

Signer:      Eddy Nigg
Company: StartCom Linux at http://www.startcom.org
                MediaHostT at http://www.mediahost.org



                 reply	other threads:[~2004-08-07 23:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='0d4901c47cd8$1a46e350$0200a8c0@internal.startcom.org' \
    --to=webmaster@startcom.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 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.