From: Magnus Naeslund <mag@kite.se>
To: Theodore Tso <tytso@mit.edu>, Magnus Naeslund <mag@kite.se>,
"Robert P. J. Day" <rpjday@mindspring.com>,
linux-kernel@vger.kernel.org
Subject: Re: ARC-1260: No space left on device, when there is (or should be) free space left
Date: Mon, 18 Jun 2007 18:28:08 +0200 [thread overview]
Message-ID: <4676B298.4080904@kite.se> (raw)
In-Reply-To: <20070618134413.GC30244@thunk.org>
Theodore Tso wrote:
>
> How are you using the filesystem? This wouldn't happen to be one of
> the backup schemes that use hard links and huge numbers of
> directories, would it? And how did you create the filesystem
> originally? Normally mke2fs is quite generous with the number of
> inodes it creates to avoid this problem. Did you use -T largefile or
> -T largefile4 by any chance? Or did you manually specify a
> non-standard inode_ratio size?
>
It's a filesystem containing images varying from 300kb to 2mb of size.
It currently contains 1426394 files in 4125 directories.
Magnus
I believe this has the appropriate information:
tune2fs 1.40-WIP (14-Nov-2006)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed directory hash
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 1430528
Block count: 1464843264
Reserved block count: 0
Free blocks: 998810993
Free inodes: 0
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 674
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 32
Inode blocks per group: 1
Filesystem created: Sun Apr 1 12:46:39 2007
Last mount time: Mon Jun 18 14:23:26 2007
Last write time: Mon Jun 18 14:23:26 2007
Mount count: 8
Maximum mount count: 20
Last checked: Sun Apr 1 12:46:39 2007
Check interval: 15552000 (6 months)
Next check after: Fri Sep 28 12:46:39 2007
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: f252b473-6db0-499b-8de1-c788e84563dc
Journal backup: inode blocks
next prev parent reply other threads:[~2007-06-18 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 11:08 Magnus Naeslund
2007-06-18 11:30 ` Robert P. J. Day
2007-06-18 12:20 ` Magnus Naeslund
2007-06-18 13:44 ` Theodore Tso
2007-06-18 16:28 ` Magnus Naeslund [this message]
2007-06-18 17:19 ` Jason L Tibbitts III
2007-06-18 17:26 ` Theodore Tso
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=4676B298.4080904@kite.se \
--to=mag@kite.se \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--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
Powered by JetHome