Path: utzoo!mnetor!uunet!husc6!bbn!aoa!mbr
From: mbr@aoa.UUCP (Mark Rosenthal)
Newsgroups: comp.unix.wizards
Subject: Re: How does filling a disk to capacity affect performance?
Message-ID: <182@aoa.UUCP>
Date: 13 Apr 88 17:59:07 GMT
References: <460@osupyr.mast.ohio-state.edu> <92@iravcl.ira.uka.de> <1508@se-sd.sandiego.NCR.COM>
Reply-To: mbr@aoa.UUCP (Mark Rosenthal)
Organization: Adaptive Optics Assoc., Cambridge, Mass. USA
Lines: 16

In article <1508@se-sd.sandiego.NCR.COM> rns@se-sd.sandiego.NCR.COM (Rick Schubert) writes:
>"cp" may be "dumb" (not meant to be derogatory to "cp" or to people who
>are unable to speak) enough not to check whether or not a write was successful
>(I haven't bothered to test whether or not it is because that's not my point),
>but it doesn't have the permission to start writing over blocks that are not
>free

Just a side note.  As I understand it, checking the return value of write()
does not really tell you what you want to know, due to the fact that write's
happen asynchronously.  All the return value can tell you is whether the data
was successfully copied into the kernel's buffer.  Then when the disk is not
busy and kernel gets around to it, the actual write happens, by which time your
process is off doing other things, or perhaps has already exited.
-- 
	Mark of the Valley of Roses
	...!{harvard,ima}!bbn!aoa!mbr