Up to [cvs.NetBSD.org] / src / sys / dev / raidframe
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: netbsd-6-0-RC2
Revision 1.33.8.1 / (download) - annotate - [select for diffs], Thu Feb 23 02:22:05 2012 UTC (12 years, 1 month ago) by riz
Branch: netbsd-6
CVS Tags: netbsd-6-1-RELEASE,
netbsd-6-1-RC4,
netbsd-6-1-RC3,
netbsd-6-1-RC2,
netbsd-6-1-RC1,
netbsd-6-1-5-RELEASE,
netbsd-6-1-4-RELEASE,
netbsd-6-1-3-RELEASE,
netbsd-6-1-2-RELEASE,
netbsd-6-1-1-RELEASE,
netbsd-6-1,
netbsd-6-0-RELEASE,
netbsd-6-0-RC2,
netbsd-6-0-RC1,
netbsd-6-0-6-RELEASE,
netbsd-6-0-5-RELEASE,
netbsd-6-0-4-RELEASE,
netbsd-6-0-3-RELEASE,
netbsd-6-0-2-RELEASE,
netbsd-6-0-1-RELEASE,
netbsd-6-0,
matt-nb6-plus-nbase,
matt-nb6-plus-base,
matt-nb6-plus
Changes since 1.33: +10 -2
lines
Diff to previous 1.33 (colored) next main 1.34 (colored)
Pull up following revision(s) (requested by oster in ticket #23): sys/dev/raidframe/rf_reconstruct.c: revision 1.118 sys/dev/raidframe/rf_reconmap.c: revision 1.34 comment, and effectively remove, a DIAGNOSTIC check that is invalid for RAID5_RS. Add logic to the main reconstruction loop to handle RAID5 with rotated spares. While here, observe that we were actually doing one more stripe than we thought we were, and correct that too (it didn't matter for non-RAID5_RS, but it definitely does for RAID5_RS). Add some bounds-checking at the beginning to handle the case where the number of stripes in the set is smaller than the sliding reconstruction window. XXX: this problem likely needs to be fixed for PARITY_DECLUSTERING too.