All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Luis Domingo Lopez <linux-raid@24x7linux.com>
To: linux-raid@vger.kernel.org
Subject: Re: Stupid Question?
Date: Mon, 24 May 2004 01:23:59 +0200	[thread overview]
Message-ID: <20040523232359.GA16899@localhost> (raw)
In-Reply-To: <134.2f7071f3.2de27730@aol.com>

On Sunday, 23 May 2004, at 17:52:48 -0400,
AndyLiebman@aol.com wrote:

> I feel like this is a stupid question. But I actually don't know the answer 
> to it. If I'm going to make a Software RAID array with a bunch of identical 
> disks, do the disks have to have at least one partition on them? Or can I use 
> disks with NO partitions? 
> 
You can use any block device as part of a Linux software RAID device, so
full disks with no partitions inside should be OK. I seem to remember
that this is not the case with LVM, wher you have (should?) to create a
partition even if you want to use the full disk, but is late and maybe I
and mixing things.

> Similarly, if I have made a hardware RAID array (say, with a 3ware 8506 
> card), do I have to create at least a single partition on it before I put a file 
> system on it? 
> 
I don't think so. You can "format" any block device, like a disk
partition, a logical volume, and even a file on disk through the loop
device, so the requirement for a partition table doesn't seem to exist.
I think the only thing needed is a couple of (major,minor) trhough which
to access the underlying block device.

> If partitions aren't necessary, is there any advantage or disadvantage to 
> having a single partition on a disk versus having none? Is having no partitions 
> faster? 
> 
A disk with no partition table is a contiguous block device from sector
zero to the end of the device. Maybe you should follow LVM's advice
about using full disks with no partition table. From pvcreate(8):

DESCRIPTION
       pvcreate initializes PhysicalVolume for later use by the Logical Volume
       Manager (LVM).  Each PhysicalVolume can  be  a  disk  partition,  whole
       disk, meta device, or loopback file.  For DOS disk partitions, the par-
       tition id should be set to 0x8e using fdisk(8), cfdisk(8), or a equiva-
       lent.   For whole disk devices only the partition table must be erased,
       which will effectively destroy all data on that disk.  This can be done
       by zeroing the first sector with:

       dd if=/dev/zero of=PhysicalVolume bs=512 count=1


Greetings.

-- 
Jose Luis Domingo Lopez
Linux Registered User #189436     Debian Linux Sid (Linux 2.6.6)

  reply	other threads:[~2004-05-23 23:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-23 21:52 Stupid Question? AndyLiebman
2004-05-23 23:23 ` Jose Luis Domingo Lopez [this message]
2004-05-24  2:01 ` jim
2004-05-24  2:33   ` Neil Brown
2004-05-24  9:09     ` AW: " root
2004-05-24 22:58       ` Neil Brown
2004-05-24 23:11         ` robin-lists
2004-05-24 23:40           ` Neil Brown
  -- strict thread matches above, loose matches on Subject: below --
2004-05-24  9:33 AndyLiebman

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=20040523232359.GA16899@localhost \
    --to=linux-raid@24x7linux.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.