linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel L. Miller" <dmiller@amfes.com>
To: linux-raid@vger.kernel.org
Subject: Re: Raid-10 mount at startup always has problem
Date: Wed, 24 Oct 2007 22:43:51 -0700	[thread overview]
Message-ID: <47202D17.3040000@amfes.com> (raw)
In-Reply-To: <471FA485.6010705@tmr.com>

Bill Davidsen wrote:
>>>> Daniel L. Miller wrote:
>> Current mdadm.conf:
>> DEVICE partitions
>> ARRAY /dev/.static/dev/md0 level=raid10 num-devices=4 
>> UUID=9d94b17b:f5fac31a:577c252b:0d4c4b2a auto=part
>>
>> still have the problem where on boot one drive is not part of the 
>> array.  Is there a log file I can check to find out WHY a drive is 
>> not being added?  It's been a while since the reboot, but I did find 
>> some entries in dmesg - I'm appending both the md lines and the 
>> physical disk related lines.  The bottom shows one disk not being 
>> added (this time is was sda) - and the disk that gets skipped on each 
>> boot seems to be random - there's no consistent failure:
>
> I suspect the base problem is that you are using whole disks instead 
> of partitions, and the problem with the partition table below is 
> probably an indication that you have something on that drive which 
> looks like a partition table but isn't. That prevents the drive from 
> being recognized as a whole drive. You're lucky, if the data looked 
> enough like a partition table to be valid the o/s probably would have 
> tried to do something with it.
> [...]
> This may be the rare case where you really do need to specify the 
> actual devices to get reliable operation.
OK - I'm officially confused now (I was just unofficially before).  WHY 
is it a problem using whole drives as RAID components?  I would have 
thought that building a RAID storage unit with identically sized drives 
- and using each drive's full capacity - is exactly the way you're 
supposed to!  I should mention that the boot/system drive is IDE, and 
NOT part of the RAID.  So I'm not worried about losing the system - but 
I AM concerned about the data.  I'm using four drives in a RAID-10 
configuration - I thought this would provide a good blend of safety and 
performance for a small fileserver.

Because it's RAID-10 - I would ASSuME that I can drop one drive (after 
all, I keep booting one drive short), partition if necessary, and add it 
back in.  But how would splitting these disks into partitions improve 
either stability or performance?

-- 
Daniel

  reply	other threads:[~2007-10-25  5:43 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-27 18:14 Raid-10 mount at startup always has problem Daniel L. Miller
     [not found] ` <46D49F1A.7030409@tmr.com>
2007-09-10  1:53   ` Daniel L. Miller
2007-09-10  2:04     ` Richard Scobie
     [not found]     ` <46E4A5F0.9090407@sauce.co.nz>
2007-09-10  2:11       ` Daniel L. Miller
2007-10-24 14:22         ` Daniel L. Miller
2007-10-24 16:25           ` Doug Ledford
2007-10-24 20:01           ` Bill Davidsen
2007-10-25  5:43             ` Daniel L. Miller [this message]
2007-10-25  6:40               ` Doug Ledford
2007-10-26  9:15                 ` Luca Berra
2007-10-26 16:53                   ` Gabor Gombas
2007-10-27  7:57                     ` Luca Berra
2007-10-26 19:26                   ` Doug Ledford
2007-10-27  7:50                     ` Luca Berra
2007-10-27 15:07                       ` Gabor Gombas
2007-10-27 20:47                       ` Doug Ledford
2007-10-28 13:37                         ` Luca Berra
2007-10-28 17:55                           ` Doug Ledford
2007-10-29  0:21                     ` Bill Davidsen
2007-10-29  7:41                       ` Luca Berra
2007-10-29 13:22                         ` Bill Davidsen
2007-10-29 15:21                           ` Doug Ledford
2007-10-29 15:54                         ` Gabor Gombas
2007-10-29 14:31                       ` Doug Ledford
2007-10-29  5:59                 ` Daniel L. Miller
2007-10-29  8:18                   ` Luca Berra
2007-10-29 15:47                     ` Doug Ledford
2007-10-29 21:29                       ` Luca Berra
2007-10-29 23:15                         ` Doug Ledford
2007-10-30  0:03                           ` Daniel L. Miller
2007-11-01 13:56                             ` Bill Davidsen
2007-12-17 14:58                             ` Daniel L. Miller
2007-10-29 17:08                   ` Doug Ledford
2007-10-29 18:56                   ` Richard Scobie
2007-10-25  6:12           ` Neil Brown
2007-10-25  6:51             ` Doug Ledford
2007-10-25 13:13             ` Daniel L. Miller
2007-10-25 13:33             ` Daniel L. Miller
2007-10-26  6:12               ` Neil Brown
2007-10-25 14:46             ` Bill Davidsen
2007-10-25 16:13               ` Daniel L. Miller
2007-10-26  5:59               ` 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=47202D17.3040000@amfes.com \
    --to=dmiller@amfes.com \
    --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 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).