Optimum UNIX File System Partition + Setup Strategy

When separating a new system disk (s) for UNIX, what is your prefered approach for both desktop computer and/or web servers?

Please include disk partition format, documents system layout (s) and also alternatives, place factors, RAID degree (s), LVM teams and also quantities, security, and also any kind of various other pertinent setups.

0
2019-05-07 08:27:08
Source Share
Answers: 6

If it is Linux, have a different/ boot.

For various other Unix versions, commonly, I have actually advised dividings for/ and also/ var, information is generally placed at/ u001,/ u002 etc

Previously, there was a demand to greatly partition as disk room was restricted and also you did not desire a solitary loaded partition to lower the whole system. With the substantially raised storage space readily available today along with the numerous resizing and also virtualization alternatives readily available, the demand for several dividings IMO has actually dropped. That paired with the reality that it's a problem to relocate points around when you have several dividings suggests that if you can escape much less, do it.

Having swap as 2xRAM does not make good sense when you have claim 32GB of memory. So bear in mind, the "regulations" are actually standards and also some merely do not make good sense taking into account the more recent equipment readily available currently.

0
2019-05-12 00:58:20
Source

Physical Disks Partitioning
Start with 2 disks minimum:

#1 100MB,     ID=83 (Linux), Boot Flag ON
#2 Remaining, ID=FD (Linux Raid Auto)

The 100MB partition is for the/ boot quantity. I leave this on all my drives (also non - boot) to permit adaptability so any kind of drive can be later on made it possible for too. IF the disks are not matched in dimension, or you have a weird number (500GB, 250GBx2), after that separate the dividings of the 500GB drive to match the smaller sized disks.

RAID
Using the 100MB dividings on sda and also sdb create a RAID1 (mirror) quantity for /boot. This comes to be md0 .

md0        /boot          100MB          Ext2

Don't trouble making use of an unique FS on/ boot, it's ineffective.

The continuing to be room can be set up in various approaches. I go with a RAID10 (mirror/stripe) making use of 64K portions and also "2 much - duplicates" for rate. This offers you a great deal of adaptability to incrementally update drives down the line. The various other alternatives is to do a RAID5/ 6. Nonetheless the useful room will certainly be restricted to the tiniest partition, and also DO NOT make use of dividings from the very same tools. Call the new RAID selections md1 , md2 , and more.

LVM
Take every one of the RAID selections other than md0 , and also placed them right into a solitary LVM quantity team called lvm_vg0 . If you have RAID5 and also RAID10 quantities, it's possibly best not to incorporate them, yet I presume it would not injure.

Partition out VG0 for the continuing to be system places. Remember it's reasonably very easy to add even more room if required, so these numbers can be rather traditional.

lvm_vg0-root   /      8GB     Ext3/ReiserFS  (core distro files)
lvm_vg0-home   /home  20+GB   Ext3/ReiserFS  (user data, documents)
lvm_vg0-data   /data  60+GB   XFS            (media, large files, vm's)

XFS documents systems can not be reduced, so maintain that in mind. Additionally, reducing an on-line origin quantity is possibly not sustained.

Updating If you ever before intend to exchange disks for bigger dimensions you have a couple of alternatives. The most convenient is including drives in sets or even more, and also add the new RAID selections to the existing LVM VG.

An additional alternative is including a solitary drive that is > = to the amount of the existing room. As an example, if you have 2 100GB tool in RAID10, you can add a new 200GB tool and also mirror it making use of both old tools. This is extra mistake vulnerable, yet will certainly function.

If required, md# tools can be gotten rid of from the LVM VG without shedding information. This can be done if there suffices free LVM room to change all made use of LVM obstructs from the md# tool to others. LVM can just make use of room that has actually not been appointed to a LV, so a vacant documents system does not count as "free" room.

0
2019-05-11 20:13:01
Source

Planning an excellent dividing framework is greatly depending on in fact recognizing just how you are mosting likely to make use of the system. Any kind of arbitrary suggestions that does not think about what the system is doing isn't mosting likely to be specifically valuable.

All the expensive filesystems might serve from time to time, yet if you desire a secure system it might be a far better suggestion to simply stick to the 'typical' filesystem (i.e. ext3) unless you have a great factor to make use of another thing.

RAID is excellent, I constantly run RAID1 on all my computers due to the fact that I have actually had way too many disk drives fall short.

Security with something like dm-crypt is excellent if your system is a mobile tool, has high - value information, or your simply paranoid.

As you are intending your dividings it is really handy to have a mutual understanding of points like the Filesystem Hierarchy Standard and also if/how your picked unix differ the criterion.

Making use of LVM can make it a lot easier to transform your mind in the future and also readjust your dividings without needing to reboot., and also its capacity to create photos can be really simple to create excellent back-ups. Usage LVM, and also do not quickly allocate every one of your room.

0
2019-05-10 15:20:25
Source

Wow, wonderful inquiry. Been searching for the excellent solution for this for yonks.

I directly have 50Mb/ boot ~ 8GB/ et cetera goes in the direction of/ residence. Thats much from the excellent though. I require to explore different filesystems, presently I make use of ext3 yet I've listened to wonderful points of various other filesystems as an example XFS.

I generally additionally create a documents container for/ tmp totally so I can be extra adaptable with it in future.

0
2019-05-09 04:16:29
Source

I'm a follower of LVM for this sort of troubles. You simply require some room for/ boot (i make use of concerning 100MB). Incorporated with filesystems which can dynamically expand and also reduce (or at the very least expand) you never ever need to think of to tiny dividings once more.

On my desktop I make use of an LVM with XFS as filesystem for all dividings. I create as tiny as feasible and also allow them expand as I require even more room.

0
2019-05-09 04:09:04
Source

I simply run Linux Workstations. I make use of the ext3 documents system and also the dimensions rather rely on the dimension of the disks, being extra charitable with the dividings on the bigger disks. These are about in the order they show up in the partition table :

  • / boot - 100 MEGABYTES
  • swap room - 2xRAM
  • / usr - 10-20 GB
  • / - 5-10 GB
  • / var - 1-2 GB
  • / tmp - 1-2 GB
  • / usr/local - 10-20 GB
  • / residence - every little thing else.

On my better half's workstations at the college, which have 2 750 GB drives, we developed, along with the above, a loads ~ 100 GB dividings throughout the numerous drives all placed in/ data/N where N was a number from 1 to 12. She makes use of these to hold the information for her various study tasks.

0
2019-05-08 00:35:00
Source