From nobody Fri Nov 11 11:00:29 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 4N7wjQ4y3yz4XQ81 for ; Fri, 11 Nov 2022 11:00:42 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (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 "mx1.riseup.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4N7wjQ01kKz3hqw for ; Fri, 11 Nov 2022 11:00:42 +0000 (UTC) (envelope-from ralf-mardorf@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=O+WF7RQu; spf=pass (mx1.freebsd.org: domain of ralf-mardorf@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=ralf-mardorf@riseup.net; dmarc=pass (policy=none) header.from=riseup.net Received: from fews2.riseup.net (fews2-pn.riseup.net [10.0.1.84]) (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 mx1.riseup.net (Postfix) with ESMTPS id 4N7wjN5KjRzDqg9 for ; Fri, 11 Nov 2022 11:00:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1668164440; bh=HpTJoYy+ZBEfhIbH4kD1NlKW6Ww8o8QzJyj3YnJD7aY=; h=Subject:From:To:Date:In-Reply-To:References:From; b=O+WF7RQuQYCWkxy4a+BFTIs6jE3QOhZm1UmbGAOApuhhoplfFefY3H//lJehzxrtc 9ffUZo2SihseQR+ftgU3a8ei+rOUpGvzHVbN7tJf0aelRcBHauj88O4rUenWylADYD /UBsnmHi29s0d4TXwhihgpWBSNFDoYYaVEUQx8Xg= X-Riseup-User-ID: 3AB7ADDDE65961EB3251AB1F09B4F67041E21D34B21AD331AB233E1668A2837D Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews2.riseup.net (Postfix) with ESMTPSA id 4N7wjN0b02z1yRB for ; Fri, 11 Nov 2022 11:00:39 +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 12:00:29 +0100 In-Reply-To: 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.20 / 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_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+mx:c]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[198.252.153.129:from]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; DKIM_TRACE(0.00)[riseup.net:+]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; MLMMJ_DEST(0.00)[questions@freebsd.org]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[questions@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; DWL_DNSWL_NONE(0.00)[riseup.net:dkim] X-Rspamd-Queue-Id: 4N7wjQ01kKz3hqw X-ThisMailContainsUnwantedMimeParts: N On Fri, 2022-11-11 at 11:57 +0100, Ralf Mardorf wrote: > 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. >=20 > 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. Pardon, I missed to read "md".