linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Andy Smith <andy@lug.org.uk>
Cc: linux-raid@vger.kernel.org
Subject: Re: block level vs. file level
Date: Sat, 18 Feb 2006 19:38:00 -0500	[thread overview]
Message-ID: <43F7BDE8.70309@tmr.com> (raw)
In-Reply-To: <20060212213157.GX32687@strugglers.net>

Andy Smith wrote:

>On Sun, Feb 12, 2006 at 11:31:07AM -0800, it wrote:
>  
>
>>The hardware raid does the mirroring on the block level, so it's 
>>actually /dev/sda mirroring /dev/sdb - the whole drive, and not 
>>partitions. There is a way to set this up on software raid. It takes 
>>more configuration tweaking, but the mirroring then includes the 
>>partition table as well. This way, if a drive fails, one can replace it 
>>without pre-partitioning it.
>>    
>>
>
>That can be less flexible though.  If I have say 4 drives then I
>quite often want small /boot, / and swap under RAID-1 then the rest
>as a single large partition in RAID-5, -6 or -10 as an LVM PV.
>
>  
>
>>This also raises another point, which is relevant for both cases - same 
>>exact models of hard disks have different number of cylinders, so if a 
>>RAID partition is created on a larger drive it cannot be mirrored to a 
>>smaller drive.
>>    
>>
>
>Same exact models don't usually have different block counts, but
>certainly if you replace a dead drive with a different one of the
>same advertised capacity you can end up getting one slightly
>smaller.
>
>  
>
>>Does anyone have any experience with this?
>>    
>>
>
>Yes, and it's a pain, but if you have to deal with it I think the
>wealth of options in md leaves you better able to handle it than
>with hardware RAID.  Here's something that happened to me:
>
>http://strugglers.net/wiki/becks.strugglers.net
>
>  
>
I don't quite understand your problem with fdisk, you can specify 
starting sector and then either ending sector or size, and call it any 
partition number you want. So I don't see why any other tool is required 
and what "at the end" meant in you tale.

Glad you got it working, but you may have used more solution than you 
have problem.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


  parent reply	other threads:[~2006-02-19  0:38 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 [this message]
2006-02-13  8:48 ` PFC
2006-02-13 12:01   ` Andy Smith

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=43F7BDE8.70309@tmr.com \
    --to=davidsen@tmr.com \
    --cc=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).