M14_Wr的ites-Reads.pptVIP

NetApp – ? 2008, NetApp – All rights reserved Write and Read Request Processing Data ONTAP Fundamentals Objectives At the end of this module, you will be able to: Describe the writing and reading of data to and from a WAFL file system on a volume Describe the WAFL file system, including consistency points, RAID management, and storage levels Describe how RAID is used to protect disk data Describe how the WAFL file system processes write and read requests Data ONTAP Simplified Write Requests Write requests come into Data ONTAP through a variety of different interface protocols CIFS NFS FCP iSCSI HTTP WebDAV Write requests are buffered into System memory NVRAM Data Flow: Write Request – Write Buffer Consistency Point A completely self-consistent image of the file system Although dynamic, if the file system were frozen momentarily to capture its structure–that is a consistency point A consistency point is completed when designated data has been written to disk and a new root inode is determined A consistency point can occur in many different ways; two major methods are: One bank of the NVRAM card is full 10 seconds have elapsed Consistency Point (cont.) During a consistency point, Data ONTAP flushes writes to disk Always writes to new data blocks The volume is always consistent on disk When Data ONTAP flushes memory to disk It updates the file system “atomically” meaning that the entire write must complete or the entire write is rolled back This includes all metadata After checking, the NVRAM is cleared Data Flow: Write Request – WAFL to RAID Consistency Point (cont.) RAID layer calculates parity of the data to protect it from one or more disk failures The storage system can be configured as either: RAID 4 – allows one disk failure in the RAID group RAID-DP – allows up to two disk failures in the RAID group The RAID layer calculates parity to protect stripes of data If a data disk fails, the missing information can be calculated from parity Data Flow: Write Req