Path: utzoo!attcan!uunet!decwrl!shelby!rutgers!cbmvax!steveb From: steveb@cbmvax.commodore.com (Steve Beats) Newsgroups: comp.sys.amiga.tech Subject: Re: Validation error hack and question (was: Re/Write Error) Message-ID: <13787@cbmvax.commodore.com> Date: 14 Aug 90 09:53:47 GMT References: <290.26B9C50B@afitamy.fidonet.org> <13759@cbmvax.commodore.com> Reply-To: steveb@cbmvax (Steve Beats) Organization: Commodore, West Chester, PA Lines: 19 In article Chuck.Phillips@FtCollins.NCR.COM (Chuck.Phillips) writes: > >Is it possible to write a program that will simply close every open file on >a device? (Possibly prompting the user interactively) DiskDoctor seems like >extreme overkill to handle these cases; it also has the effect of >undeleting lots of files I really don't want to have to clean up again. Under 2.0 files that are left open are no different from files that have been closed. While there will be a lock and a filehandle hanging around (preventing other processes from deleting/modifying the file) the format on disk is identical. 2.0 does all updates on the disk copy of the fileheader and bitmap so that the file is never in an unknown state. 1.3 and previous versions of the FS kept the fileheader and bitmap information in memory, only flushing it out when the file was closed. This was the prime cause of many of the "key already set" requesters after a crash. Rebooting the computer will release all hanging filehandles and locks. Steve