On 19 Jan, Stefan Esser wrote:
> I seem to remember, that drives of that time required the write cache
> to be enabled to get any speed-up from tagged commands. This was no
> risk with SCSI drives, since the cache did not make the drives lye
> about command completion (i.e. the status for the wri
On 18 Jan, Wojciech Puchar wrote:
> If computer have UPS then write caching is fine. even if FreeBSD crash,
> disk would write data
I've had my share of sudden UPS failures over the years. Probably more
than half have been during an automatic battery self test. UPS goes on
battery, and then *b
On Jan 19, 2013, at 4:33 PM, Wojciech Puchar
wrote:
>> to be enabled to get any speed-up from tagged commands. This was no
>> risk with SCSI drives, since the cache did not make the drives lye
>
> i see no correlation between interface type and possibility of lying about
> command completion.
to be enabled to get any speed-up from tagged commands. This was no
risk with SCSI drives, since the cache did not make the drives lye
i see no correlation between interface type and possibility of lying about
command completion.
___
freebsd-hackers
Stefan writes:
> I seem to remember, that drives of that time required the write cache
> to be enabled to get any speed-up from tagged commands. This was no
> risk with SCSI drives, since the cache did not make the drives lye
> about command completion (i.e. the status for the write was only
> retu
I remember those drives from some 20 years ago. Before that time, SCSI
and IDE drives were independently developed and SCSI drives offered way
yes. 20 years ago it was true. even in 1995, when i had SCSI controller in
my 486 and it was great compared to ATA.
today SATA and SAS are mostly the
Am 19.01.2013 00:32, schrieb Karim Fodil-Lemelin:
> * Although no one has reported problems with the 2 gig
> * version of the DCAS drive, the assumption is that it
> * has the same problems as the 4 gig version. Therefore
> * this
Hi,
Some time ago Stanislav Sedov suggested to me extending libprocstat(3)
with functions to retrieve process command line arguments and
environment variables.
In the first approach I tried, the newly added functions
procstat_getargv/getenvv allocated a buffer of necessary size, stored
the values
Turning the write cache off eliminates the risk of having the write cache
on.
this sentence sounds like "not having a car eliminates a risks of
driving".
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hac
9 matches
Mail list logo
