From nobody Fri Sep 30 19:02:44 2022 X-Original-To: questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4MfKPK6s6yz4Y9wg for ; Fri, 30 Sep 2022 19:03:01 +0000 (UTC) (envelope-from 4250.82.1d4f30000abd3b9.f990a820291acc19ed61da0b52d6c794@email-od.com) Received: from s1-b0c6.socketlabs.email-od.com (s1-b0c6.socketlabs.email-od.com [142.0.176.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4MfKPJ6PClz3Bvd for ; Fri, 30 Sep 2022 19:03:00 +0000 (UTC) (envelope-from 4250.82.1d4f30000abd3b9.f990a820291acc19ed61da0b52d6c794@email-od.com) DKIM-Signature: v=1; a=rsa-sha256; d=email-od.com;i=@email-od.com;s=dkim; c=relaxed/relaxed; q=dns/txt; t=1664564581; x=1667156581; h=content-transfer-encoding:content-type:mime-version:references:in-reply-to:message-id:subject:to:from:date:x-thread-info:subject:to:from:cc:reply-to; bh=Hk4iSJfnYgg3qwICise/JH25m0R3fXwvMwfcqfl4Nxo=; b=qqGFXsJ4thOQwaERgBxjAR+C0jd5je0GZe8b+xitLycqv3bm1v0Wb+m69tF6G/xdtZKB/EI0UuT1aJdFRZwTeQNWC9olimX29F29QcKsNvVFnFTtwRDo2B5I+TsB3L5XlFjArFBYZD+7zIQ7/ogUr9VA60lz1MZjiFUSmlziRlk= X-Thread-Info: NDI1MC4xMi4xZDRmMzAwMDBhYmQzYjkucXVlc3Rpb25zPWZyZWVic2Qub3Jn Received: from r2.us-east-2.aws.in.socketlabs.com (r2.us-east-2.aws.in.socketlabs.com [142.0.189.2]) by mxsg2.email-od.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Fri, 30 Sep 2022 15:02:47 -0400 Received: from smtp.lan.sohara.org (EMTPY [185.202.17.215]) by r2.us-east-2.aws.in.socketlabs.com with ESMTP(version=Tls12 cipher=Aes256 bits=256); Fri, 30 Sep 2022 15:02:46 -0400 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.94.2 (FreeBSD)) (envelope-from ) id 1oeLHZ-0003PZ-2J for questions@freebsd.org; Fri, 30 Sep 2022 20:02:45 +0100 Date: Fri, 30 Sep 2022 20:02:44 +0100 From: Steve O'Hara-Smith To: questions@freebsd.org Subject: Re: mkdir error message -- what does this mean? Message-Id: <20220930200244.31d71c489812fd26c0d39769@sohara.org> In-Reply-To: References: X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.0) X-Clacks-Overhead: "GNU Terry Pratchett" List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4MfKPJ6PClz3Bvd X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=email-od.com header.s=dkim header.b=qqGFXsJ4; dmarc=none; spf=pass (mx1.freebsd.org: domain of 4250.82.1d4f30000abd3b9.f990a820291acc19ed61da0b52d6c794@email-od.com designates 142.0.176.198 as permitted sender) smtp.mailfrom=4250.82.1d4f30000abd3b9.f990a820291acc19ed61da0b52d6c794@email-od.com X-Spamd-Result: default: False [-1.70 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MV_CASE(0.50)[]; FORGED_SENDER(0.30)[steve@sohara.org,4250.82.1d4f30000abd3b9.f990a820291acc19ed61da0b52d6c794@email-od.com]; R_DKIM_ALLOW(-0.20)[email-od.com:s=dkim]; R_SPF_ALLOW(-0.20)[+ip4:142.0.176.0/20]; MIME_GOOD(-0.10)[text/plain]; ASN(0.00)[asn:7381, ipnet:142.0.176.0/22, country:US]; RCVD_IN_DNSWL_NONE(0.00)[142.0.189.2:received]; MIME_TRACE(0.00)[0:+]; FROM_NEQ_ENVFROM(0.00)[steve@sohara.org,4250.82.1d4f30000abd3b9.f990a820291acc19ed61da0b52d6c794@email-od.com]; MLMMJ_DEST(0.00)[questions@freebsd.org]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[email-od.com:+]; TO_MATCH_ENVRCPT_ALL(0.00)[]; DMARC_NA(0.00)[sohara.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[email-od.com:dkim] X-ThisMailContainsUnwantedMimeParts: N On Fri, 30 Sep 2022 14:48:09 -0400 Paul Procacci wrote: > 31 EMLINK Too many links. Maximum allowable hard links to a single > file has been exceeded (limit of 32767 hard links per file). > > I betcha the parent directory has at least this many number of objects in > it. DIRHASH has a lot to answer for, time was we'd jump through hoops when writing applications to avoid having huge numbers of files in a directory, now nobody notices any problems until they hit the limit. -- Steve O'Hara-Smith