can you answer 11a nad 11b..... a. Explain the difference between basic linked a

Question

can you answer 11a nad 11b.....

a. Explain the difference between basic linked allocation of file blocks and the file allocation table (FAT) block allocation scheme. b. The two most common methods for managing free space in a file system are bitmaps and linked free space lists. Give one benefit of bitmap over a linked free space list, and one benefit of a linked free space list over a bitmap. a. Explain why methods for ensuring reliability in file systems center on operations that write a single sector. b. A Linux variant called TxOS, developed at the University of Texas, supports transactions with shadowing by decomposing inodes into two parts: a header that contains infrequently modified data about each file, and a data component holding fields that are commonly modified by system calls. The header contains a pointer to the related data component, and the data component contains a pointer to the header. Explain how this inode organization makes it relatively easy to implement shadowing for changes to a file's metadata. a. Distributed file systems often allow nodes to cache local copies of shared data, using either write-through or write-back policies to handle changes to those data. List one benefit of using write-through file caching, and one benefit of using write-back file caching. b. A client process uses a binary search tree to store 2 set of 32-bit integers, one integer per node. The 32-bit address of the tree's root node is passed as the only argument to a remote procedure call to be executed in a server process. If the binary search tree contains 15 values, what is the minimum amount of space required to marshal the parameter or parameters of this function such that the remote procedure can access the entire binary search tree stored by the client? Show your work for full credit.

Explanation / Answer

11a)

The benefits of using write-through and write-back cache are given below.

1.write-through cache :
the "Write-through cache directs the write I/O on to a cache and through the underlying permanent storage before confirming I/O completion to the host network. and this will ensure the data updates are safely stored on.
for example: "the shared storage array", but it is having the disadvantage that I/O still experiences latency based on writing to that storage and Write-through cache is good for applications that write and then re-read data frequently as data is stored in cache and results in low read latency".

2.write-back cache :
the "Write-back cache is where write I/O is directed to the cache and its completion is immediately confirmed to the host. and this will result in the low latency and high throughput for write-intensive applications. but there is data availability exposure risk because the only copy of the written data is in the cache. we will come to this point later. the suppliers have added resiliency with products that duplicate writes. and the users will need to consider whether write-back cache solutions offer enough protection as data is exposed until it is staged to external storage. Write-back cache is the best performing solution for mixed workloads as both read and write I/O have similar response time levels".

Benefits :
1.the Latency will be reduced for active data, which results in higher performance levels for the applications.
2.the I/O operations to external storage are reduced as much of the I/O is diverted to the cache, and this will be resulting in lower levels of SAN traffic and contention for the SAN.
3.the Data can sit permanently on the external storage arrays or traditional storage, which will maintain the consistency and integrity of the data using features provided by the array, such as snapshots or replication.
4.the Flash is targeted at just the part of the workload that benefits from lower latency, resulting in a more cost-effective use of high $/TB storage.

Related Questions

Navigate

• Browse (All)
• Browse C
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.