RAID0

References

1. ^ 2025.
2. ^ 2025.
3. ^ 2015.
4. ^
5. ^.{{}}: |last= has generic name ()
6. ^
7. ^ 185. CiteSeerX 10.1.1.41.3889. doi:10.1145/176979.176981. S2CID 207178693.{{}}: Cite uses deprecated parameter |citeseerx= ()
8. ^.
9. ^.
10. ^.
11. ^.
12. ^
13. ^ .
14. ^ .
15. ^.
16. ^ .
17. ^ .
18. ^ 2019.
19. ^
20. ^
21. ^
22. ^.
23. ^
24. ^.
25. ^.
26. ^ 2021.
27. ^ 129.
28. ^ 2021. Last valid archived webpage at Wayback Machine
29. ^.
30. ^.
31. ^.
32. ^
33. ^
34. ^
35. ^
36. ^ .
37. ^
38. ^
39. ^ . Proceedings of the 1988 ACM SIGMOD international conference on Management of data - SIGMOD '88. p. 112. doi:10.1145/50202.50214. ISBN . S2CID 52859427 2022. A single parity disk can detect a single error, but to correct an error we need enough check disks to identify the disk with the error. [...] Most check disks in the level 2 RAID are used to determine which disk failed, for only one redundant parity disk is needed to detect an error. These extra disks are truly "redundant" since most disk controllers can already detect If a dusk failed either through special signals provided in the disk interface or the extra checking information at the end of a sector
40. ^ . Intel.com. Intel. p. 10.
41. ^ 5. doi:10.1109/LISAT.2013.6578246. ISBN .
42. ^ . USENIX: Hotstorage.
43. ^ 168. doi:10.1016/j.ipl.2004.10.009.
44. ^ 405. doi:10.1007/978-3-319-09465-6_41. ISBN .{{}}: |journal= ignored ()