1. Assume that all data and metadata begin on disk. Assume further that all inodes are in separate blocks, and that each directory is only one block in size. How long (in term of D time units) does it take to open the file /a/b/c/d.txt? 2. Assume after opening the file, we read the file in its entirety. It is a big file, containing 1036 blocks. The inode itself has room for 12 direct pointers and 1 indirect pointer. Disk addresses are 4 bytes long, and disk blocks are 4KB in size. After opening it, how long does it take to read the entire file?
One problem with page-mapped FTLs is that they make the mapping tables too large
-
Assume you have a page-mapped FTL. If each entry in the FTL takes 4 bytes (assuming it is an array), how large is the FTL? Assume the SSD is only 1 MB in size, and uses 1 KB pages.
a) 1 KB
b) 4 KB
c) 1 MB
d) 4 MB
e) None of the above
A basic file systems, assume a simple disk model where each disk read of a block
takes D time units. Also assume the basic layout is quite like the very simple file system or (vsfs).
1. Assume that all data and metadata begin on disk. Assume further that all inodes are in separate blocks, and that each directory is only one block in size. How long (in term of D time units) does it take to open the file /a/b/c/d.txt?
2. Assume after opening the file, we read the file in its entirety. It is a big file, containing 1036 blocks. The inode itself has room for 12 direct pointers and 1 indirect pointer. Disk addresses are 4 bytes long, and disk blocks are 4KB in size. After opening it, how long does it take to read the entire file?
Please explain the answers
Step by step
Solved in 2 steps with 1 images
