Sponsored Content
Full Discussion: How to partition your disk?
Operating Systems Linux Red Hat How to partition your disk? Post 302774579 by bakunin on Saturday 2nd of March 2013 12:36:35 PM
Old 03-02-2013
First off: whatever your translation engine is, please switch to another one. I have a hard time second-guessing what you might mean.

Before you begin: PLAN, PLAN, PLAN, then plan again. Write down which application you are going to install, how much space you need for the binaries, how much for the data itself, etc..

Always keep in mind that it is easy to increase the size of a filesystem but hard to make it smaller. Therefore, start out with as little space as possible and increase this to the size necessary.

What you need:

1. Boot partition Linux cannot boot from a logical volume, so you need a boot partition to boot from. It should be formatted as "ext3" filesystem and can be very small: 512MB is absolutely enough.

2. The rest of the disk goes to one volume group. If i am correct the RedHat installation process will guide you through the creation of the volume group, so just follow the dialog.

3. Within the volume group all the other filesystems will be created as logical volumes. You will need:

3A. a swap area: make it the same size as your installed memory. More is not better, just a waste.

3B. a "/" filesystem (ext3 or ext4) for the system itself. 5GB are more than enough, you can make it bigger later if this is necessary.

3C. a "/tmp" filesystem (ext3 or ext4) for temporary files. Start with 1GB and increase as necessary.

3D. a "/opt" filesystem (ext3 or ext4) for the application (binaries). Start with what you have found out the application needs, NOT MORE. Increase if it is too small, but only then.

3E. You mentioned DB2, so you probably need some space for the database itself. Talk to the application people where to mount they want it mounted and how much space you have to provide for this. I suggest you leave that out during installation and create it later, as you don't need it to install the system.

3F. It might be a good idea to have a small filesystem for "/home", so that users can put some scripts in their home directories without taxing the "/" filesystem. You might also consider "/root" to be its own filesystem, because you might need some space for logs, administrative scripts, etc.. Start with 5GB in both cases and increase as necessary.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

partition Magic disk

How do I get a partition magic disk or a disk to create a non-DOS partition? :*: c0ldzer0 :*: (4 Replies)
Discussion started by: c0ldzer0
4 Replies

2. UNIX for Dummies Questions & Answers

Disk Partition

Hi All, While my LINUX SERVER installed we didnt' used all the space for partitions. with what tool I can create a new partition or mount point to use the free space. I tried the command fdisk and diskdruid. They are not working. Thanks in advance With Best regards, Varma. (2 Replies)
Discussion started by: jarkvarma
2 Replies

3. Solaris

New disk - how to partition?

Have a solaris x86 running solaris 9. Root disk - logical - mirrored. I added 2 more disks today - and I have mirrored them using array configuration utility. I did a reconfiguration boot - and now I can see the logical disk using format: I then partitioned this the way I wanted (I hope)... (4 Replies)
Discussion started by: frustrated1
4 Replies

4. Solaris

Disk Partition

I have 3 disks to partition in following file system. c1t1d0 = 72gb /prod1 /prod2 /prod3 /prod4 /prod5 I am first time using "format" command to do this. How can i name with specified size. -Adeel (1 Reply)
Discussion started by: deal732
1 Replies

5. UNIX for Advanced & Expert Users

partition disk issue

hi guys, I've got a strange issue, may be one of you has experienced this. SunOS 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-V440 everything is mirrored. My issue is that I have a umpty directory but seems to have data on. Let me show you # df -h /data Filesystem size used... (10 Replies)
Discussion started by: moustik
10 Replies

6. Filesystems, Disks and Memory

Partition disk

Hi, Can I partition disk in use or would I damage the file store on it? Regards Mehrdad (1 Reply)
Discussion started by: mehrdad68
1 Replies

7. Solaris

Move partition to new disk

Hi, The disks of my servers are getting full and I need to move the /export/home partition on to a new set of disks. I already have 2 mirrored disks and have added 2 more and mirrored them after creating the filesystem on them. Do I just need to edit the /etc/vfstab and point the /export/home... (1 Reply)
Discussion started by: run_time_error
1 Replies

8. UNIX for Advanced & Expert Users

Shrink my partition to new disk

I want to backup my partitions by shrinking it my issue is like I want to create a new disk copy from only the used blocks I my current image. How would I redirect the output of resize2fs to new disk and dd the current partition so that I can boot my new image without issues and also without... (3 Replies)
Discussion started by: amol28kulkarni
3 Replies

9. Red Hat

Disk Partition : Skip 1 MB

I want to skip the first cylinder (first 1 MB infact) while I partition my disk using fdisk as it is required that the disk partition to be used (for Oracle RAC Installation) must skip the first 1Mb to avoid overwriting the disk VTOC. The way I am using is: Command (m for help): n Command... (2 Replies)
Discussion started by: jpsingh
2 Replies

10. Solaris

Disk partition slice0

Hi Guys, when performing a disk partition, can any file system other than root be giving to slice 0 or must slice0 hold only root? I am confused about this. Any clarification will be greatly appreciated. Thanks Guys (4 Replies)
Discussion started by: cjashu
4 Replies
re(7)							 Miscellaneous Information Manual						     re(7)

NAME
re - SWXCR RAID interface SYNOPSIS
2100 Server Model A500MP DEC SWXCR controller xcrn at * vector xcintr device disk renn at xcrn drive nn DESCRIPTION
The re driver is for the SWXCR RAID Array controller. The following rules are used to determine the major and minor numbers that are associated with an re type disk. There are two major num- bers used to represent re disks. The major numbers are 11 for block devices and 44 for character (raw) devices. The minor number is used to represent both the unit number and partition. A disk partition refers to a designated portion of the physical disk. To accomplish this reference, the 20-bit minor number is divided into three parts. The lowest six bits of the minor number specify a disk partition. The partitions use a letter, a through h, for their name. The next three bits of the minor number specify the RE unit number for a unit attached to an SWXCR controller. The final 11 bits specify the controller number. The device special file names associated with re disks are based on conventions that are closely associated with the minor number assigned to the disk. The standard device names begin with re for block special files and rre for character (raw) special files. Following the re is the unit number and then a letter, a through h, that represents the partition. Throughout this reference page, the question mark (?) character represents the unit number in the name of the device special file. For example, re?b could represent re0b, re1b, and so on. The unit number can be calculated if the major and minor numbers of an re disk are provided. For example, suppose you have a device spe- cial file rre6a, with a major number of 44 and a minor number of 384. The partition is represented by the lower six bits of the number 384. These lower six bits of the number 384 are 0, which specifies the a partition. The next three bits of the minor number 384 specify the unit number, which is 6. The next eleven bits specify the controller number, which is zero. Putting these three pieces together reveals that the major/minor number pair 44/384 refers to the a partition of unit 6 attached to controller number 0. A disk can be accessed through either the block special file or the character special file. The block special file accesses the disk using the file system's normal buffering mechanism. Reads and writes to the block special file can specify any size. This capability avoids the need to limit data transfers to the size of physical disk records and to calculate offsets within disk records. The file system can break up large read and write requests into smaller fixed size transfers to the disk. The character special file provides a raw interface that allows for direct transmission between the disk and the user's read or write buf- fer. A single read or write to the raw interface results in exactly one I/O operation. Consequently, raw I/O may be considerably more efficient for large transfers. For systems with RE disks, the first software boot after the system is powered on may take longer than expected. This delay is normal and is caused by the software spinning up the RE disks. Disk Support The RE driver handles all disk drives that can be connected to the SWXCR controller. To determine which drives are supported for specific CPU types and hardware configurations, see the Installation and Configuration Guide for the StorageWorks RAID Array 200 Subsystem Family. SWXCR RAID Controllers are viewed in all cases as RE type disks. There are some notable differences that should be taken into considera- tion when configuring a RAID device: Currently only sector sizes of 512 bytes are supported. Logical Volume sizes are not fixed sizes as compared to other disk devices. The size of the Logical Volume is configurable based on needs. The dynamic nature of Logical Volume sizes is dealt with by defining RAID devices as DYNAMIC. Only partitions a, b, c, and g are defined. If necessary, the disklabel(8) command can be run to change and define partitions for RAID devices. Usually, the re?a partition is used for the root file system and the re?b partition as a paging area. The re?c partition can be used for disk-to-disk copying because it maps the entire disk. The starting location and length (in 512 byte sectors) of the disk partitions of each drive are shown in the following table. Partition sizes can be changed by using the disklabel(8) command. SWXCR (RAID) partitions for systems based on the Alpha AXP architecture disk start length re?a 0 131072 re?b 131072 262144 re?c 0 end of media re?d 0 0 re?e 0 0 re?f 0 0 re?g 393216 end of media re?h 0 0 FILES
/dev/re??? /dev/rre??? /etc/disktab RELATED INFORMATION
disklabel(8), MAKEDEV(8), uerf(8) delim off re(7)
All times are GMT -4. The time now is 02:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy