Abstract
DACO is a proposal to provide disk head separation so that a Read-Modify-Write to update check blocks in RAID arrays with erasure encoding can be processed with a minimal rotational delay. Aside from the difficulty associated with implementation of such R/W heads, there are various reasons why such a disk architecture which runs contrary to the write verify SCSI (read after write) command is not highly desirable. DACO is not utilized by the Disk Array Controller in XORing data from multiple disks and processing updates to prevent write holes. We discuss alternate methods to cope with the small write penalty and quantify the effect of DACO on performance via a simple queueing analysis.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
