Why is contiguous storage allocation less flexible than linked stoaage allocatio
ID: 3547331 • Letter: W
Question
Why is contiguous storage allocation less flexible than linked stoaage allocation?
The following shows the information for a file stored on disk using the contiguous allocation approach shown in class. Modify the table if block 6 is deleted from the file.
file starting address length
f1 3 4
The following shows a FAT of a file system. Modify the contents of the FAT if a new block is allocated to file f3 using the first-fit strategy shown in class.
file name starting address FAT
f1 4 0 6
f2 1 1 5
f3 7 2 -
3 8
4 eof
5 3
6 eof
7 0
8 eof
9 -
Use the LOOK strategy shown in class to show the arm movement history for the following disk requests. We assume the arm is currently moving toward the smaller track number side and the current position of the arm is at track 64.
38, 79, 27, 18, 54, 44, 91, 62
Use the C-SCAN strategy shown in class to show the arm movement history for the following disk requests. We assume the arm is currently moving toward the smaller track number side and the current position of the arm is at track 64.
38, 79, 27, 18, 54, 44, 91, 62
Explanation / Answer
Linked allocation is does not disk compaction required. Because of noncontiguous nature of allocation, the linking does not produce any external disk fragmentation. Any disk block on the free space can be used to satisfy a request, since all blocks are linked together. There is also no need of declaration of the size of a file in linked allocation while it is created. A file can continue to grow as there are free blocks. Consequently, it is never necessary to have disk compaction.
file name starting address FAT
f1 4 0 8
f2 1 1 5
f3 7 2 -
3 8
4 eof
5 3
7 0
8 eof
9 -
C-Scan works the way to the nearest end
Currently at 64 so
62,54,44,34,27,18,91,79
LOOK
62,54,44,34,27,18,79,91
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.