Red Hat SYSTEM 8.0 - MIGRATION GUIDE 7.X TO 8.0 Installationsanleitung PDF herunterladen (Seite 106)

106 Appendix E. An Introduction to Disk Partitions

Figure E-2. Disk Drive with a File System

As Figure E-2, implies, the order imposed by a ﬁle system involves some trade-offs:

• A small percentage of the drive’s available space is used to store ﬁle system-related data and can be

considered as overhead.

• A ﬁle system splits the remaining space into small, consistently-sized segments. For Linux, these

segments are known as blocks.

Given that ﬁle systems make things like directories and ﬁles possible, these tradeoffs are usually seen

as a small price to pay.

It is also worth noting that there is no single, universal ﬁle system. As Figure E-3, shows, a disk

drive may have one of many different ﬁle systems written on it. As you might guess, different ﬁle

systems tend to be incompatible; that is, an operating system that supports one ﬁle system (or a

handful of related ﬁle system types) may not support another. This last statement is not a hard-and-

fast rule, however. For example, Red Hat Linux supports a wide variety of ﬁle systems (including

many commonly used by other operating systems), making data interchange between different ﬁle

systems easy.

Figure E-3. Disk Drive with a Different File System

Of course, writing a ﬁle system to disk is only the beginning. The goal of this process is to actually

store and retrieve data. Let us take a look at our drive after some ﬁles have been written to it.

1. Blocks really are consistently sized, unlike our illustrations. Keep in mind, also, that an average disk drive

contains thousands of blocks. But for the purposes of this discussion, please ignore these minor discrepancies.

1 2 ... 101 102 103 104 105 106 107 108 109 110 111 ... 139 140

Keine Kommentare

Red Hat SYSTEM 8.0 - MIGRATION GUIDE 7.X TO 8.0 Installationsanleitung Seite 106