Which I/O scheduling algorithm can potentially lead to starvation of certain I/O requests, particularly those located far from the current head position?

Shortest Seek Time First (SSTF) is an I/O scheduling algorithm that selects the I/O request closest to the current position of the disk head. While this algorithm minimizes seek time, it has the drawback of potentially causing starvation for requests that are far from the current head position. This happens because the algorithm keeps prioritizing closer requests, leaving distant requests unserviced for long periods of time. For example, if there are many requests close to the current head position, a request far away might never get serviced because closer requests keep appearing, which leads to starvation. Although SSTF improves overall efficiency by minimizing seek time, its potential to starve distant requests is a significant disadvantage. Why Other Options Are Wrong: A) FCFS: FCFS services requests in the order they arrive, ensuring fairness but potentially leading to high seek times. C) SCAN: SCAN moves the disk arm across the disk, servicing requests along the way, reducing the likelihood of starvation. D) C-SCAN: C-SCAN treats the disk as a circular buffer, which improves fairness and reduces the risk of starvation. E) LOOK: LOOK is similar to SCAN but stops when there are no more requests in the current direction, also reducing the risk of starvation compared to SSTF.