Nick Holland wrote on Sat, Jun 09, 2007 at 10:56:20PM -0400:
quoted text
> luccio01 wrote:
[...]
quoted text
>> And what do you think about stability of aac driver ?
>> Because I read it is not a good idea to use it ...
> 
> http://www.openbsd.org/faq/faq12.html#aac
> 
> do you care about your data?
> do you feel lucky?

For some more details, see

http://marc.info/?l=openbsd-misc&m=110384546229848
  and the following thread, in particular
    http://marc.info/?l=openbsd-misc&m=110417903607462
http://marc.info/?l=openbsd-misc&m=110540361502637
http://marc.info/?l=openbsd-misc&m=110005477128153
  and the following thread, in particular
    http://marc.info/?l=openbsd-misc&m=110580665416587
http://marc.info/?l=openbsd-misc&m=111180845207030
  and the following thread
http://marc.info/?l=openbsd-misc&m=112741307319043
  and the following thread, in particular
    http://marc.info/?l=openbsd-misc&m=112749851526934

In a nutshell:
Sometimes, the controller will just stop responding to SCSI
requests.  In these cases, it needs a firmware reboot.  This
firmware reboot needs up to two minutes to complete.  During
that time, you have no access to your data.
If the operating system is prepared to detect the firmware
failure condition, to initiate the firmware reboot and to wait
for up to two minutes before resuming normal operation, you
can work with the controller if you are willing to wait for
two minutes now and then.
If the operating system is not prepared to work around those
firmware crashes in the way described, it will hang or crash
or become unusable in some other way.

Of course, i'm not saying that's the only bug.
All i claim is: This is one bug which is certainly there.