NOMENCLATURE
FILE
bunch of BYTEs having
start & end
location
Byte stream
fixed/moving
unique ID
FILE SYSTEM
how an OS
store
arrange
access
DATA on a storage device - eg: HDD
PARTITION
physical separate area
lowest, fundamental level
on disk structure
support
1 file system
1 blocking factor
BLOCKING FACTOR
the smallest addressable area on disk
effect
the larger the blocking factor
the fewer i-nodes
the smaller the i-node table.
the smaller the blocking factor
the more i-nodes
the larger the i-node table
BLOCK
DEF
smallest addressable unit on a storage device
feature
where read/write operations are performed
files must start on block boundary
1 block =< file
FRAGMENTATION
large file = many blocks
scattered around the disk
MBR
special type of boot sector
at the very beginning of PARTITIONED mass storage devices
eg: not floppy disk
contains
how logical partitions are organised
exe code => load the installed OS
SWAP
special file system
aid in refer-paging
= fast swapping between RAM & disk
FILE INDICES
UNIX
inodes
HOT FIX
WINDOWS FILE SYSTEM
FAT16
max partition = 2GB
win 9x
FAT 32
64kb cluster
NTFS
512 bytes cluster
journaling file system
UNIX FILE SYSTEM
different disk types
DEVICE
manipulate data
around Unix environment
/dev
driver for device
Floppy Disk
/dev/fd0
CD-ROM
/dev/cdrom
IDE
SATA/SCSI/USB
Mouse
/dev/mouse
mounting
fixed file system
/mnt
removable file system
/media
TYPICAL STORAGE DEVICE
HDD disk drive
old-fashion standard
connected to slow IDE controller
Serial ASA disk drive
faster through-out
small connector
better air circulation
eSATA
used externally like an USB flash drive
SCSI disk drive
based SCSI controller card
substaintially faster
the generation of SCSI controller card
determine no. of disks available on a single BUS
Fire-wire disk drive
USB flash drive
handled by USB controller
USB
1.5 MBit/s
USB 2.0
12MBit/s - 480MBit/s
USB 3.0
4GBit/s
READ/WRITE DISK I/O
READ
identify starting block
move head to starting block
wait for head to settle at starting block
read data from starting block -> RAM
check if file use more blocks
go to next block
read next block -> RAM
WRITE
find empty blocks