From: Bill Davidsen <davidsen@tmr.com>
To: Greg Freemyer <greg.freemyer@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Adding a smaller drive
Date: Wed, 01 Jul 2009 14:53:23 -0400 [thread overview]
Message-ID: <4A4BB0A3.6050401@tmr.com> (raw)
In-Reply-To: <87f94c370906301122p404c5cbcg61a8dfa81ee78594@mail.gmail.com>
Greg Freemyer wrote:
> On Tue, Jun 30, 2009 at 1:01 PM, Bill Davidsen<davidsen@tmr.com> wrote:
>
>> Leslie Rhorer wrote:
>>
> <snip>
>
>>> I may have to rethink my position on using raw drives. If I
>>> partition the drives, I can make the partition a bit smaller than the
>>> whole
>>> drive, allowing for the addition of a future drive whose size is a bit
>>> off.
>>> I hate to waste space, but being stuck with an undersized or limping array
>>> is worse.
>>>
>>>
>> Some manufacturers use the HPA (host protected area) to reduce the size
>> available to the user. You will see reference to this in the dmesg output.
>> There is a tool to let you see/set HPA, but I can't put my hand on the info
>> right now, the one I have is out of date, so I won't mention it.
>>
>
> Any recent version of hdparm can get/set HPA for LBA-48 drives. That
> feature went in a couple years ago. And it is the only tool I know
> that works with LBA-48 drives. (ie. drives larger than 128 GiB).
>
> If your version is too old you can get a new version off of
> sourceforge I believe.
>
I was actually thinking of a GUI tool, used for partition management,
but I can't recall the name (I do most things like that from the cli).
There's also SleuthKit, which may handle larger drives, 1TB limit comes
to mind, but I was using it for something else rather than HPA.
In any case, some drives seem to use that for sizing, just wanted to
note that to the O.P.
--
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.
prev parent reply other threads:[~2009-07-01 18:53 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
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 [this message]
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=4A4BB0A3.6050401@tmr.com \
--to=davidsen@tmr.com \
--cc=greg.freemyer@gmail.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).