On Feb 3, 2010, at 3:15 PM, Aleksandr Levchuk wrote: > We switched to OpenSolaris + ZFS. RAID6 + hot spare on LSI Engenio san > hardware, worked well for us. (I'm used to the san management GUI. Also, > something that RAID-Z would not be able to do is: the san lights-up the amber > LEDs on the drives that fail, so I know which one to replace.)
In Solaris, lighting service LEDs is part of the FMA framework agents. When ZFS has repeated checksum failures from a device, it will notify FMA, which is responsible for diagnosis and subsequent service alerts. > So, I wanted to try to stick to the hardware RAID for data protection. I > understand that the end-to-end checks of ZFS make it better at detecting > corruptions. > > In my case, I can imagine that ZFS would FREEZ the whole volume when a single > block or file is found to be corrupted. No. > Ideally, I would not like this to happen and instead would like to get a log > with names of corrupted files. > > What exactly does happens when > zfs detects a corrupted block/file and does not have redundancy to correct it? It depends on the failmode property setting and how your application reading the file handles errors. In all cases, the "zpool status -xv" command can display the file name or metadata that is corrupted. -- richard _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
