09.03.2015 Views

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

VSAN-Troubleshooting-Reference-Manual

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Diagnostics and <strong>Troubleshooting</strong> <strong>Reference</strong> <strong>Manual</strong> – Virtual SAN<br />

2. On the second read I/O, the data is returned from the read cache. This is a<br />

cache hit.<br />

3. The third I/O is a write. This now marks that range in the read cache line as<br />

invalid/dirty. A line in cache is a range of data blocks. When one block in the<br />

range changes, the whole range (or line) is marked as dirty. At this point, the<br />

data has not yet made it from the write buffer to the magnetic disk.<br />

4. The fourth I/O is another read, and it attempts to read a different block on<br />

the same cache line. This will be satisifed by the read cache. If the data block<br />

being read is not dirty, it can still be read from the read cache. This is<br />

considered a Read Cache Partial Hit as Virtual SAN does not know whether<br />

the data block it just read came from flash or magnetic disk.<br />

This will become clearer when we discuss a read of the dirty/invalid block.<br />

V M W A R E S T O R A G E B U D O C U M E N T A T I O N / 2 1 7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!