From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: avoid ENOSPC when avoiding to reuse recently deleted inodes
Date: Thu, 26 Mar 2020 10:55:32 -0400 [thread overview]
Message-ID: <20200326145532.GA296708@mit.edu> (raw)
In-Reply-To: <20200318121317.31941-1-jack@suse.cz>
On Wed, Mar 18, 2020 at 01:13:17PM +0100, Jan Kara wrote:
> When ext4 is running on a filesystem without a journal, it tries not to
> reuse recently deleted inodes to provide better chances for filesystem
> recovery in case of crash. However this logic forbids reuse of freed
> inodes for up to 5 minutes and especially for filesystems with smaller
> number of inodes can lead to ENOSPC errors returned when allocating new
> inodes.
>
> Fix the problem by allowing to reuse recently deleted inode if there's
> no other inode free in the scanned range.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
Thanks, applied with a minor whitespace fixup.
- Ted
prev parent reply other threads:[~2020-03-26 14:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 12:13 [PATCH] ext4: Avoid ENOSPC when avoiding to reuse recently deleted inodes Jan Kara
2020-03-26 14:55 ` Theodore Y. Ts'o [this message]
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=20200326145532.GA296708@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
/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).