All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: cy6erGn0m <cy6ergn0m@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: No space left on device after many files creation
Date: Mon, 12 Apr 2010 17:00:37 -0500	[thread overview]
Message-ID: <4BC39805.7090807@redhat.com> (raw)
In-Reply-To: <4BC39762.9080406@gmail.com>

cy6erGn0m wrote:
> In the past I have done the same test for ext3 and it was created ~10M
> files in one firectory at working filesystem (/home) and it was no
> issues reached.
> 
> On ext4 i found inodes max size is limited as you wrote:
> [root@cgmachine sandbox]# df -i /e4
> Файловая система      Инодов   Испол   Своб  Исп % смонтирована на
> (file system/inodes/used/free/used%/mounted on)
> /dev/sda4               1,8M    1,8M       0  100% /e4
> [root@cgmachine sandbox]#
> 
> Why inodes count limit is so small by default? Is it depends on
> partition size?

it does depend on partition size; the inode_ratio = 16384 in mke2fs.conf
says 1 inode per 16k of filesystem space.

the inode size was also increased a couple years ago, and the default
inode count was reduced by half so that the total size remained the same.

-Eric

> Eric Sandeen wrote:
>> cy6erGn0m wrote:
>>   
>>> I have found issue with ext4 partition.
>>> I created many many empty files with the following way:
>>> [cy6ergn0m@cgmachine heap]$ seq 1 10000000 | xargs touch
>>>
>>> But this command crashes asfter a while with a error 'no space left on
>>> device'. At the same time, df -h shows that I have 7Gb free on this file
>>> system. So, I can't create any file in any directory at this filesystem.
>>>
>>> [cy6ergn0m@cgmachine heap]$ pwd
>>> /e4/sandbox/heap
>>> [cy6ergn0m@cgmachine heap]$ ls -1 | wc -l
>>> 1261144
>>> [cy6ergn0m@cgmachine heap]$ df -h /e4
>>> Файловая система      Разм  Исп  Дост  Исп% смонтирована на
>>> (filesystem/size/used/available/used%/mounted)
>>> /dev/sda4              28G  7.2G   19G  28% /e4
>>>     
>> try df -i
>>
>> There is a limited number of inodes that you can create, as set
>> at mkfs time.
>>
>> -Eric
>>
>>   
>>> [cy6ergn0m@cgmachine heap]$ touch ttt
>>> touch: невозможно выполнить touch для `ttt': На устройстве кончилось место
>>> (touch: failed to execute touch for 'ttt': No space left on device)
>>>
>>>
>>>     
>>   
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-04-12 22:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 21:20 No space left on device after many files creation cy6erGn0m
2010-04-12 21:28 ` Eric Sandeen
2010-04-12 21:57   ` cy6erGn0m
2010-04-12 22:00     ` Eric Sandeen [this message]
2010-04-12 22:44       ` tytso
2010-04-13  6:35         ` cy6erGn0m
2010-04-13 15:34           ` Eric Sandeen
2010-04-15 15:14           ` Andi Kleen

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=4BC39805.7090807@redhat.com \
    --to=sandeen@redhat.com \
    --cc=cy6ergn0m@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.