From: Elana Hashman <Elana.Hashman@twosigma.com>
To: 'Reindl Harald' <h.reindl@thelounge.net>,
"'tytso@mit.edu'" <tytso@mit.edu>
Cc: "'linux-ext4@vger.kernel.org'" <linux-ext4@vger.kernel.org>
Subject: RE: Phantom full ext4 root filesystems on 4.1 through 4.14 kernels
Date: Thu, 8 Nov 2018 18:20:24 +0000 [thread overview]
Message-ID: <f3ea91fea4604783b4b03ce3817561f9@exmbdft5.ad.twosigma.com> (raw)
In-Reply-To: <8ac9d2e2-f462-2b8d-d10e-93f065528009@thelounge.net>
-----Original Message-----
From: Reindl Harald <h.reindl@thelounge.net>
Sent: Thursday, November 8, 2018 1:14 PM
> and what says "df -hi"?
> maybe you are running simply out of inodes
We are nowhere near the inode limit:
$ df -hi /
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/disk/by-uuid/<some-uuid> 3.2M 191K 3.0M 6% /
I can't confirm 100% since we rebooted this host and I don't have a candidate demonstrating the problem right now that I can check, but it's something we've checked previously.
- e
next prev parent reply other threads:[~2018-11-09 4:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 17:59 Phantom full ext4 root filesystems on 4.1 through 4.14 kernels Elana Hashman
2018-11-08 18:13 ` Reindl Harald
2018-11-08 18:20 ` Elana Hashman [this message]
2018-11-08 18:47 ` Darrick J. Wong
2018-12-05 16:26 ` Elana Hashman
2019-01-23 19:59 ` Thomas Walker
2019-06-26 15:17 ` Thomas Walker
2019-07-11 9:23 ` Jan Kara
2019-07-11 14:40 ` Geoffrey Thomas
2019-07-11 15:23 ` Jan Kara
2019-07-11 17:10 ` Theodore Ts'o
2019-07-12 19:19 ` Thomas Walker
2019-07-12 20:28 ` Theodore Ts'o
2019-07-12 21:47 ` Geoffrey Thomas
2019-07-25 21:22 ` Geoffrey Thomas
2019-07-29 10:09 ` Jan Kara
2019-07-29 11:18 ` ext4 file system is constantly writing to the block device with no activity from the applications, is it a bug? Dmitrij Gusev
2019-07-29 12:55 ` Theodore Y. Ts'o
2019-07-29 21:12 ` Dmitrij Gusev
2019-01-24 1:54 ` Phantom full ext4 root filesystems on 4.1 through 4.14 kernels Liu Bo
2019-01-24 14:40 ` Elana Hashman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f3ea91fea4604783b4b03ce3817561f9@exmbdft5.ad.twosigma.com \
--to=elana.hashman@twosigma.com \
--cc=h.reindl@thelounge.net \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).