Linux-Fsdevel Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
linux-ext4@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Dave Jiang <dave.jiang@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Matthew Wilcox <willy@infradead.org>, Jan Kara <jack@suse.cz>,
Eric Sandeen <esandeen@redhat.com>,
Dave Chinner <david@fromorbit.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: A bug in ext4 with big directories (was: NVFS XFS metadata)
Date: Wed, 23 Sep 2020 11:44:57 +0200 [thread overview]
Message-ID: <20200923094457.GB6719@quack2.suse.cz> (raw)
In-Reply-To: <alpine.LRH.2.02.2009230459450.1800@file01.intranet.prod.int.rdu2.redhat.com>
Hi!
On Wed 23-09-20 05:20:55, Mikulas Patocka wrote:
> There seems to be a bug in ext4 - when I create very large directory, ext4
> fails with -ENOSPC despite the fact that there is plenty of free space and
> free inodes on the filesystem.
>
> How to reproduce:
> download the program dir-test:
> http://people.redhat.com/~mpatocka/benchmarks/dir-test.c
>
> # modprobe brd rd_size=67108864
> # mkfs.ext4 /dev/ram0
> # mount -t ext4 /dev/ram0 /mnt/test
> # dir-test /mnt/test/ 8000000 8000000
> deleting: 7999000
> 2540000
> file 2515327 can't be created: No space left on device
> # df /mnt/test
> /dev/ram0 65531436 633752 61525860 2% /mnt/test
> # df -i /mnt/test
> /dev/ram0 4194304 1881547 2312757 45% /mnt/test
Yeah, you likely run out of space in ext4 directory h-tree. You can enable
higher depth h-trees with large_dir feature (mkfs.ext4 -O large_dir). Does
that help?
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2020-09-23 9:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 12:34 [RFC] nvfs: a filesystem for persistent memory Mikulas Patocka
2020-09-15 13:00 ` Matthew Wilcox
2020-09-15 13:24 ` Mikulas Patocka
2020-09-22 10:04 ` Ritesh Harjani
2020-09-15 15:16 ` Dan Williams
2020-09-15 16:58 ` Mikulas Patocka
2020-09-15 17:38 ` Mikulas Patocka
2020-09-16 10:57 ` [PATCH] pmem: export the symbols __copy_user_flushcache and __copy_from_user_flushcache Mikulas Patocka
2020-09-16 16:21 ` Dan Williams
2020-09-16 17:24 ` Mikulas Patocka
2020-09-16 17:40 ` Dan Williams
2020-09-16 18:06 ` Mikulas Patocka
2020-09-21 16:20 ` NVFS XFS metadata (was: [PATCH] pmem: export the symbols __copy_user_flushcache and __copy_from_user_flushcache) Mikulas Patocka
2020-09-22 5:03 ` Dave Chinner
2020-09-22 16:46 ` Mikulas Patocka
2020-09-22 17:25 ` Matthew Wilcox
2020-09-24 15:00 ` Mikulas Patocka
2020-09-28 15:22 ` Mikulas Patocka
2020-09-23 2:45 ` Dave Chinner
2020-09-23 9:20 ` A bug in ext4 with big directories (was: NVFS XFS metadata) Mikulas Patocka
2020-09-23 9:44 ` Jan Kara [this message]
2020-09-23 12:46 ` Mikulas Patocka
2020-09-23 20:20 ` Andreas Dilger
2020-09-23 17:19 ` NVFS XFS metadata (was: [PATCH] pmem: export the symbols __copy_user_flushcache and __copy_from_user_flushcache) Mikulas Patocka
2020-09-23 9:57 ` Jan Kara
2020-09-23 13:11 ` Mikulas Patocka
2020-09-23 15:04 ` Matthew Wilcox
2020-09-22 12:28 ` Matthew Wilcox
2020-09-22 12:39 ` Mikulas Patocka
2020-09-16 18:56 ` [PATCH] pmem: fix __copy_user_flushcache Mikulas Patocka
2020-09-18 1:53 ` Dan Williams
2020-09-18 12:25 ` the "read" syscall sees partial effects of the "write" syscall Mikulas Patocka
2020-09-18 13:13 ` Jan Kara
2020-09-18 18:02 ` Linus Torvalds
2020-09-20 23:41 ` Dave Chinner
2020-09-17 6:50 ` [PATCH] pmem: export the symbols __copy_user_flushcache and __copy_from_user_flushcache Christoph Hellwig
2020-09-21 16:19 ` [RFC] nvfs: a filesystem for persistent memory Mikulas Patocka
2020-09-21 16:29 ` Dan Williams
2020-09-22 15:43 ` Ira Weiny
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=20200923094457.GB6719@quack2.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=david@fromorbit.com \
--cc=esandeen@redhat.com \
--cc=ira.weiny@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=vishal.l.verma@intel.com \
--cc=willy@infradead.org \
--subject='Re: A bug in ext4 with big directories (was: NVFS XFS metadata)' \
/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
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).