Re: ARC-1260: No space left on device, when there is (or should be)free space left
From: Magnus Naeslund
Date: Mon Jun 18 2007 - 12:28:19 EST
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/