search for: nonrecoverable

...ading the whole slice for every random read. Only raid > systems like ZFS that use block checksuming can verify data on reads. > parity (or mirrors) are verified by doing 'scrubs' > > Further, even if a raid DID verify parity/mirroring on reads, this would > at best create a nonrecoverable error (bad data on one of the N drives > in the slice, no way of knowing which one is the bad one). > Thanks John, that's good information, something I didn't know. So I should think of RAID-5/6 parity as a mechanism for recovering from a drive fault that is more space-efficient th...

...he buffer (16MB vs 64MB on the SATA model), the same rotational speed, and costs 10% more than its enterprise SATA twin. (They also offer a Barracuda XT SATA drive; it''s roughly 20% less expensive than the Constellation drive, but rated at 60% the MTBF of the others and a predicted rate of nonrecoverable errors an order of magnitude higher.) Assuming I''m going to be using three 8-drive RAIDz2 configurations, and further assuming this server will be used for backing up home directories (lots of small writes/reads), how much benefit will I see from the SAS interface? -- Dave Pooser, ACSA M...

running b37 on amd64. after removing power from a disk configured as a mirror, 10 minutes has passed and ZFS has still not offlined it. # zpool status tank pool: tank state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear

Hey on Centos 5 hfsplus.ko is part of the Kernel: kernel-2.6.18-238.12.1.el5.x86_64 : The Linux kernel (the core of the Linux operating system) Repo : installed Matched from: Filename : /lib/modules/2.6.18-238.12.1.el5/kernel/fs/hfsplus/hfsplus.ko doing a yum provides "*/hfsplus.ko" on CentOS 6 finds nothing. What happened to hfsplus.ko on Centos 6? Thanks, Jerry

...than ICH5 (at least under Linux) 2. Reliability I have observed that frequent disk access with small files has destroyed ICH5 raid arrays in the past (at least under Linux) 3. Recovery I had a bad experience with the death of an Adaptec 3200S controller not long ago. The array was nonrecoverable because a replacement card could not be sourced in time. Additionally the firmware revision for the 3200s was unknown. (Recovery from controller death if even possible requires the same firmware revision as the original card, since that was not known we would have had to guess which takes t...