From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17591 invoked from network); 29 Dec 2021 21:21:12 -0000 Received: from minnie.tuhs.org (45.79.103.53) by inbox.vuxu.org with ESMTPUTF8; 29 Dec 2021 21:21:12 -0000 Received: by minnie.tuhs.org (Postfix, from userid 112) id 88F6D9D003; Thu, 30 Dec 2021 07:21:08 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id A60ED9CEBE; Thu, 30 Dec 2021 07:20:49 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=ccc.com header.i=@ccc.com header.b="IOIuWTM7"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 4562E9CEBE; Thu, 30 Dec 2021 07:20:47 +1000 (AEST) Received: from mail-qv1-f48.google.com (mail-qv1-f48.google.com [209.85.219.48]) by minnie.tuhs.org (Postfix) with ESMTPS id 906359CE9F for ; Thu, 30 Dec 2021 07:20:46 +1000 (AEST) Received: by mail-qv1-f48.google.com with SMTP id o10so20312576qvc.5 for ; Wed, 29 Dec 2021 13:20:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ccc.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Sc3ECRtXpMCILAuq8OhJGQLKLAgmpWNHrr1I8NyqQuw=; b=IOIuWTM7gxfrGQVjZ8JaRnOi987zE99qOUdqvnI3cyQfnKaVDIXVZePxdCLDg+XEJG cejvVKCaBjO05Xm8O2sxfs1FY12Ly5MiUAzfFNqjlLzG/Fqv8EtWs8NNysUZ0KyQ8k0h ms6tOZj6IaDVr5sw1eUU6pCcnsu+Xiw36QWEk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Sc3ECRtXpMCILAuq8OhJGQLKLAgmpWNHrr1I8NyqQuw=; b=YEvUwqGYNy2uNimzHLt9rnt4TuxSJOX2eLLH/2g7VSJOIaJIVkJELkyufL6IiOpFNt 3rIYIWNKGJ0R1B07IIiqNh97KhJqziTy3CdXfogYWaw/qc5PdSeUdbZB5CmNI1EYL3LN S9Ax9ywxqp/FOOSVxoA09wCwZ4lXGG4C6uOeoBY3y2hqP7TkwV0V5LfhS7ms6aj6YQYI TczUw3VZoE0f0KKvMTUbpQqArZrJodGbWbSVVvw+V/k+XCrmUL0t31neCaWPTzQB2Mvg iG8JUm0n7o6L2+oCd1htIrFCqYKSIr/0GxfUX5DZX75is2SOiugJ5Gm0kzJJcF2CpH9a ASUw== X-Gm-Message-State: AOAM533fzPR4UXM74NYR2IJZlgz5B2oDPl3V7yCX7ePlp6l2CIMoDqxi BBODk/4y7ZASmQJWCPt0UnirCxDTk5eUl5J/m72O5Q== X-Google-Smtp-Source: ABdhPJzu0lfDLa2j+Ngdc1R2egG3EO9jdUNc9BvfShs+YK69vQNpgppywRWAQdi7n8qzL/7oaqoQ8OTwpffZaP8omIM= X-Received: by 2002:a05:6214:2aac:: with SMTP id js12mr25285173qvb.38.1640812845538; Wed, 29 Dec 2021 13:20:45 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Clem Cole Date: Wed, 29 Dec 2021 16:20:19 -0500 Message-ID: To: Dan Cross Content-Type: multipart/alternative; boundary="000000000000cd3c7805d44f82ff" Subject: Re: [TUHS] moving directories in svr2 X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: TUHS main list , Douglas McIlroy Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" --000000000000cd3c7805d44f82ff Content-Type: text/plain; charset="UTF-8" On Wed, Dec 29, 2021 at 3:59 PM Dan Cross wrote: > Did `icheck` and friends have something analogous to the `lost+found` > directory created by `fsck`? > The lost+found directory was a tjk-ism although I can get a very small level of credit/inspiration. It was born of need. Ted was explaining to me one night that one of the issues when you had identified a file that no directory was claiming was what to do with it. Originally, Ted linked lost files into root because there was usually only a couple of files, but ... we startiong seeing a situation where often the root directory did not have free directory slots. Some of the folks (I want to say it was either bio-med or architecture dept) had a recurring crash that occurred after a bunch of intermediate files had been created on a long running program. If the program stopped we had a way of restarting it part way using them. The problem was that people did not clean up the /tmp directory so the program unlinked them after creating them. But if it crashed, the files were still there but just connected to anything. Ted could find them with f*ck [it had a different name then]. I remember that we talked more about the issue and he came up with the idea of creating the directory lost+found and then preallocating a bunch of slots with a shell script instead of hoping the root directory was going to being available. --000000000000cd3c7805d44f82ff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Dec 29, 2021 at 3:59= PM Dan Cross <crossd@gmail.com&= gt; wrote:
Did `icheck` and friends have somethin= g analogous to the `lost+found` directory created by `fsck`?=C2= =A0
The=C2=A0lost+found directory was a tjk-ism although= I can get a very small level of credit/inspiration.=C2=A0 It was born of n= eed. =C2=A0 Ted was explaining to me one night that one of the issues when = you=C2=A0had=C2=A0identified a file that no directory was claiming was what= to do with it.=C2=A0 Originally, Ted linked lost files into root because t= here was usually=C2=A0only a couple of files, but ... we startiong seeing a= situation where often the root directory did not have free directory slots= .

Some of the folks (I want to=C2=A0say it was either = bio-med or architecture dept) had a recurring crash that occurred after a b= unch of intermediate files had been created on a long running program.=C2= =A0 If the program stopped we had a way of restarting it part=C2=A0way usin= g them. =C2=A0 The problem was that people did not clean up the /tmp direct= ory so the program unlinked them after creating them.=C2=A0 But if it crash= ed, the files were still there but just connected to anything. =C2=A0 Ted c= ould find them with f*ck [it had a different name then].=C2=A0

=
I remember that we talked more about the issue and he came up with= the=C2=A0idea of creating the directory lost+found and then preallocating = a bunch of slots with a shell script instead of hoping the root directory w= as going to being available.
--000000000000cd3c7805d44f82ff--