Choosing a partitioning scheme
The Sum of the Parts
Despite the popularity of LVM, traditional partitioning is still preferred by some admins. We provide some tips to consider before choosing a partitioning scheme for your setup.
Partitioning a hard disk used to be simple. You had one large partition for the Linux operating system and one swap partition to provide additional virtual memory when your RAM ran out. Today, however, you are often well-advised to consider more complex partitioning schemes.
Especially on networks, traditional partitioning is often replaced today by Logical Volume Management (LVM) , an alternative method for dividing hard drives. LVM has several advantages over traditional partitioning, including the ability to hot-swap disks and to create a single logical volume that spans multiple hard disks. In particular, with LVM, the resizing and moving of partitions is much easier and quicker than with traditional partitioning, which can take six or seven hours to resize a 1TB partition.
Both LVM and traditional partitioning help contain runaway processes and applications that might otherwise crash the system. Both, too, work well with disk-oriented backup applications and can help increase system security by marking key directories as read-only for everyday use. However, when LVM goes down, it can make all partitions inaccessible. By contrast, with traditional partitioning, the failure of one partition often leaves the others recoverable. For this reason, many administrators continue to regard traditional partitioning as the preferred way to divide hard disks.
Numerous tools are available for traditional partitioning , including cfdisk  and fdisk , which are useful only for adding or deleting partitions, and GNU Partition Editor (Parted) , which also resizes and moves partitions. Other tools, such as Gnome Partition Editor (GParted)  give Parted a graphical front end. All these tools are reliable, but none should be used without first making a backup and either unmounting the partitions to be edited or – better still – booting from a Live CD so that all partitions on the system are unmounted.
Before you use any of these tools, however, you need to know which directories you want on separate partitions and the size required for each partition. Installation programs for distributions sometimes suggest partitioning schemes and partition sizes, but check these suggestions against your own needs; for example, I find that the Debian installer consistently underestimates the partition sizes.
In fact, even after you are sure of your needs, you might want to increase the sizes by 25 to 100 percent to allow for future growth. After all, who can know how your needs are going to change in the three to five years you are likely to be using the system?
Mapping Directories to Partitions
New Linux users are often told to make their system consist of one root and one swap partition. However, the size of modern hard drives could make this arrangement inefficient and a waste of space.
Conversely, some directories, such as
/bin should generally not be given their own partitions, because putting them anywhere other than on the root partition may make them hard for the system to find. Also, more than about half a dozen partitions could bring its own inefficiencies as the system constantly switches between them.
Whatever partitions you create, use the
e2label command to give them the name of the directory they will carry. The command has the structure
e2label PARTITION LABEL
and returns no input. As you work with your system, labels like
/tmp will be far more meaningful to you than
/dev/sda3 and will free you from having to make deductions based on size.
Exactly which directories go on separate partitions will depend on your own needs and preferences. However, I will outline some of the considerations that should influence your final choice.
For your system to start properly, the root directory must contain
/sbin. Ordinarily, it should also contain
/boot, but on most modern systems you can have a separate
Under ordinary circumstances, 25GB should be adequate for the root partition. However, increase this size if you regularly add new kernels without deleting old ones, or use plenty of applications like Calibre or LibreOffice's own binaries that install to
The boot partition includes Linux kernels, ramdisks, and bootloaders. By isolating the boot function from the rest of the system, you may be able to minimize corruption to the files necessary to start the system by isolating them from those used to keep the system running. For added security, mark
/boot read only, temporarily changing the permissions when installing new kernels.
Typically, 50-100MB is a reasonable size for
/boot. However, if you have more than half a dozen kernels, consider increasing the size or else be careful to delete unused ones.
Buy this article as PDF
MSBuild is now just another GitHub project as Redmond continues its path to the light.
New rules emphasize collegiality in coding.
Upstart lands in the dust bin as a new era begins for Linux.
HP's annual Cyber Risk report offers a bleak look at the state of IT.
But what do the big numbers really mean?
.NET Core execution engine is the basis for cross-platform .NET implementations.
The Xnote trojan hides itself on the target system and will launch a variety of attacks on command.
Spammers go low-volume, and 90% of IE browsers are unpatched.
Adobe scrambles to release patches for vulnerable Flash Player.