Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!hplabs!pyramid!voder!wlbr!pete
From: pete@wlbr.EATON.COM (Pete Lyall)
Newsgroups: comp.sys.m6809
Subject: Re: Poisonous File Bug in Level 2
Message-ID: <1123@wlbr.EATON.COM>
Date: Fri, 28-Aug-87 19:20:10 EDT
Article-I.D.: wlbr.1123
Posted: Fri Aug 28 19:20:10 1987
Date-Received: Sun, 30-Aug-87 06:22:14 EDT
References: <1939@ihwpt.ATT.COM>
Reply-To: pete@wlbr.UUCP (0000-Pete Lyall)
Organization: Eaton IMS, Westlake Village, CA
Lines: 29
Keywords: funny files hang windows

In article <1939@ihwpt.ATT.COM> knudsen@ihwpt.ATT.COM (mike knudsen) writes:
>In the last couple of days, My Coco-3 Level 2 system
>has taken to creating "poison files."
>
>The symptoms of a poison file are that any attempt to
>List or even Delete it will cause that window to hang.

Mike,

Sounds a lot like file busy stuff - error #253. This and related
symptoms can be caused by either a non-sharable file, or a file 
opened for write, etc. The file lengths of 0, $2000, $4000, etc. that
you are seeing are products of the RBF manager value IT.SAS which
preallocates that much space ($2000 = 32  sectors.. common for an HD)
on each request for additional disk real estate.

Now *why* you're getting into a busy files scenario, I don't know.
Shell redirection to a file causes locking and blocking on that file.

The bottom line is, if it's a NEW problem, and if it occurs primarily
after the machine warms up, and you have altered nothing else ( i.e.
rewritten RBF...), then you probably *do* have a hardware problem.


-- 
                                                   Pete Lyall

Usenet:     {trwrb, scgvaxd, ihnp4, voder, vortex}!wlbr!pete
Compuserve: 76703,4230 (OS9 Sysop) OS9 (home): (805)-985-0632 (24hr./1200 baud)