>>>>> "fc" == Frank Cusack <fcus...@fcusack.com> writes:
fc> why would dropping a flush cache imply dropping every write
fc> after the flush cache?
it wouldn't and probably never does. It was an imaginary scenario
invented to argue with you and to agree with the guy in the USB bug
who said ``dropping a cache flush command is as bad as dropping a
write.''
fc> oh. can you supply a reference or if you have the time, some
fc> more explanation? (or can someone else confirm this.)
I posted something long a few days ago that I need to revisit. The
problem is, I don't actually understand how the disk commands work, so
I was talking out my ass. Although I kept saying, ``I'm not sure it
actually works this way,'' my saying so doesn't help anyone who spends
the time to read it and then gets a bunch of mistaken garbage stuck in
his head, which people who actually recognize as garbage are too busy
to correct. It'd be better for everyone if I didn't do that.
On the other hand, I think there's some worth to dreaming up several
possibilities of what I fantisize the various commands might mean or
do, rather than simply reading one of the specs to get the one right
answer, because from what people in here say it soudns as though
implementors of actual systems based on the SCSI commandset live in
this same imaginary world of fantastic and multiple realities without
any meaningful review or accountability that I do. (disks, bridges,
iSCSI targets and initiators, VMWare/VBox storage, ...)
pgpkzKNL1NfqX.pgp
Description: PGP signature
_______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
