Can't mkdir events - 39% used, but 100% inodes used

gregom · Post by **gregom** » Tue Jun 11, 2013 8:41 pm

I need help! I thought I had set the correct bytes per inode when I created the file system for my 4.5 TB array which holds my ZM events but I am now out of inodes at 39% disk space utilization. I followed Paranoid's post in this thread: http://www.zoneminder.com/forums/viewto ... ilit=inode to create a volume and specify the correct bytes per inode value. Yet here I am with the exact same problem again.

To confirm I am indeed out of inodes, I check:

Result of command df -i

Code: Select all

Filesystem        Inodes     IUsed    IFree IUse% Mounted on
/dev/sda1       15007744     89611 14918133    1% /
udev              503825       485   503340    1% /dev
tmpfs             514319       404   513915    1% /run
none              514319         5   514314    1% /run/lock
none              514319        17   514302    1% /run/shm
/dev/sdb1       15269888      3487 15266401    1% /var
/dev/sdc       137351168 137351168        0  100% /var/cache/zoneminder/events

Yep... but I am certainly not out of disk space:

Result of command df

Code: Select all

Filesystem      1K-blocks       Used  Available Use% Mounted on
/dev/sda1       236236544    1481040  222755300   1% /
udev              2015300          4    2015296   1% /dev
tmpfs              822912        296     822616   1% /run
none                 5120          0       5120   0% /run/lock
none              2057276          0    2057276   0% /run/shm
/dev/sdb1       240364032    3793156  224361008   2% /var
/dev/sdc       4360542640 1583451044 2557333004  39% /var/cache/zoneminder/events

So what should my correct bytes per inode be set at? I gathered the needed information from the following results:

Run command dumpe2fs -h /dev/sdc

Code: Select all

dumpe2fs 1.42 (29-Nov-2011)
Filesystem volume name:   <none>
Last mounted on:          /var/cache/zoneminder/events
Filesystem UUID:          0e7def72-758b-484e-b31d-2b96a355e4f6
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              137351168
Block count:              1098792960
Reserved block count:     54939648
Free blocks:              694272899
Free inodes:              0
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      762
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         4096
Inode blocks per group:   256
Flex block group size:    16
Filesystem created:       Fri May 17 10:08:46 2013
Last mount time:          Mon Jun 10 17:31:59 2013
Last write time:          Mon Jun 10 17:31:59 2013
Mount count:              4
Maximum mount count:      -1
Last checked:             Fri May 17 10:08:46 2013
Check interval:           0 (<none>)
Lifetime writes:          1896 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      c3246ef1-2e0f-478a-9017-79b096265ab3
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x000bbdd4
Journal start:            27745

So using the math he [Paranoid] mentions, I did block size (which is 4096) times block count (1098792960) divided by inode count (137351168) which equals 32767.51140667402. Rounding that to the nearest power of two is 32768.

So as far as I can tell, that is the correct value to use. When I created the file system, I used the command mkfs –t ext4 –i 32768 /dev/sdc

So what have I done wrong? Why am I out of inodes? The only thing I can think of is at the end of Paranoid's post they mention the assumption that you only have ZM events on your volume. I think I may have an inaccurate calculation due to the fact that events are not the only thing on my /var volume. Another thing mentioned is the average size of my JPEG's compared to the bytes per inode value, but they all appear to be under 14Kbytes, which is well below the 32Kbytes value set.