All of lore.kernel.org
 help / color / mirror / Atom feed
From: matt brennan <raid@classforge.com>
To: linux-raid@vger.kernel.org
Subject: partition sizing and raid1
Date: Thu, 04 Nov 2004 15:14:36 +1030	[thread overview]
Message-ID: <4189B3B4.2060203@classforge.com> (raw)
In-Reply-To: <4179D9DB.2070709@classforge.com>

I created a new raid1 array on two 300GB disks but it came in 
underweight in size...

Filesystem           1M-blocks      Used Available Use% Mounted on
/dev/md0                129013     27322     95137  23% /home

I guess I stuffed up with the partitioning (from fdisk):

> Disk /dev/hda: 255 heads, 63 sectors, 16709 cylinders
> Units = cylinders of 16065 * 512 bytes
> 
>    Device Boot    Start       End    Blocks   Id  System
> /dev/hda1             1     16709 134215011   fd  Linux raid autodetect

This was accepting fdisk's default max size.

I realise this is not an fdisk mailing list but I guess you've probably 
hit this problem when creating large disk arrays. Could anyone please 
provide a quick hint on what I've stuffed up?

kernel: 2.4.18

dpkg (debian woody) says fdisk is:
ii  util-linux     2.11n-7        Miscellaneous system utilities.

the fdisk man page suggests using cfdisk... is this likely to help? it 
looks like a will have to recreate the raid1 array anyway. :-(

   matt


  parent reply	other threads:[~2004-11-04  4:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23  4:11 Resizing raid-1 on replacing failed disk matt brennan
2004-10-23  5:41 ` Guy
2004-10-23  6:12   ` Guy
2004-10-23  6:31   ` matt brennan
2004-10-25  5:14     ` Neil Brown
2004-11-04  4:44 ` matt brennan [this message]
2004-11-04  5:24   ` partition sizing and raid1 Jim Paris
2004-11-04  8:10   ` Gordon Henderson

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=4189B3B4.2060203@classforge.com \
    --to=raid@classforge.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.