All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: lrhorer@satx.rr.com
Cc: linux-raid@vger.kernel.org
Subject: Re: Adding a smaller drive
Date: Sat, 04 Jul 2009 10:59:52 -0400	[thread overview]
Message-ID: <4A4F6E68.7030209@tmr.com> (raw)
In-Reply-To: <20090703161151277.OOAZ19903@cdptpa-omta03.mail.rr.com>

Leslie Rhorer wrote:
>>> Leslie> I may have to rethink my position on using raw drives.  If I
>>> Leslie> partition the drives, I can make the partition a bit smaller
>>> Leslie> than the whole drive, allowing for the addition of a future
>>> Leslie> drive whose size is a bit off.  I hate to waste space, but being
>>> Leslie> stuck with an undersized or limping array is worse.
>>>
>>> This is not nearly as big a problem as it used to be.  Drive
>>> manufacturers need to adhere to an IDEMA standard which requires them to
>>> use a specific LBA count for each capacity class.
>>>
>>> I.e. a 500GB Seagate drive must have exactly the same number of sectors
>>> as a 500GB Western Digital or Hitachi.
>>>
>>> The IDEMA LBA standard applies to 3.5" form factor drives over 160GB as
>>> well as 2.5" FF drives over 80 GB.
>>>       
>> Is that realy exactly so many LBA sectors or at least as many?
>>
>> I don't really see anything wrong with a 500G drive having a few more
>> sectors. And I know my Maxtor 200G disk is 3G bigger than Seagates.
>>     
>
> 	'Excellent point.  If the spec calls for a minimum of sectors, then
> it is quite possible a complaint drive might well have fewer sectors than
> the ones I used to build the array.  OTOH, all of the 1T drives on my
> systems  have precisely the same number of user available sectors, and all
> the 1.5T drives have the same number.  Since the drives represent not only
> different models from one manufacturer but also different manufacturers,
> this suggests to me an adherence to a specific spec.  On yet the other hand,
> it may merely mean they all have the same number of platters and similar
> architectures.  The 1.5T drives are less than 1.5 times bigger than the 1T
> drives, so I could not replace a 3 drive 1T triplet with a pair of 1.5T
> drives.
>   

That last sentence is important! If this is a standard, then it would 
seem to be actually intended to deceive the consumer. If there is to be 
a standard for 1, 1.5, and 2, they really should have some sensible 
relationship in size.

That said, I confess that I use partitions and leave a little breathing 
room on my drives when building a raid array.

-- 
Bill Davidsen <davidsen@tmr.com>
  Obscure bug of 2004: BASH BUFFER OVERFLOW - if bash is being run by a
normal user and is setuid root, with the "vi" line edit mode selected,
and the character set is "big5," an off-by-one error occurs during
wildcard (glob) expansion.


  parent reply	other threads:[~2009-07-04 14:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 18:31 Adding a smaller drive Leslie Rhorer
2009-06-28 19:05 ` John Robinson
2009-06-28 19:47   ` Leslie Rhorer
2009-06-28 21:09     ` John Robinson
2009-06-28 21:22       ` Leslie Rhorer
2009-06-28 22:52         ` John Robinson
2009-06-28 23:07           ` John Robinson
2009-06-29 10:05             ` Goswin von Brederlow
2009-07-01  4:16           ` Leslie Rhorer
2009-06-28 21:33     ` Martin K. Petersen
2009-06-28 21:49       ` Martin K. Petersen
2009-06-28 22:33       ` Mikael Abrahamsson
2009-06-28 22:51         ` Martin K. Petersen
2009-06-28 23:37           ` Mikael Abrahamsson
2009-06-28 23:43             ` Martin K. Petersen
2009-06-28 23:57               ` Mikael Abrahamsson
2009-07-01  4:12           ` Leslie Rhorer
2009-07-01  5:25             ` Martin K. Petersen
2009-07-03 15:46               ` Leslie Rhorer
2009-07-06  0:05                 ` Martin K. Petersen
2009-07-07  3:15                   ` Leslie Rhorer
2009-06-28 23:54         ` John Robinson
2009-06-29  0:02           ` Mikael Abrahamsson
2009-06-29 10:07       ` Goswin von Brederlow
2009-06-29 14:45         ` Martin K. Petersen
2009-07-03 16:12         ` Leslie Rhorer
2009-07-03 17:23           ` Billy Crook
2009-07-04 14:59           ` Bill Davidsen [this message]
2009-07-04 15:20             ` John Robinson
2009-07-05 22:03               ` Leslie Rhorer
2009-07-05 22:12                 ` John Robinson
2009-07-07  2:57                   ` Leslie Rhorer
2009-06-30 17:01     ` Bill Davidsen
2009-06-30 18:22       ` Greg Freemyer
2009-07-01 18:53         ` Bill Davidsen

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=4A4F6E68.7030209@tmr.com \
    --to=davidsen@tmr.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lrhorer@satx.rr.com \
    /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.