linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Smith <andy@lug.org.uk>
To: linux-raid@vger.kernel.org
Subject: Re: block level vs. file level
Date: Mon, 13 Feb 2006 12:01:55 +0000	[thread overview]
Message-ID: <20060213120155.GZ32687@strugglers.net> (raw)
In-Reply-To: <op.s4wlfngxcigqcu@apollo13>

[-- Attachment #1: Type: text/plain, Size: 974 bytes --]

On Mon, Feb 13, 2006 at 09:48:49AM +0100, PFC wrote:
> 	I suggest, when using software raid, to create partitions that are, 
> 	say,  100 megabytes or even a gigabyte smaller than the size of the drive. 
> You  lose a bit of space, but if you ever need to change one, you won't 
> feel  stupid with a brand new drive that you can't use because it's a few  
> sectors too short.

After my previous experience what I tend to do now is set aside
about 2GB on each disk to use as components of a RAID-0 that I use
for scratch space (/tmp or whatever, anything that I don't care
about losing) while the machine is running.

That way if I end up by bad luck getting a slightly smaller
replacement drive then I can just do away with or shrink its RAID-0
component while keeping the other partitions the same, yet the space
is not *totally* wasted.

-- 
http://strugglers.net/wiki/Xen_hosting -- A Xen VPS hosting hobby
Encrypted mail welcome - keyid 0x604DE5DB

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-02-13 12:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 19:31 block level vs. file level it
2006-02-12 21:31 ` Andy Smith
2006-02-13  1:16   ` it
2006-02-20 16:53     ` Molle Bestefich
2006-02-26  5:11       ` Bill Davidsen
2006-03-03 14:07         ` Molle Bestefich
2006-02-19  0:38   ` Bill Davidsen
2006-02-13  8:48 ` PFC
2006-02-13 12:01   ` Andy Smith [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=20060213120155.GZ32687@strugglers.net \
    --to=andy@lug.org.uk \
    --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).