Reserved Space Not Working - Disk Filling to 0 bytes available

[GoogleCodeExporter]

What steps will reproduce the problem? (I'm guessing on these steps)
1. tune2fs -m 0 /dev/sdaX
2. load up mogilefs with data till it fills the disk

What is the expected output? What do you see instead?

min_free_space 5000

I would expect that mogilefs would leave 5,000 (or around) megabytes on each 
disk

The mogadm check output should show the actual values of the disk if there are 
0 bytes available, instead it shows:
[ 6] dev49  MISSING FIELD (available) FROM USAGE FILE: 
http://x.x.x.x:7500/dev49/usage

What version of the product are you using? On what operating system?

Trackers 2.60
O/S 2.6.32.21-168.fc12.x86_64

Please provide any additional information below.

Disks are ext3 (2 TB drives)

'df' output: (dev60 was marked tune2fs -m 1 after this issue started)

Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda2             26206076   4125132  20749744  17% /
tmpfs                 12366520         0  12366520   0% /dev/shm
/dev/sda1               198337     23349    164748  13% /boot
/dev/sdb2            1917819724 1820400940         0 100% /var/mogdata/dev50
/dev/sdc2            1917819724 1820400716         0 100% /var/mogdata/dev51
/dev/sdd2            1917819724 1820400708         0 100% /var/mogdata/dev52
/dev/sde1            1922858352 1825183548         0 100% /var/mogdata/dev53
/dev/sdf1            1922858352 1825183552         0 100% /var/mogdata/dev54
/dev/sdg1            1922858352 1825183368         0 100% /var/mogdata/dev55
/dev/sdh1            1922858352 1825183456         0 100% /var/mogdata/dev56
/dev/sdi1            1922858352 1825183492         0 100% /var/mogdata/dev57
/dev/sdj1            1922858352 1825183504         0 100% /var/mogdata/dev58
/dev/sdk1            1922858352 1825183812         0 100% /var/mogdata/dev59
/dev/sdl1            1922858352 1825387432  97470920  95% /var/mogdata/dev60
/dev/sda3            1896451184 1800118184         0 100% /var/mogdata/dev49

tune2fs output:

tune2fs -l /dev/sdf1
tune2fs 1.41.9 (22-Aug-2009)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          466aeaf8-debd-4c95-8b15-ff80cea387bd
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr 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:              122101760
Block count:              488378000
Reserved block count:     24418900
Free blocks:              53145959
Free inodes:              116013334
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      907
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Thu Nov 18 12:33:00 2010
Last mount time:          Wed May  2 08:05:07 2012
Last write time:          Wed May  2 08:05:07 2012
Mount count:              4
Maximum mount count:      -1
Last checked:             Thu Nov 18 12:33:00 2010
Check interval:           0 (<none>)
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:      3f441b48-3dc7-4f70-84dc-919c201fa50b
Journal backup:           inode blocks

Original issue reported on code.google.com by jdan...@intelemage.com on 9 May 2012 at 9:43

[GoogleCodeExporter]

Note: mogadm device list shows space available:

storage3 [6]: alive
                   used(G) free(G) total(G)
dev58: alive      1740.630 93.150  1833.780

Original comment by jdan...@intelemage.com on 9 May 2012 at 10:05

[GoogleCodeExporter]

What version are your mogstored's running? 2.60 as well or potentially 
something from before october 2009? :)

Original comment by dorma...@rydia.net on 19 May 2012 at 3:07

[GoogleCodeExporter]

Guilty as charged. I've got a mogstored that's very old. Version 1.70 so that's 
probably the issue. I'll upgrade and re-open if necessary.

Original comment by jed.dan...@gmail.com on 20 Jun 2012 at 1:11

• Changed state: Invalid

[GoogleCodeExporter]

fwiw that looks like a perlbal version, so mogstored's code and perlbal both 
need upgradin's

Original comment by dorma...@rydia.net on 20 Jun 2012 at 1:12

[GoogleCodeExporter]

Thanks - the mogstored file is from 2009-12-07 -- is there another way to 
verify it's version # other than what I did (telnet localhost 7501 -> version)

Original comment by jed.dan...@gmail.com on 20 Jun 2012 at 1:17

[GoogleCodeExporter]

Apparently, not easily... It changes extremely rarely so mostly it doesn't 
matter. In october 2009 it was updated to require perlbal 1.73 at least, so 
your version is probably older than that.

Give 'em both an upgrade anyway :p report back if that doesn't fix it.

Original comment by dorma...@rydia.net on 20 Jun 2012 at 1:24