I never really tested the performance, but it looks nice to use. We have a
small 3 node cluster running with AFD, so I still don't know what to expect
for large environments, since our core here runs on Exadata.
I think there is plenty of reasons to use it.
When the filter is enabled you can't mess up the disks either trying a
simple echo or dd command, even as root.
*Kind regards / Cordialmente / Saludos cordiales / Sincères amitiés / Mit
freundlichen Grüßen / Cordiali saluti,*
Franky Weber Faust
Oracle DBA
Skype: franky.faust
2017-03-16 17:52 GMT-03:00 Yong Huang <dmarc-noreply@xxxxxxxxxxxxx>:
According to
https://docs.oracle.com/database/121/OSTMG/GUID-E1E9DA6F-6E4B-427A-83AE-
7F9DFCE068D9.htm
"The [12c] Oracle ASM Filter Driver rejects any I/O requests that are
invalid. This action eliminates accidental overwrites of Oracle ASM disks
that would cause corruption in the disks and files within the disk group.
For example, the Oracle ASM Filter Driver filters out all non-Oracle I/Os
which could cause accidental overwrites."
That sounds like a good feature to a shop where such risk is not
negligible. But just like ASMLib, AFD relies on a kernel module, which may
be a hassel with frequent kernel update. I'm guessing people using ASMLib
will continue with AFD and those withour ASMLib will ignore AFD. What's
your opinion of it? Is the benefit worth all possible issues?
Yong Huang
--
//www.freelists.org/webpage/oracle-l
