All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Walsh <tom@openhardware.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: array always resyncs on boot
Date: Wed, 03 Dec 2008 00:14:31 -0500	[thread overview]
Message-ID: <493615B7.1010503@openhardware.net> (raw)
In-Reply-To: <49357372.5030304@tmr.com>

Bill Davidsen wrote:
> Tom Walsh wrote:
>> Bill Davidsen wrote:
>>>
> 
>>> Just for grins, could you post the partition table for each disk? 
>>> Maybe just the output of "fdisk -l" to show everything? I always 
>>> worry when using drives of "almost" the same size.
>>>
>>
>> Sure, identical tables for all six drives:
>> Disk /dev/sda: 320.0 GB, 320071851520 bytes
>> 255 heads, 63 sectors/track, 38913 cylinders
>> Units = cylinders of 16065 * 512 = 8225280 bytes
>> Disk identifier: 0x733f1de9
>>
>>    Device Boot      Start         End      Blocks   Id  System
>> /dev/sda1   *           1        2433    19543041   fd  Linux raid 
>> autodetect
>> /dev/sda2            2434        2677     1959930   82  Linux swap / 
>> Solaris
>> /dev/sda3            2678       38900   290961247+   5  Extended
>> /dev/sda5            2678       38900   290961216   fd  Linux raid 
>> autodetect
>>
> Okay, I was just looking at the sizes of the drives, since they are not 
> the same, and wondering if the HPA used to make them look the same was 
> in any way leaking and making the HPA area visible. Looks like the 
> "assembled at the wrong time" is the issue, and any of the fixes will 
> probably solve the issue.
>>


Oh yes, the addition of the bitmap cured the resync problems.  I am so 
happy that you guys helped resolving this!  This box is to become a 
primary work machine for me and the problem with the array was driving 
me crazy. I hate having computers doing bad things without an 
explanation. Reason #73 that I don't use the Brand-M O/S...  ;-)


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net http://cyberiansoftware.com http://openzipit.org
"Windows? No thanks, I have work to do..."
----------------------------------------------------


  parent reply	other threads:[~2008-12-03  5:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-29 21:23 array always resyncs on boot Tom Walsh
2008-11-29 21:37 ` Justin Piszcz
2008-11-30  1:07   ` Tom Walsh
2008-11-30  1:23     ` Justin Piszcz
2008-11-30  2:21       ` Tom Walsh
2008-12-01 17:46     ` Bill Davidsen
2008-12-01 18:03       ` Tom Walsh
     [not found]         ` <49357372.5030304@tmr.com>
2008-12-03  5:14           ` Tom Walsh [this message]
2008-11-30  8:07 ` Luca Berra
2008-11-30  9:50   ` Tom Walsh
2008-11-30 23:55     ` Tom Walsh
2008-12-01  7:47       ` Luca Berra
2008-12-11  2:46   ` Tom Walsh

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=493615B7.1010503@openhardware.net \
    --to=tom@openhardware.net \
    --cc=davidsen@tmr.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 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.