Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Discuss] On Btrfs raid and odd-count disks

On Fri, Apr 12, 2013 at 10:51:21AM -0400, Derek Atkins wrote:
> Richard Pieri <richard.pieri at> writes:
> > Both ZFS and Btrfs provide facilities for automatically "erasing" write
> > holes. The process is called "scrubbing". The scrubbing process walks
> > through the entire file system tree, recalculates all file and metadata
> > checksums, and compares them to the stored checksums. Errors are
> > repaired using replica data. Oracle's documentation recommends a weekly
> > scrubbing schedule for consumer-grade disks and a monthly scrubbing
> > schedule for server-grade disks.
> Fair enough...  I don't know if standard (e.g. DM-level) RAID5 or RAID6
> provide for said "scrubbing"?  Or detecting/handling disk read or (or
> worse, disk write) failures.

Disk read and write failures are events which ought to be
reported by the disk interface. I've certainly seen enough of
them. There are occasions where they won't be, though... the one
time that happened to me, it was an earlyish 3Ware RAID card
that turned out to have problems with non-passive PCI risers.

mdadm has a sort of scrub facility available, in which it reads
all the bits -- see /sys/block/$array/md/sync_action 

Most HW RAID controllers have something similar available.


BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!

Boston Linux & Unix /