WebIf always saying no disk space

S

SunnysideUK

Member
Using network-shares-automount (Samba/SMB-cifs), I recently archived a couple of smallish recordings to one of my HDR-Fox recorders. It had about 6GiB free, less the copy of about 0.9GiB, but checking later, the recordings showed 0 byte file size and the WebIf free space went to "Free: 0 bytes (1%)".

I deleted the zero byte files and another larger recording to free up space, but the webif free space stayed the same!
I ran fixdisk (several times, after removing more recordings). However, while fixdisk shows more free space, WebIf summary still shows the same "Free: 0 bytes (1%)".

SMART show OK, and there are no reallocations.
Last fixdisk log showed sda2: "115005514 blocks used (96.47%, out of 119209984)"

Any ideas what I should do to resolve this problem?

p.s. streaming of several test recording is still working OK.
Also, prior to the copy, I had updated the packages but I forget what it/they were.
 
What does it do without network-shares-automount ?
You'll need to provide the output from these commands run at the command line:
Code: 
humax# /mod/bin/busybox/stat -f -c "%S %b %f" /mnt/hd2
humax# /mod/webif/html/diskspace/diskspace.jim
And what version of WebIf ?

(And on a separate topic, I'm interested in your no. 1 machine with an Unknown loader version. What does it say on the on-screen interface?)
 
Humax#2 (problem machine)
Web interface version: 1.4.9-9
Custom firmware version: 3.13 (build 4028)
Humax Version: 1.03.12 (kernel HDR_CFW_3.13)
Loader Version: a7.33
System ID: 80bc.7e00

prpr said:
What does it do without network-shares-automount ?
Click to expand...
Do you mean record something locally?
I was copying from humax4 to humax2 (using Blue/Storage: USB)

prpr said:
humax# /mod/bin/busybox/stat -f -c "%S %b %f" /mnt/hd2
Click to expand...
humax#2 /mod/bin/busybox/stat -f -c "%S %b %f" /mnt/hd2
4096 117335874 4204467

prpr said:
humax# /mod/webif/html/diskspace/diskspace.jim
Click to expand...

<script type=text/javascript>
diskspace_data = [
{
name: 'Used',
y: 480607739904,
sliced: false,
pretty: '447.6 GiB'
},
{
name: 'Dustbin',
y: 0,
sliced: false,
pretty: '0 bytes'
},
{
name: 'Free',
y: 0,
sliced: false,
pretty: '0 bytes'
}
];
</script>
<span id=tbdiskpie></span>


<span id=tbdiskspace>
Total space: 447.6 GiB<br>
<img src=/img/pie-blue.png height=10>
Used: 447.6 GiB (100%)<br>
<img src=/img/pie-grey.png height=10>
Free: 0 bytes (0%)


</span>
<script src=/diskspace/diskspace.js type=text/javascript></script>

humax2#
p.s. I have today, before this updated another package (tv-diary) which appears to have installed OK.
Maybe that's why it now says 0% instead of 1%?
prpr said:
(And on a separate topic, I'm interested in your no. 1 machine with an Unknown loader version. What does it say on the on-screen interface?)
Click to expand...
Menu SysInfo: a7.31
Humax#1 {not involved}
Web interface version: 1.4.9-9
Custom firmware version: 3.13 (build 4028)
Humax Version: 1.02.20 (kernel HDR_CFW_3.13)
Loader Version: Unknown - 012d
System ID: 80bc.7e00

I've updated my Signature. I've now 4 HDR-Fox machines.
 
Additional:
My Humax2 webif shows a box: Save last streamed content: 381 MiB
Humax2.PNG
But I don't think I've seen this on the Humax4 source machine.
All machines are set to boot the LCN:100.Freeview (to reduce load).
 
SunnysideUK said:
Do you mean record something locally?
Click to expand...
I meant either disable or uninstall it temporarily, to rule out side-effects.
humax#2 /mod/bin/busybox/stat -f -c "%S %b %f" /mnt/hd2
4096 117335874 4204467
Click to expand...
That looks reasonable, but a bit confused how free space ends at zero. Can you try some jimsh commands and report, like this example:
Code: 
humax# jimsh
Welcome to Jim version 0.81
. source /mod/webif/lib/setup
jscss
. require system.class
. system diskspace
{1.81 TiB} {1.52 TiB} 83 {296.67 GiB} 17 {20 GiB} {17.76 GiB}
. system diskspace 1
1987960578048 1669414080512 83 318546497536 17 21474836480 19065860096
. exit
before this updated another package (tv-diary) which appears to have installed OK.
Maybe that's why it now says 0% instead of 1%?
Click to expand...
Unlikely I'd have thought (famous last words).
SunnysideUK said:
My Humax2 webif shows a box: Save last streamed content: 381 MiB
Click to expand...
Not relevant.
 
prpr said:
Can you try some jimsh commands and report
Click to expand...
humax2# jimsh
Welcome to Jim version 0.79
. source /mod/webif/lib/setup
jscss
. require system.class
. system diskspace
{447.6 GiB} {431.56 GiB} 96 {16.04 GiB} 4 {20 GiB} {234.23 MiB}
. system diskspace 1
480607739904 463386288128 96 17221451776 4 21474836480 245604352
. exit
humax2#

p.s. Menu|Data Storage says:
Available: 0.0GB
Used: 447.6GB
Reserved: 72.6GB
Total: 500.0GB
Pie chart: 0% available
& diags pass OK.
 
SunnysideUK said:
My Humax2 webif shows a box: Save last streamed content: 381 MiB
Humax2.PNG

But I don't think I've seen this on the Humax4 source machine.
Click to expand...
That's because the streaming buffer on Humax2 has something in it (probably from an iPlayer operation, possibly some time ago), while Humax4 doesn't.
 
"Reserved: 72GB" looks weird. Should be 20GB, like in the two system diskspace outputs? How does the settop program determine "Reserved"?

Maybe the output of dumpe2fs -h /dev/sda1 (and for HDR: ...sda2, ...sda3) would be useful.
 
/df said:
Maybe the output of dumpe2fs -h /dev/sda1 (and for HDR: ...sda2, ...sda3) would be useful.
Click to expand...
Code: 
humax2# dumpe2fs -h /dev/sda1
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   VirtualUSB
Last mounted on:          <not available>
Filesystem UUID:          205168d0-b4cd-4b84-9d6f-7713c4582e08
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      ext_attr resize_inode dir_index filetype sparse_super large_file
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         not clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              16
Block count:              60
Reserved block count:     3
Free blocks:              0
Free inodes:              2
First block:              1
Block size:               1024
Fragment size:            1024
Blocks per group:         8192
Fragments per group:      8192
Inodes per group:         16
Inode blocks per group:   2
Filesystem created:       Tue Feb  7 07:40:37 2017
Last mount time:          Wed Sep 28 13:55:34 2022
Last write time:          Wed Sep 28 13:55:34 2022
Mount count:              11
Maximum mount count:      -1
Last checked:             Tue Feb  7 07:40:37 2017
Check interval:           0 (<none>)
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               128
Default directory hash:   half_md4
Directory Hash Seed:      e42aa59d-7eb0-4070-9bee-dc9f0c6ef629

humax2# dumpe2fs -h /dev/sda2
dumpe2fs 1.42.13 (17-May-2015)
/usr/lib/ext2/bin/dumpe2fs: No such device or address while trying to open /dev/sda2
Couldn't find valid filesystem superblock.
humax2# dumpe2fs -h /dev/sda3
dumpe2fs 1.42.13 (17-May-2015)
/usr/lib/ext2/bin/dumpe2fs: No such device or address while trying to open /dev/sda3
Couldn't find valid filesystem superblock.
humax2# dumpe2fs -h /dev/sda
dumpe2fs 1.42.13 (17-May-2015)
/usr/lib/ext2/bin/dumpe2fs: Bad magic number in super-block while trying to open /dev/sda
Couldn't find valid filesystem superblock.
humax2#
/df said:
"Reserved: 72GB" looks weird. Should be 20GB,
Click to expand...
Checked two other PVR's (Humax1 & 4) and they are also showing the same reserved 72.6GB.

<EDIT>
humax2# fdisk -l

Disk /dev/sda: 0 MB, 65536 bytes
4 heads, 8 sectors/track, 4 cylinders
Units = cylinders of 32 * 512 = 16384 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 128 2044 83 Linux

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdb1 1 131 1052256+ 83 Linux
/dev/sdb2 132 59495 476841330 83 Linux
/dev/sdb3 59496 60801 10490445 83 Linux
humax2#
 
Last edited:
/df said:
In your system, /dev/sdb* are the interesting ones, sorry.
Click to expand...
OK, for /sdb*
Code: 
humax2# dumpe2fs -h /dev/sdb1
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          72a0457f-998c-4685-86f7-99ff020e7c98
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:              65808
Block count:              263064
Reserved block count:     13153
Free blocks:              248430
Free inodes:              65794
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      64
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         7312
Inode blocks per group:   457
Filesystem created:       Sat Jan  1 00:00:14 2000
Last mount time:          Wed Sep 28 12:55:39 2022
Last write time:          Wed Sep 28 12:55:39 2022
Mount count:              7
Maximum mount count:      35
Last checked:             Tue Sep 27 17:35:34 2022
Check interval:           15552000 (6 months)
Next check after:         Sun Mar 26 17:35:34 2023
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      fc5e725d-c558-481f-b6e3-aafa7a448ae1
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             32M
Journal length:           8192
Journal sequence:         0x0004f33f
Journal start:            1

humax2#
 
Last edited:
...sdb2 and ...sdb3, not ...sd2, etc.

/dev/sdb1 has housekeeping files. That looks fine.
/dev/sdb2 is the one that has the recordings and is shown in the disk space statistics, so what we're really interested in.
/dev/sdb3 stores files streamed by eg the iPlayer app.
 
/df said:
..sdb2 and ...sdb3, not ...sd2, etc.
Click to expand...
Sorry, some kind of type as I'm unfamiliar...
Code: 
humax2# dumpe2fs -h  /dev/sdb1
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          72a0457f-998c-4685-86f7-99ff020e7c98
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:              65808
Block count:              263064
Reserved block count:     13153
Free blocks:              248430
Free inodes:              65794
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      64
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         7312
Inode blocks per group:   457
Filesystem created:       Sat Jan  1 00:00:14 2000
Last mount time:          Wed Sep 28 12:55:39 2022
Last write time:          Wed Sep 28 12:55:39 2022
Mount count:              7
Maximum mount count:      35
Last checked:             Tue Sep 27 17:35:34 2022
Check interval:           15552000 (6 months)
Next check after:         Sun Mar 26 17:35:34 2023
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      fc5e725d-c558-481f-b6e3-aafa7a448ae1
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             32M
Journal length:           8192
Journal sequence:         0x0004f33f
Journal start:            1

humax2# dumpe2fs -h  /dev/sdb2
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          ba26da7c-9255-4c0f-94ce-31bc2a1445da
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:              29860704
Block count:              119209984
Reserved block count:     5960516
Free blocks:              4204475
Free inodes:              29847644
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      995
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8208
Inode blocks per group:   513
Filesystem created:       Sat Jan  1 00:00:15 2000
Last mount time:          Wed Sep 28 12:55:41 2022
Last write time:          Wed Sep 28 12:55:41 2022
Mount count:              6
Maximum mount count:      33
Last checked:             Tue Sep 27 17:35:59 2022
Check interval:           15552000 (6 months)
Next check after:         Sun Mar 26 17:35:59 2023
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      f0cb25f0-276e-470d-b33a-5530b4d0de99
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x00e52633
Journal start:            4516

humax2# dumpe2fs -h  /dev/sdb3
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   hmx_int_stor
Last mounted on:          <not available>
Filesystem UUID:          fb65b9aa-05f8-4088-aa5a-ced437117778
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:              655776
Block count:              2622611
Reserved block count:     131130
Free blocks:              2412370
Free inodes:              655756
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      640
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8096
Inode blocks per group:   506
Filesystem created:       Wed Jul  6 16:11:16 2016
Last mount time:          Wed Sep 28 12:55:41 2022
Last write time:          Wed Sep 28 12:55:41 2022
Mount count:              8
Maximum mount count:      23
Last checked:             Tue Sep 27 17:35:21 2022
Check interval:           15552000 (6 months)
Next check after:         Sun Mar 26 17:35:21 2023
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      b0290e9d-b4f8-4c49-8e3c-0914477ee66b
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x00020083
Journal start:            1

humax2#
 
Last edited:
/dev/sdb2
Free blocks: 4204475 x Block size: 4096 = 17,221,529,600 bytes
divide by 1024x1024x1024 = 16.0388 | ~16GiB free space
 
Black Hole said:
Code: 
...
, or
Click to expand...
You mean format telnet output like this?
Code: 
humax2# dumpe2fs -h  /dev/sdb1
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          72a0457f-998c-4685-86f7-99ff020e7c98
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:              65808
Block count:              263064
Reserved block count:     13153
Free blocks:              248430
Free inodes:              65794
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      64
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         7312
Inode blocks per group:   457
Filesystem created:       Sat Jan  1 00:00:14 2000
Last mount time:          Wed Sep 28 12:55:39 2022
Last write time:          Wed Sep 28 12:55:39 2022
Mount count:              7
Maximum mount count:      35
Last checked:             Tue Sep 27 17:35:34 2022
Check interval:           15552000 (6 months)
Next check after:         Sun Mar 26 17:35:34 2023
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      fc5e725d-c558-481f-b6e3-aafa7a448ae1
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             32M
Journal length:           8192
Journal sequence:         0x0004f33f
Journal start:            1

humax2# dumpe2fs -h  /dev/sdb2
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   <none>
Last mounted on:          <not available>
Filesystem UUID:          ba26da7c-9255-4c0f-94ce-31bc2a1445da
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:              29860704
Block count:              119209984
Reserved block count:     5960516
Free blocks:              4204475
Free inodes:              29847644
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      995
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8208
Inode blocks per group:   513
Filesystem created:       Sat Jan  1 00:00:15 2000
Last mount time:          Wed Sep 28 12:55:41 2022
Last write time:          Wed Sep 28 12:55:41 2022
Mount count:              6
Maximum mount count:      33
Last checked:             Tue Sep 27 17:35:59 2022
Check interval:           15552000 (6 months)
Next check after:         Sun Mar 26 17:35:59 2023
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      f0cb25f0-276e-470d-b33a-5530b4d0de99
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x00e52633
Journal start:            4516

humax2# dumpe2fs -h  /dev/sdb3
dumpe2fs 1.42.13 (17-May-2015)
Filesystem volume name:   hmx_int_stor
Last mounted on:          <not available>
Filesystem UUID:          fb65b9aa-05f8-4088-aa5a-ced437117778
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:              655776
Block count:              2622611
Reserved block count:     131130
Free blocks:              2412370
Free inodes:              655756
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      640
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8096
Inode blocks per group:   506
Filesystem created:       Wed Jul  6 16:11:16 2016
Last mount time:          Wed Sep 28 12:55:41 2022
Last write time:          Wed Sep 28 12:55:41 2022
Mount count:              8
Maximum mount count:      23
Last checked:             Tue Sep 27 17:35:21 2022
Check interval:           15552000 (6 months)
Next check after:         Sun Mar 26 17:35:21 2023
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Journal inode:            8
Default directory hash:   tea
Directory Hash Seed:      b0290e9d-b4f8-4c49-8e3c-0914477ee66b
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x00020083
Journal start:            1

humax2#
 
Last edited:
[Yes, except all the output and not just the 1st line - you can use triple backquotes to wrap the code text too]

Right, to quote the Fourth Yorkshireman.

The Reserved value shown in the on-screen display is tosh (tldr; reserved = disk_size/GB - video_partition_size/GiB + reserved_TSR_buffer_size/GiB !).

Block count: 119209984
Reserved block count: 5960516
Free blocks: 4204475
Click to expand...

So:
  • disk (partition): 476839936 bytes = 454.75 GiB
  • file system reserved blocks: 24414273536 bytes = 22.74GB
  • free space: 17221529600 bytes = 16.04GiB

Again
That looks reasonable, but a bit confused how free space ends at zero.
Click to expand...

As almost everything is uid 0 in this system, the filesystem reserved blocks value is not relevant.

The calculation for the other values shown on-screen was also inferred (where 20GiB is the reserved TSR buffer size):
The Available Size shown is: <free space on recording partition> - (20GiB - <current size of TSR buffer)
The Used Size shown is: <used space on recording partition> + (20GiB - <current size of TSR buffer)
Click to expand...

This means that if something has happened that truncates the TSR buffer more free space can be shown than will be available after some time watching the same channel.

Tell that to the young people of today and they'll not believe you.
 
SunnysideUK said:
. system diskspace
{447.6 GiB} {431.56 GiB} 96 {16.04 GiB} 4 {20 GiB} {234.23 MiB}
Click to expand...
Your TSR buffer should be 20 GiB but is only 234 MiB for whatever reason, which probably means it won't work.
The WebIf calculations remove the TSR reserved space (20 GiB) when calculating the apparent free space.
As you only have 16 GiB free, which is obviously less than 20, then you effectively have no space.
Either turn off the TSR buffer (using diagnostic tsr/disable), which should give you your 16GiB free space back, or delete some more stuff to make more than 20 GiB available, which may make the TSR work, along with the rest of the calculations.

Basically the disk is full.
 
You must log in or register to reply here.
Back
Top