atactl parity w/scsictl? (enable SATA write cache?)

2017-08-10 Thread John D. Baker
I came into possession of a couple of SATA disks which appear to have their write caches disabled. 'atactl wdN identify' reports, in part: [...] Device supports following standards: ATA-1 ATA-2 ATA-3 ATA-4 ATA-5 ATA-6 ATA-7 Command set support: READ BUFFER command (enabled) WRITE

Re: atactl parity w/scsictl? (enable SATA write cache?)

2017-08-10 Thread Jonathan A. Kollasch
On Thu, Aug 10, 2017 at 08:29:19AM -0500, John D. Baker wrote: > I came into possession of a couple of SATA disks which appear to have > their write caches disabled. 'atactl wdN identify' reports, in part: You're probably looking for dkctl(8)'s getcache and setcache. Jonathan Kollasch

Re: atactl parity w/scsictl? (enable SATA write cache?)

2017-08-10 Thread John D. Baker
On Thu, 10 Aug 2017, Jonathan A. Kollasch wrote: > You're probably looking for dkctl(8)'s getcache and setcache. Thanks! That was it. (too many XXXctl tools...) Now to see if that makes a difference. (There's still the possibility of OEM-crippled firmware making it misbehave unless it gets th

Re: atactl parity w/scsictl? (enable SATA write cache?)

2017-08-10 Thread John D. Baker
On Thu, 10 Aug 2017, John D. Baker wrote: > Now to see if that makes a difference. (There's still the possibility > of OEM-crippled firmware making it misbehave unless it gets the secret > handshake from the OEM's RAID controller.) That helped and sped up the write by a factor of 8.73. The cach

Re: atactl parity w/scsictl? (enable SATA write cache?)

2017-08-10 Thread Michael van Elst
jdba...@mylinuxisp.com ("John D. Baker") writes: >I'd like to use them as ordinary disks, so having the write caches >enabled would be nice. Is there any way to do that with tools in >base? dkctl wd0 setcache rw -- -- Michael van Elst Internet: mlel...@serpens

Re: Hypervisor advice

2017-08-10 Thread Andy Ruhl
On Wed, Aug 9, 2017 at 5:19 PM, Greg Troxel wrote: > I have been using xen, with the packages from pkgsrc, on NetBSD since > 2005ish. It has been totally solid. Any semi-recent AMD or Intel > processor will be fine. See the xen howto for more discussion: > > https://wiki.netbsd.org/ports/xen/ho