User talk:90.223.203.193
From my perspective the statement about
"that supports large, high-performance ... quick restarts without lengthy consistency checks in the event of a crash or power failure" holds true, and doesn't require the caveat in brackets.
The only time WAFL check was required is when a panic is caused by detection of filesystem inconsistency, which for the most part is caused by hardware events such as multiple simultaneous disk failures, or faulty interconnects long after data has been committed to stable storage.
Additionally, in modern ONTAP implementations (7.3.1 onwards), WAFL check has been replaced with a different consistency repair tool (WAFL Iron with Optional Commit) which returns service levels generally within minutes while a background check of the remaining data continues. The maximum size of a WAFL aggregate is designed to keep the time taken for a worst case these background phases to under 24 hours.
April 2013
[edit]
Hello, I'm Webclient101. I wanted to let you know that I undid one of your recent contributions, such as the one you made with this edit to Ping (networking utility), because it didn’t appear constructive to me. If you think I made a mistake, or if you have any questions, you can leave me a message on my talk page. Thanks, Webclient101talk 14:31, 13 April 2013 (UTC)
 | This is the discussion page for an IP user, identified by the user's IP address. Many IP addresses change periodically, and are often shared by several users. If you are an IP user, you may create an account or log in to avoid future confusion with other IP users. Registering also hides your IP address. |