Harald Schmalzbauer wrote: > Am 23.02.2010 19:14, schrieb Alexander Motin: >>> I'll restore the default vfs.zfs.txg.timeout=30, so the hang can be >>> easily reproduced and see if I can 'camcontrol stop' the drive. Do you >>> think I can get usefull information with that test? >> Stop won't work for ATA devices. It is SCSI command. And all it does - >> stops spindle. It won't destroy device. AFAIK there is no method in CAM >> now to manually disable some device on-flight. If some device half-died, >> the best way is to mechanically disconnect it. It will help CAM to >> recover as fast as possible. > > Thank you very much again. I wasn't aware of that. I thought 'camcontrol > stop' is similar to 'atacontrol detach'. > It's important for me te be able to manage my systems rmotely, so I need > to stay with the old ataahci driver. The detach feature has been > life-saver several times for me, especially with IDE disks. I often had > drives going nuts and detach/attach with gmirror/graid3 rebuild always > solved the problem. I expect to see also SATA drive oddities (maybe like > now) when they replace the old ide servers.
gmirror and graid3 allow you to remove failed component from array, add new or resync without detaching devices from the system. I don't see problem there, sufficient to migrate back. > One last quick question: I read about a new feature adopting old ata to > cam. Do you have a link to useful information? Or will a mailman search > list all useful info. It's really simple. Add `options ATA_CAM` to the kernel and you are there. Everything the same as with loading ahci(4) (adX -> adaX, acdX -> cdX, ...), just without NCQ. Then you could remove all ata(4) peripheral device drivers from the kernel, as they become useless. atacontrol is also deprecated in this mode. -- Alexander Motin _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
