From nobody Fri Nov 11 10:57:06 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 4N7wdM1L1rz4XNjS for ; Fri, 11 Nov 2022 10:57:11 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N7wdL0n1Yz3QjK for ; Fri, 11 Nov 2022 10:57:10 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=cyKs3NCs; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.6 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews1.riseup.net (fews1-pn.riseup.net [10.0.1.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mail.riseup.net", Issuer "R3" (not verified)) by mx0.riseup.net (Postfix) with ESMTPS id 4N7wdJ5Pc9z9sdN for ; Fri, 11 Nov 2022 10:57:08 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1668164228; bh=VMrKof6yV3ltPgoA4cofyyjjIjcXTW8UR/fS6Lzoy/M=; h=Subject:From:To:Date:In-Reply-To:References:From; b=cyKs3NCsNdDdZcWO/FgVTTpy5NCFVjJlKcSdgrsamdvrzkB2UXF1LdNvZ9kW2A9Ue 1sjCBg8IEETOA5y8zq1oTAMHcLXjV5g45j5VYPR1GOwC9umZFM0Vzz/rmDtRPNYkWF Qc0tQmGtuDshIuFqmfAY+RY5hcshA7S+s1Yhm1D0= X-Riseup-User-ID: 5D4506DC6B99DFFE1797A3A36AAB6B37BF8894E804CD364871B51ABD2990FEB3 Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews1.riseup.net (Postfix) with ESMTPSA id 4N7wdJ1D9Jz5vRk for ; Fri, 11 Nov 2022 10:57:07 +0000 (UTC) Message-ID: Subject: Re: how many inodes on a tmpfs mount From: Ralf Mardorf To: questions@freebsd.org Date: Fri, 11 Nov 2022 11:57:06 +0100 In-Reply-To: <20221111102248.9992541ce8d8bfc0eb3426e8@sohara.org> References: <20221111102201.Horde.zCCRGyrT-BPHCJVdzNB5Btt@webmail.nethead.se> <20221111102248.9992541ce8d8bfc0eb3426e8@sohara.org> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.10 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_SPF_ALLOW(-0.20)[+a:mx0.riseup.net]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.6:from]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[questions@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_ALL(0.00)[]; DKIM_TRACE(0.00)[riseup.net:+]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DWL_DNSWL_NONE(0.00)[riseup.net:dkim]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4N7wdL0n1Yz3QjK X-ThisMailContainsUnwantedMimeParts: N On Fri, 2022-11-11 at 10:22 +0000, Steve O'Hara-Smith wrote: > On Fri, 11 Nov 2022 10:22:01 +0100 > Per olof Ljungmark wrote: >=20 > > We ran out of inodes on a 2G md tmpfs mount, can someone please tell = =20 > > how I can calculate this number? As I understand it is a function of = =20 > > the size of the filesystem, but how to get the figure? >=20 > df -i will return the number of free and used inodes - but bear in > mind that with ZFS the inodes belong to the pool not the filesystem. Hi, I suspect that the OP knows that df -i shows the free and used inodes. IIUC the OP wants to know how to calculate the amount of available inodes for a tmpfs (not a file system on a disk). Probably the OP want's to know how much GiB tmpfs are needed, to hold a given amount of inodes. In my experiences with tmpfs (on Linux, not FreeBSD), it can happen that tmpfs runs out of inodes. I tend to build some packages on disk instead of tmpfs, a package for a small disk space sized icon theme could suffer from countless inodes. I increased tmpfs from around 4 GiB to around 8 GiB and probably got rid of not having enough tmpfs inodes for my needs. Regards, Ralf