OPERATING SYSTEMS

(CSE2005)
DIGITAL ASSIGNMENT-2
TEAMMATES:
1) SATWIK MOHANTY (17BCE1004)
2) UDESH KUMAR(17BCE1251)
3) VIRAJ SHAH (17BLC1169)

SUBMITTED TO: PROF. HARINI S.

TOPIC: DIFFERENTIATING FILE SYSTEMS AVAILABLE WITH RESPECT

TO SCALABILITY,PORTABILITY,PROTECTION AND SECURITY.
FILE SYSTEMS:

A file system controls how data is stored and retrieved. Without a file system, information placed in a
storage medium would be one large body of data with no way to tell where one piece of information stops
and the next begins. By separating the data into pieces and giving each piece a name, the information is
easily isolated and identified. Taking its name from the way paper-based information systems are named,
each group of data is called a "file". The structure and logic rules used to manage the groups of information
and their names is called a "file system".
There are many different kinds of file systems. Each one has different structure and logic, properties of
speed, flexibility, security, size and more.

FILE SYSTEMS SCALABILITY SECURITY PROTECTION RELIABILITY PORTABILITY

NTFS NTFS is streamlined In NTFS, each In the event that you NTFS is a NTFS is a bit nicer
for 4 KB groups, yet file or folder is are utilizing the recoverable record than FAT32 in
underpins a greatest assigned a NTFS document framework that many ways. It
bunch size of 2 MB. security framework you can ensures the supports filesystems
The most extreme descriptor that
control the entrance consistency of the up to 16EB in size,
NTFS volume defines its owner that clients are volume by utilizing and you can fill all
measure that the and contains two permitted to standard exchange of that space with a
particular can access control envelopes (and to the logging and single file, if you
bolster is 264 − 1 lists (ACLs). The records and recuperation want. (In other
groups, however not first ACL, called
discretionary
subfolders contained methods. In case of a words, there's
all executions inside them) by plate disappointment, effectively no limit
accomplish this access control
list (DACL), allotting NTFS NTFS reestablishes on file size other
hypothetical organizer consistency by than the size of the
defines exactly
maximum. The
what type of authorizations to running a containing
greatest NTFS interactions (e.g. clients and client recuperation filesystem.)
volume estimate reading, writing, gatherings. There are methodology that gets Filenames can be up
actualized in executing or
Windows XP
six authorizations to data put away in a to 255 characters
deleting) are that you can dole out: log document. The long, just like other
Professional is 232 − allowed or
1 bunches, halfway forbidden by
NTFS recuperation modern filesystems.
because of segment which user or method is definite, NTFS supports
table restrictions. groups of users. (1)Read: enables the ensuring that the POSIX-compatible
Utilizing the default For example, client to see volume is file ownership and
bunch size of 4 KB, files in the documents and reestablished to a permissions, hard
the greatest NTFS “C:\Program subfolders in the reliable state. and soft links, case-
volume measure is Files” folder organizer and view Exchange logging sensitivity, and
16 TB less 4 KB. Both may be read and envelope requires an extremely sparse files, all of
of these are executed by all little measure of which which make
users but
proprietorship,
tremendously higher consents and traits. overhead. it a lot more
than the 128 GB limit modified only by
interoperable with
in Windows XP SP1. a user holding
administrative Unix than
Since segment tables FAT32.Its main
privileges. (2)Write: enables the
on ace boot record drawback is that it's
Windows Vista client to make new
(MBR) circles bolster adds mandatory proprietary and
just segment sizes up records and
access control what support exists
to 2 TB, numerous info to DACLs.
subfolders inside the
has been reverse-
GUID Partition Table DACLs are the envelope, change engineered.
(GPT or "dynamic") primary focus of organizer Windows supports
volumes must be User Account characteristics and NTFS, since it came
joined to make a Control in view organizer from Microsoft
solitary NTFS volume Windows Vista
and later. The
possession and originally, back to
bigger than 2 TB. consents. Windows 2000 and
Booting from a GPT second ACL,
called system Windows NT 3.5.
volume to a Max OSX has had
access control
Windows domain in
list (SACL), (3)List Folder native read-only
a Microsoft defines which Contents: enables the support since 10.3
bolstered way interactions with
client to see the (Panther). Linux
requires a the file or folder
framework with names of records and can read and write
are to be audited NTFS volumes via
Unified Extensible and whether subfolders in the
Firmware Interface they should be envelope. NTFS-3G, which
(UEFI) and 64-bit logged when the runs in userspace
support.[17] The activity is (via FUSE). NTFS-
NTFS greatest successful, failed (4) Read and 3G doesn't give
hypothetical point of or both. For tremendous
Execute: enables the
confinement on the example, performance when
auditing can be client to peruse
measure of through envelopes to accessing SATA or
individual enabled on SAS disks, but
sensitive files of achieve different
documents is 16 EiB modern hardware is
a company, so documents and
(16 × 10246 or 264 more than capable
bytes) less 1 KB,
that its organizers, regardless
managers get to of whether the clients of keeping up with
which aggregates USB-attached disks.
know when don't have consent
18,446,744,073,709, someone tries to (At least for USB
550,592 bytes. With for those envelopes. It
delete them or
additionally enables 2.0; I haven't done
Windows 10 make a copy of comparisons with
rendition 1709 and them, and the client to perform
USB 3.0 hosts and
Windows Server whether he or activities allowed by
2019, the most she succeeds. the Read consent and disks.)
extreme actualized the List Folder
document measure Contents
is 8 PB short 2 MB or authorization.
9,007,199,252,643,8
40 bytes.
(5) Modify: enables
the client to erase the
organizer and
perform activities
allowed by the Write
consent and the Read
and Execute
authorization.

(6)Full Control:
enables the client to
change consents, take
possession, and erase
subfolders and
documents. It
additionally enables
the client to perform
activities allowed by
all different NTFS
organizer consents.
Executives,
proprietors of
 records or envelopes
and clients with Full
Control authorization
can allot NTFS
consents to different
clients and
gatherings.

(7)Deny: denies a
client record or
gathering all entrance
to an organizer and
denies the Full
Control
authorization.

FAT FAT32 just FAT neither has To protect the Updating the FAT FAT32 is often the
backings singular built-in data volume, two copies of table is very filesystem of choice
documents up to security the FAT are kept in important as well as for flash drives and
4GB in size and mechanisms case one becomes time consuming. If smaller media.
volumes up to 2TB nor supports damaged. In addition, the FAT table is not Windows, OSX, and
in size. For such the FAT tables and regularly updated, it Linux all have
instance, in the mechanisms the root directory can lead to data loss. native support for
must be stored in a It is time consuming it. It can span
event that you had which are built
fixed location so that because the disk read filesystems up to
a huge video into the
the system's boot files heads must be 2TB in its default
document over supported OS. can be correctly repositioned to the configuration and
4GB in size, you The fault- drive's logical track up to 16TB or so if
just couldn't spare tolerance located. zero each time the you tweak its block
it on the FAT32 mechanism is FAT table is updated. size. It cannot
record framework. poorly support files larger
on the off chance implemented than 4GB, nor does
that you had a 3TB in FAT32, so it include support
drive, you couldn't the percentage for file ownership
design it as a of data loss in and permissions. Its
support for
solitary FAT32 FAT32 is quite
filenames longer
segment. Being high. Different
than eight
developed by organizational characters plus a
Microsoft, NTFS is measures that three character
compatible in help to restrict extension is
almost all the the number of something of a
Windows people having hack. It's not case-
operating systems. access to sensitive (though it
In fact, the computer does preserve
compatibility goes equipment as case).Basically,
back till Windows well as the FAT32's biggest
XP. However, timely data strength is its cross-
when it comes to backup can platform support.
Mac OS X, the serve as In most other areas
NTFS file system protection it falls down when
has little mechanisms of compared to more
limitations. For data stored in modern filesystems.
It can be used in
one, Mac OS X can FAT32 In case
WIN
only read NTFS of the damage
NT/2K/XP/VISTA/7
drives, but can't of the FAT32 . Speaking of
write to them. On table as well as conversion, you
 the other hand, of the partition may easily convert a
MAC OS can not boot record, FAT32 system to
only read but also the file system NTFS. But the
write to FAT32 allows reverse is not true
drives. replacing them because NTFS
by their follows a secure
backups. protocol.

APFS(APPLE To give you an Apple File Apple File System is While HFS+ runs on all Two of the most
FILE System designed to avoid of Apple's current high-profile features
SYSTEMS) idea of how
natively metadata corruption devices, from Apple of APFS are
“state of the art” supports full caused by system Watch to Mac Pro, snapshots and
has changed disk crashes. Instead of there are differences clones.
since then, encryption, overwriting existing in how it's been
and file metadata records in implemented across Snapshots create a
consider this. encryption place, it writes those devices, read-only copy of
My first Mac, with the entirely new records, including key areas the system at that
which came out following points to the new like encryption. That single point in time.
late in 1984, options: ones and then means different It's initially more
releases the old ones. source code and space-efficient,
had 512 KB of no encryption This avoids corrupted separate maintenance because it doesn't
RAM (four times single-key records containing and development. duplicate any data
the original encryption partial old and partial APFS was designed to until changes begin
multi-key new data caused by a scale more to be made. It also
Mac’s memory)
encryption, crash that occurs consistently across means changes can
and a single where each file during an update. It Apple's platforms, be reverted.
floppy drive is encrypted also avoids having to now and into the Clones are copies of
that could store with a separate write the change future. That should "files" (both real
 400K. This key, and twice, as happens allow for a single code files and the Mac's
metadata is with an HFS+ base with fewer bundled folders-as-
computer I’m
encrypted with journaled file system, resources need to files). They're
writing from a different key. where changes are develop and maintain similarly more
now has 8 GB of written first to the it and allow it to grow space-efficient at
RAM – almost journal and then to faster and better. first, also not
the catalog file. duplicating data
16 thousand ti until changes are
mes more RAM made.
than my first This makes creating
Mac – and 512 both snapshots and
clones far faster and
GB of storage more efficient than
capacity. That’s making traditional
more than copies.
1.2 million time
s the size of
that first Mac.
ZFS A key design Hierarchical ZFS will automatically ZFS file systems can
element of the With Oracle
checksumming of all allocate data storage be moved to other
ZFS file system Solaris, the
data and metadata, across all vdevs in a pools, also on
is scalability. encryption
ensuring that the pool (and all devices remote hosts over
The file system capability in
entire storage system in each vdev) in a way the network, as the
itself is 128 bit, ZFS is
can be verified on use, that generally send command
allowing for 256 embedded into
and confirmed to be maximises the creates a stream
quadrillion the I/O
correctly stored, or performance of the representation of
zettabytes of pipeline.
remedied if corrupt. pool. ZFS will also the file system's
storage. All During writes,
metadata is a block may be Checksums are stored update its write state. This stream
allocated compressed, with a block's parent strategy to take can either describe
dynamically, so encrypted, block, rather than account of new disks complete contents
no need exists checksummed with the block itself. added to a pool, when of the file system at
to preallocate and then This contrasts with they are added. a given snapshot, or
inodes or deduplicated, many file systems As a general rule, ZFS it can be a delta
otherwise limit in that order. where checksums (if allocates writes across between snapshots.
the scalability of
The policy for held) are stored with vdevs based on the Computing the delta
the file system
encryption is the data so that if the free space in each stream is very
when it is first
created. All the set at the data is lost or corrupt, vdev. This ensures efficient, and its size
algorithms have dataset level the checksum is also that vdevs which have depends on the
been written when datasets likely to be lost or proportionately less number of blocks
with scalability (file systems or incorrect. data already, are changed between
in mind. ZVOLs) are given more writes the snapshots. This
Directories can created. The when new data is to provides an efficient
have up to wrapping keys be stored. This helps strategy, e.g., for
248 (256 trillion) provided by to ensure that as the synchronizing offsite
entries, and no the pool becomes more backups or high
limit exists on user/administr used, the situation availability mirrors
the number of ator can be does not develop that of a pool.
file systems or changed at any some vdevs become
the number of time without full, forcing writes to
files that can be taking the file occur on a limited
contained within system offline. number of devices. It
a file system.
The default also means that when
behaviour is for data is read (and
the wrapping reads are much more
key to be frequent than writes
inherited by in most uses),
any child data different parts of the
sets. The data data can be read from
encryption as many disks as
keys are possible at the same
randomly time, giving much
generated at higher read
dataset performance.
creation time. Therefore, as a
Only general rule, pools
descendant and vdevs should be
datasets managed and new
(snapshots and storage added, so that
clones) share the situation does not
data arise that some vdevs
encryption in a pool are almost
keys. A full and others almost
command to empty, as this will
switch to a make the pool less
new data efficient.
encryption key
for the clone or
at any time is
provided—this
does not re-
encrypt already
existing data,
instead
 utilising an
encrypted
master-key
mechanism.

DATABASE These type of Databases Since all the records Since all these files Since in the
systems store the have been will be stored in the will be stored in the database, it is
files or the largely database, under the form of a database, possible that the
contents of the secured protection of the without the records or the
files in the form of against database permission of a entries of different
a database, or in hackers administrator the database people may change
the form of a through netwo data present in the administrator, no one depending upon
hierarchical rk database will be safe can access the the people and the
structural security meas and secure against database, and also situation, so to
representation so ures such different kind of we can easily extract change them, the
that the data in as firewalls, users. the data which we database
the files or the and network- Without the want to find. So, administrator
files become based intrusio permission of the database file continuously has to
organised. Any n database systems along with update the
number of data detection syst administrator, no one the security, the data database so as to
which the user ems. While is allowed to get extraction and ensure that the
wants can be network access to the finding also becomes latest entries are
entered into the security database entries and easier. Also, the data fed into the
database. So, controls fields. in these file systems database. This
database file remain is abstracted and requires some kind
systems are valuable in unique, so that no of aa rework. So
scalable. this regard, two data are they are more
securing the repeated, or there is portable than the
database at least one factor other file systems.
systems differentiating two
themselves, same data. So these
and the systems are reliable.
programs/func
tions and data
within them,
has arguably
become more
critical as
networks are
increasingly
opened to
wider access,
in particular
access from
the Internet.
Furthermore,
system,
program,
function and
data access
controls, along
with the
associated
user
identification,
authentication
and rights
management
functions,
have always
 been
important to
limit and in
some cases
log the
activities of
authorized
users and
administrators
. In other
words, these
are
complementar
y approaches
to database
security,
working from
both the
outside-in and
the inside-out
as it were.

NETWORK A network file A distributed Distributed file Programs using local The difference
system is a file file system systems do not interfaces can between a
system that acts may also be share block level transparently create, distributed file
as a client for a created by access to the same manage and access system and
remote file software storage but use a hierarchical a distributed data
access protocol, implementing network protocol. Th directories and files store is that a
providing access IBM's Distribut ese are commonly in remote network- distributed file
to files on a ed Data known as network connected system allows files
server. These file Management file systems, even computers. These to be accessed
systems can Architecture ( though they are not file systems are using the same
handle a lot of DDM), in the only file systems extremely reliable in interfaces and
remote files at a which that use the network terms of creating semantics as local
time and makes programs to send directories and files files – for example,
them available on running on data. Distributed file so that even if the mounting/unmounti
our server which one computer systems can restrict computers are ng, listing
makes them use local access to the file connected through directories,
potentially interfaces and system depending networks even if at a read/write at byte
capable to semantics to on access remote distance, boundaries,
execute a lot of create, lists or capabilities o then too we can system's native
data at a time. manage and n both the servers access them. So permission model.
access files and the clients, these systems are Distributed data
located on depending on how extremely reliable. stores, by contrast,
other the protocol is require using a
networked designed. So different API or
computers. All according to the library and have
such client protocols assigned, different semantics
requests are different files are (most often those
trapped and protected. So, these of a database).
converted to systems are well Since they use a
equivalent protected. database, the
messages consistency of
defined by the multiple data is
DDM. Using maintained in these
protocols also systems, so they
defined by the are portable as
DDM, these they maintain the
messages are consistency of
transmitted to data.
 the specified
remote
computer on
which a DDM
server
program
interprets the
messages and
uses the file
system
interfaces of
that computer
to locate and
interact with
the specified
file.

TRANSACTIO In terms of Data stored in File locking cannot Transaction The difference
NAL scalability, which a transactional prevent TOCTTOU r processing between a
is the capacity of manner is not ace conditions on introduces distributed file
a system, secure. Data symbolic links. File the isolation guarant system and
network or a backup locking also cannot ee, which states that a distributed data
process to handle systems automatically roll operations within a store is that a
a growing amount typically do back a failed transaction are distributed file
of work, or the not provide operation, such as a hidden from other system allows files
potential of the support for software upgrade; threads on the to be accessed
system to direct backup this requires system until the using the same
accommodate of data stored, atomicity. So to transaction commits, interfaces and
that large amount which makes prevent such race and that interfering semantics as local
of work. In case recovery of conditions, we operations on the files – for example,
of transactional reliable and require protection. system will be mounting/unmounti
file systems, in consistent This protection can properly serialized wi ng, listing
case of a power data sets be provided through th the transaction. directories,
failure or when difficult. As a file system Transactions also read/write at byte
the system workaround, transactions. provide boundaries,
reaches an some the atomicity guarant system's native
unusable state database ee, ensuring that permission model.
then, after systems operations inside of Distributed data
recovery how simply a transaction are stores, by contrast,
much large the produce an either all committed require using a
file is, we can archived state or the transaction different API or
easily restore our file containing can be aborted and library and have
system and make all data up to the system discards different semantics
our system that point, and all of its partial (most often those
consistent. An the backup results. Due to of a database).
unusable partial software only atomicity property, Since they use a
install will not be backs that up transaction file database, the
left in the system. and does not systems are reliable. consistency of
So it can handle interact multiple data is
large amount of directly with maintained in these
works and handle the active systems, so they
a growing amount transactional are portable as
of network. In databases at they maintain the
terms of all. Recovery consistency of
scalability, the requires data.
transactional file separate
systems are recreation of
good. the database
from the state
file, after the
file has been
restored by
the backup
software.