Sponsored Content
Operating Systems Linux Red Hat Partitions necessary in RHEL 6 Post 302772650 by rbatte1 on Tuesday 26th of February 2013 10:19:21 AM
Old 02-26-2013
I suppose that you set up what you think is right for you. Whilst there is nothing officially wrong in just having /, /boot & swap there may be a problem over usage, contention and what happens if something goes wild. Assuming that you will always have /boot and swap, the other filesystems in the base volume group and indeed and other volume groups are up to you.

Consider each volume group as a room in your house. You have one room for total disk space in a volume group (say the kitchen) which you could configure as one large filesystem for the whole room. On the door you hang a clipboard to list what you have, expiry dates and free space information etc. You can just load everything randomly into this one big allocation and keep a note of where it is. You then know that to access any item, you have to read through the notes on the clipboard.


Alternatively, if you separate the room into several cupboards with their own clipboards, you can set up areas for different type of objects, e.g. temporary storage for perishables or frequently created files that are clean up at the end; tinned food for long term storage that you need to know are there but rarely used (reference database perhaps); books area for reference material such as manual pages; appliances/software resources to use etc. etc.

In the second case, you know vaguely what you're after or what is the item you have to store, so you have a clipboard on each of the cupboards. To refer to anything or to update the list is now a smaller job than reading/writing the entire catalogue. If you left the tap running and filled the sink, the tap would fail and turn off.

Back on Unix, if we have log files in /var being part of one big root filesystem then they will continue to grow until the whole of the root filesystem is full and that could be a severe headache. The alternate of having /var as a separate filesystem means that whilst logging might go badly wrong, the operating system as a whole should be protected.


Has that just confused things? Smilie


Overall I would always prefer to split the disks and work out what was critical to allow the system to boot. Keep this in the root filesystem and base volume group. Have everything else in separate filesystems from separate volume groups. Again, it's up to you what you choose for names and function of each, but I would always recommend creating the following as a minimum:-
  • /var
  • /usr
  • /opt
  • /home
  • /tmp

You might consider somewhere to store software install media, be that yum CD media copies or whatever.


If you have a disaster recovery plan, then this can help you to backup and restore just what you need to get the base OS running and then have a working system to restore all you company data and applications.


I hope that this is a useful and that I haven't just confused everyone.

Robin
Liverpool/Blackburn
UK
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

partitions

HI. i installed solaris on a x86 machine and i only partition for 4 gig when it suppose to be 8. i only using 4 gig right now how can i start using the other four. please help, thanks in advance Meeh (2 Replies)
Discussion started by: souldier
2 Replies

2. Red Hat

Difference between RHEL 3 AND RHEL 4

Anybody, let me know major differences between RHEL 3 & 4 . (2 Replies)
Discussion started by: sakthi_13
2 Replies

3. UNIX for Advanced & Expert Users

Partitions

Hello masters, Actually, i am user of Ubuntu, but I want to use Debian too. I have a computer with a product key for w7 so i will use too, only for games... The structure I have thought is the next with 1TiB of capacity. Primary: 50 GB NTFS for W7 Extended: Logical: 20 GB FAT32... (3 Replies)
Discussion started by: albertogarcia
3 Replies

4. UNIX for Dummies Questions & Answers

Partitions.

Hi All, My colleague says . On some boxes we have /var/,/opt are inside root and on some they are not on root they are separately. So please any one explain me what actually the difference is. Thanks is Advance. (3 Replies)
Discussion started by: rama krishna
3 Replies

5. Red Hat

cannot ssh (use NFS) on RHEL box, but can mount external & ssh out of RHEL box

Ok, Im trying to get NFS working on my RHEL 5 box, apparently i can use the box as a client, but not as a server. If it helps i cant ssh into the box (server), but as a client ssh works fine. Ive configured server: /etc/hosts.allow: all : all all :all@all setup my /etc/exports file... (4 Replies)
Discussion started by: drs.grid
4 Replies

6. Red Hat

Does RHEL 5 provide a command to collect RHEL system log in single compress file?

Hi, I heard a command that can collect all RHEL 5 log in a single compress file before I forget. Does any body know...What the command is ? Thanks. (4 Replies)
Discussion started by: nnnnnnine
4 Replies

7. Red Hat

Error throwing while installing vsftpd package in rhel 6. using rhel 6 dvd.

Hi all, Im studying rhcsa as of now, so yum installation and dependencies are messing me to not workit out. i have dual os, win 7 & rhel 6. i have tried this installation of vsftpd package with rhel 6 dvd in VM rhel 6 in win 7 as well as host rhel 6.still the same issue. below error... (6 Replies)
Discussion started by: redhatlbug
6 Replies

8. Red Hat

RHEL 6, Spacewalk 2.3 unable to download RHEL 5 repo data

Hello all, I am having a bit of an issue on my Spacewalk installation. Some amplifying information is that it is Spacewalk 2.3 installed on a RHEL 6 machine and I am attempting to install/update a RHEL 5 channel/repository. I am fairly new to Spacewalk so I am still learning but this is what I... (3 Replies)
Discussion started by: jstone4646
3 Replies

9. UNIX for Dummies Questions & Answers

Windows->RHEL->RHEL X11 Forwarding?

I know this question might have been asked a lot but couldn't find anything that worked. From a windows machine 'A' I can only SSH into Linux server 'B' from where I can SSH into another Linux server 'C'. I need to be able to run GUI interfaces on server C which run on my Windows machine. I... (3 Replies)
Discussion started by: hr.prasan
3 Replies

10. Red Hat

Is it possible to install RHEL 7 on top of RHEL 6?

Hi We have RHEL 6.7 on an HP physical server and want to install RHEL 7 (not upgrade) on top of it by means of virtualization. Is it possible to install/configure RHEV/KVM virtualization on base RHEL 6.7 OS instance and then install RHEL 7 as a VM guest on it? If yes, could you please guide me... (1 Reply)
Discussion started by: magnus29
1 Replies
QUOTACHECK(8)						    BSD System Manager's Manual 					     QUOTACHECK(8)

NAME
quotacheck -- filesystem quota consistency checker SYNOPSIS
quotacheck [-gquv] filesystem ... quotacheck [-gquv] [-l maxparallel] -a DESCRIPTION
quotacheck examines each filesystem, builds a table of current disk usage, and compares this table against that recorded in the disk quota file for the filesystem. If any inconsistencies are detected, both the quota file and the current system copy of the incorrect quotas are updated (the latter only occurs if an active filesystem is checked). By default both user and group quotas are checked. Available options: -a If the -a flag is supplied in place of any filesystem names, quotacheck will check all the filesystems indicated in /etc/fstab to be read-write with disk quotas. By default only the types of quotas listed in /etc/fstab are checked. See also -l. -g Only group quotas listed in /etc/fstab are to be checked. See also -u. -l maxparallel Limit the number of parallel checks to the number specified in the following argument. By default, the limit is the number of disks, running one process per disk. If a smaller limit is given, the disks are checked round-robin, one file system at a time. This option is only valid with -a. -q quotacheck runs more quickly, particularly on systems with sparse user id usage, but fails to correct quotas for users [groups] not in the system user [group] database, and owning no files on the filesystem, if the quota file incorrectly believes that they do. -u Only user quotas listed in /etc/fstab are to be checked. See also -g. -v quotacheck is more verbose, and reports corrected discrepancies between the calculated and recorded disk quotas. Specifying both -g and -u is equivalent to the default. Parallel passes are run on the filesystems required, using the pass numbers in /etc/fstab in an identical fashion to fsck(8). Normally quotacheck operates silently. quotacheck expects each filesystem to be checked to have a quota files named quota.user and quota.group which are located at the root of the associated file system. These defaults may be overridden in /etc/fstab. If a file is not present, quotacheck will create it. quotacheck is normally run at boot time from the /etc/rc file, see rc(8), before enabling disk quotas with quotaon(8). quotacheck accesses the raw device in calculating the actual disk usage for each user. Thus, the filesystems checked should be quiescent while quotacheck is running. If quotacheck receives a SIGINFO signal (see the status argument for stty(1)), a line will be written to the standard error output indicating the name of the device currently being checked and progress information. FILES
quota.user at the filesystem root with user quotas quota.group at the filesystem root with group quotas /etc/fstab default filesystems SEE ALSO
quota(1), libquota(3), fstab(5), edquota(8), fsck(8), quotaon(8), repquota(8) HISTORY
The quotacheck command appeared in 4.2BSD. BSD
January 5, 2004 BSD
All times are GMT -4. The time now is 05:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy