lenny@icus.UUCP (Lenny Tropiano) (01/24/88)
In article <2700@pbhyf.UUCP> tlh@pbhyf.UUCP (Lee Hounshell) writes: |>In article <144800017@occrsh.ATT.COM> rjd@occrsh.ATT.COM writes: |> > On the same note: I was a little fuzzy why fsck required already-made |> >but empty directory entries or allocated blocks. I seem to recall that |> >my lost+found directory was 32 characters (the minimum, just the . and .. |> >entries) prior to fsck being run and finding 5 disconnected files that |> >were reconnected just fine (I happened to have an ls -l output of the |> >/ filesystem before the crash which showed the 32 character lost+found |> >entry). I will grant that Berkley unix may need the entries, but is this |> >really true for AT&T System V? |> |>Yeah.. so was mine, and fsck reconnected about 10 files for me with no |>problems about 3 weeks ago. I suspect that the directory slot stuff is |>only specific to Berkeley unix.. it certainly isn't needed for the 3B1. |>comments? |> Agreed. When I first wrote the article about making the /lost+found directory, I never knew about allocating blocks/entries. In fact the way I found the fsck "reconnected" files is from the fsck output saying: "(RECONNECTED)". I never allocated blocks and it did it anyway, so it might only be specific to Berkeley UNIX and not related System V. -Lenny -- ============================ US MAIL: Lenny Tropiano, ICUS Computer Group IIIII CCC U U SSSS PO Box 1 I C C U U S Islip Terrace, New York 11752 I C U U SSS PHONE: (516) 968-8576 [H] (516) 582-5525 [W] I C C U U S AT&T MAIL: ...attmail!icus!lenny TELEX: 154232428 IIIII CCC UUU SSSS UUCP: ============================ ...{uunet!godfre, harvard!talcott}!\ ...{ihnp4, boulder, mtune, bc-cis, ptsfa, sbcs}! >icus!lenny "Usenet the final frontier" ...{cmcl2!phri, hoptoad}!dasys1!/