File System - LT Tran Y Son
File System - LT Tran Y Son
This file system assumes that the disk begins with a boot block and then the disk is created from a series
of other blockgroups. Block groups are numbered sequentially, and contain several subfields.
1. Super Block – Specifies the number of blocks, the number of i-nodes, block size etc.
2. Group Description – Contains information about the bitmap location, number of free blocks, i-
nodes, directories in the group, etc.
3. Block Bitmap – Contains a list of free blocks.
4. I-node Bitmap – Contains a list of free I-nodes.
5. I-nodes – These are the actual i-nodes. Each I-node is 128 byte long.
Windows 2000 (W2K) supports a number of file systems including the file allocation table (FAT) that
runs on Windows 95, MS-DOS and OS/2. But the developers of W@K also designed a new file system,
the W2K file system (NTFS), that is intended to meet high-end requirements for workstations and
servers.
1. Client/server applications such as file servers, computer servers and database servers.
2. Resource-intensive engineering and scientific applications.
3. Network applications for large corporate systems.
1. Recoverability
2. Security
3. Large disks and large files
4. Multiple data streams
5. General Indexing Facility
1. Sector :
The smallest physical storage unit on the disk. The data size in bytes is a power of 2 and is
almost always 512 bytes.
2. Cluster :
One or more contiguous (next to each other on the same track) sectors. The cluster size in
sectors is a power of 2.
3. Volume :
A logical partition on a disk, consisting of one or more clusters and used by a file system to
allocate space. At any time, a volume consists of a file system information, a collection of files,
and any additional unallocated space remaining on the volume that can be allocated to files. A
volume can be all or a portion of a single disk or it can extend across multiple disks. If hardware
or software RAID 5 is employed, a volume consists of stripes spanning multiple disks.
C. Comparison:
Windows uses FAT and NTFS as file systems, while Linux uses a variety of file systems.
Unlike Windows, Linux is bootable from a network drive.
Linux has two kinds of major partitions called data partitions and swap partitions. Because of the
existence of swap partitions, you never run out of memory in Linux (like in windows).
In terms of recovery tools, only a limited number of tools can be used on Windows, while there is a large
number of UNIX based recovery tools available for Linux file systems.
Each Windows file system gets a drive letter, like “C:”. On Linux, each file system gets a device, like
/dev/hda1 (“hard disk A part 1”), which is represented as a file. Such a file is a device file (since a disk is a
device), hence the “dev” part of the path name. Also, the device file is not an ordinary text file, it is a
“special file.” Since disks are block devices (unlike a serial mouse), such a file is fully described as a
“block special device file.” The numbered part of the path can be a little weird to get right; it’s best to
be guided by documentation there or extract the right name from a report.
On Windows, file systems can be FAT16, FAT32 or NTFS, to name a few. Recall FAT16 is the ancient
standard responsible for Windows file names with the “8.3” file name length restriction. On Linux,
filesystems can be “minix,” “ext,” or “ext2,” to name a few. Also, “minix” is an example of the ancient
standard responsible for UNIX file names once being limited to 14 characters. Linux also has “msdos”
and “vfat” file systems for compatibility with Windows and DOS, plus more.
Windows uses FORMAT.EXE to format a disk. Linux uses “mkfs” (“make file system”) in various specialist
forms.
Each Windows file system has a File Allocation Table (FAT, VFAT, or similar) that states which disk blocks
hold the topmost directory. On Linux, the equivalent on most filesystems is the superblock. A Linux file
system has multiple copies of the superblock physically saved on the disk. This provides redundancy in
case of a partial disk corruption. The superblock is just about always in memory on Linux; that is not the
case for ancient DOS-like file systems. There are no special restrictions on files placed in the topmost
directory on Linux, either.
On Windows, there is one drive letter per mounted file system: for example, C: for C: and D: for D:.
On Linux there are no drive letters, so one file system is mounted on “/” and all other file systems are
mounted on subdirectories of “/.” This arrangement is like the little-used MS-DOS command SUBST, or
the NET USE command that supports Novell‘s NetWare. The equivalent Linux command is “mount.”
You can see all this at work on Linux, but for some of it you need to be logged in as root. Type “cat
/etc/fstab” to see all the mountable devices, including floppy disks and CD players. Type “df” to see the
devices currently mounted, and their free space. In the usual case you can even see the superblock: try
“/sbin/dumpe2fs /dev/hda1” where hda1 comes from the output of “df.” The name “dumpe2fs” is a
casualty of history; it replaces the older “dumpfs.” The information produced is really just for diagnostic
purposes.