From owner-freebsd-hackers Mon May 6 19:00:22 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA28893 for hackers-outgoing; Mon, 6 May 1996 19:00:22 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA28886 for ; Mon, 6 May 1996 19:00:17 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id LAA18048; Tue, 7 May 1996 11:33:15 +0930 From: Michael Smith Message-Id: <199605070203.LAA18048@genesis.atrad.adelaide.edu.au> Subject: Re: dosfsck anyone? To: terry@lambert.org (Terry Lambert) Date: Tue, 7 May 1996 11:33:15 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, terry@lambert.org, rnordier@iafrica.com, hackers@FreeBSD.org In-Reply-To: <199605070122.SAA22485@phaeton.artisoft.com> from "Terry Lambert" at May 6, 96 06:22:39 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Terry Lambert stands accused of saying: > > > > 1) There is a limit on the number of entries in "/" on DOS FS's > > > that isn't enforced on subdirectories. > > > > > > a) If you don't use "lost+found", you risk exceeding > > > this limit. > > > > I don't think _not_ using it is an option. > > Works not having one under DOS... "works" in what context? If you mean "chkdsk works without one", then I suggest you consider what happens when it tries to create too many .chk files. These aren't actually much use anyway. Using a heirachy under a lost+found directory gives you some chance of segregating the victims of seperate corruptions, which may help a little in reconstruction. I think that most people faced with serious FAT FS corruption would just blow it away and restore/reinstall, so the aim is not to intuit magical details, but just to get the FS in a consistent state. > I liked the idea of handling crosslinks by deconstruction rather > than lost+found. The problem being that the deconstruction is almost certain to be wrong. > Sorry; I just got off a project doing a network redirector for > Win95, and they were all faked. Shouldn't have assumed. 8-(. Fair enough 8) The only useful think about '..' is that it points to the starting cluster of the parent directory. > What about ".." in "/"? There isn't one 8) > > > How will these anomolies be introduced? By (in violation of usage > > > semantics) caching? > > > > No. By the potential operation of the 'dosfsck' program, as stated in > > the preceeding paragraph. > > How does a cross-link get created is what I was asking...? Ah. I don't think we're expecting any to be created by the new DOSFS, but you'll get them under DOS if 'smartdrive' loses its marbles, or if a program with a rogue pointer scribbles on DOS' buffers, or if some twonk hits RESET while the FAT is being updated, or if DOS/Win/whatever takes a dive while the FAT is in an inconsistent state. None of the MS FAT filesystem drivers seem to place much emphasis on maintaining filesystem consistency. > Terry Lambert -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[