From: Bill Davidsen <davidsen@tmr.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Craig Hollabaugh <craig@hollabaugh.com>,
Neil Brown <neilb@suse.de>,
linux-raid@vger.kernel.org
Subject: Re: RAID5 kicks non-fresh drives
Date: Fri, 26 May 2006 13:32:28 -0400 [thread overview]
Message-ID: <44773BAC.9090002@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0605260956120.20178@uplift.swm.pp.se>
Mikael Abrahamsson wrote:
> On Thu, 25 May 2006, Craig Hollabaugh wrote:
>
>> That did it! I set the partition FS Types from 'Linux' to 'Linux raid
>> autodetect' after my last re-sync completed. Manually stopped and
>> started the array. Things looked good, so I crossed my fingers and
>> rebooted. The kernel found all the drives and all is happy here in
>> Colorado.
>
>
> Would it make sense for the raid code to somehow warn in the log when
> a device in a raid set doesn't have "Linux raid autodetect" partition
> type? If this was in "dmesg", would you have spotted the problem before?
>
As long as it is written where logwatch will see it, not recognize it,
and report it... People who don't read their logwatch reports get no
sympathy from me.
--
bill davidsen <davidsen@tmr.com>
CTO TMR Associates, Inc
Doing interesting things with small computers since 1979
next prev parent reply other threads:[~2006-05-26 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 15:38 RAID5 kicks non-fresh drives Craig Hollabaugh
2006-05-25 21:18 ` Neil Brown
2006-05-25 21:39 ` Craig Hollabaugh
2006-05-25 22:30 ` Craig Hollabaugh
2006-05-26 7:57 ` Mikael Abrahamsson
2006-05-26 14:11 ` Craig Hollabaugh
2006-05-26 16:45 ` Mark Hahn
2006-05-26 17:06 ` Craig Hollabaugh
2006-05-26 17:30 ` Mark Hahn
2006-05-26 18:01 ` Craig Hollabaugh
2006-05-26 18:38 ` Luca Berra
2006-05-26 19:37 ` Mark Hahn
2006-05-27 12:21 ` Luca Berra
2006-05-29 4:34 ` Neil Brown
2006-05-26 17:32 ` Bill Davidsen [this message]
2006-05-26 17:49 ` Craig Hollabaugh
2006-05-29 5:20 ` Neil Brown
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=44773BAC.9090002@tmr.com \
--to=davidsen@tmr.com \
--cc=craig@hollabaugh.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=swmike@swm.pp.se \
/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).