Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I just tried installed RHEL 4 update 4 on a Rackable box I just received. System has 12 disks, so I created a large raid 5 volume using the system's raid utility. It created a volume that was 4.2Tb, which I kickstarted the OS on top of. During the kickstart I only created the / and /boot partitions figuring I would add the rest of the space later, but it seems that I'm unable to fully utilize all of the space. A fdisk reveals this
[root@et01 ~]# fdisk -l
Disk /dev/sda: 4999.8 GB, 4999893483520 bytes
255 heads, 63 sectors/track, 607869 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 1045 8289540 83 Linux
/dev/sda3 1046 1561 4144770 82 Linux swap
/dev/sda4 1562 73171 575201714 5 Extended
/dev/sda5 1562 73171 575201682+ 83 Linux
showing 607869 cylinders, but fdisk only allows me to go up to 73171 cylinders? Is there any way to use all of the cylinders here, hopefully without having to rebuild the system completely?
IIRC, the fdisk utility has a size limitation (I think it's 2 TB or so). Use parted instead ... that's what I do to partition the big RAID arrays at work. It will be able to address the full size of the array.
btmiller, I was able to use parted, and that did allow me to create a large enough partition. Thanks for the suggestion
GNU Parted 1.6.19
Copyright (C) 1998 - 2004 Free Software Foundation, Inc.
This program is free software, covered by the GNU General Public License.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied
warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
Disk geometry for /dev/sda: 0.000-4768270.000 megabytes
Disk label type: msdos
Minor Start End Type Filesystem Flags
1 0.031 101.975 primary ext3 boot
2 101.975 8197.229 primary ext3
3 8197.229 12244.855 primary linux-swap
(parted) mkpart p 12244.855
Information: Don't forget to update /etc/fstab, if necessary.