plugout.net

Hello

First I'd like to thank for a great firmware. :thumbup

I have a Network Space 2 lite. Recently I noticed not all of the space of the HDD is available to use.

I have used version 15.2 for a while and now updated to version 16.0.

Web interface says
Total Storage 1859.89 GB
Available Storage 1010.71 GB

I only have one share containing subfolders and 25GB of files. I have also used MiniDLNA server.

I'm quite sure all the space was available when I installed the firmware so I guess something has happened and now there's over 800GB of space missing.

Any idea what I should do? Try to figure out what has happened of just start over and install everything from scratch?

Hi teemu_s,

Maybe you did not set rightly the data partition.

So can you post the outputs of, (use Putty)

Code: Select all

dh -h /dev/sda8

and

Code: Select all

fdisk -lu /dev/sda

(use gdisk -l /dev/sda if you have a GPT partition table)

Command dh gives an error: not found.

fdisk -lu /dev/sda

Code: Select all

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1          128520     1156679      514080  83 Linux
/dev/sda2         1156680     2184839      514080  83 Linux
/dev/sda3         2184840     3212999      514080  82 Linux swap
/dev/sda4         3213000  3907024064  1951905532+  5 Extended
/dev/sda5         3341520     5012279      835380  83 Linux
/dev/sda6         5140800     5269319       64260  83 Linux
/dev/sda7         5397840     6425999      514080  83 Linux
/dev/sda8         6554520  3907024064  1950234772+ 83 Linux


When installing the firmware for some reason I did not choose to use GPT partition table even though my device is the lite version which should support it.

Ouups, you need to use df instead of 'dh'

Code: Select all

df -h /dev/sda8

At least the size of data partition (sda8) is right :

Code: Select all

(3907024064  - 6554520) * 512 = 1859 GB

Thank you for your help, Jocko.

df -h /dev/sda8

Code: Select all

Filesystem                Size      Used Available Use% Mounted on
/dev/sda8                 1.8T    801.3G   1010.7G  44% /share/1000


I'm not familiar with Linux but the info above told me where to start looking.

ls -LRs

Code: Select all

./1000/minidlna/database:
total 815524760
       80 files.db  815524680 minidlna.log


I guess MiniDLNA has for some reason written huge amount of log. Can the log file just be deleted? I tried resetting MiniDLNA to default settings but apparently that doesn't clear the log.

I remember a couple of times the HDD has kept spinning for hours even when no one was accessing any files from the NAS. Maybe that's when MiniDLNA had crashed and kept writing the log?

So you found the culprit...

Yes, you can delete this file (best after stopping minidlna).

But maybe you would want to download it before deleting it to see what the server wrote...

downloading 800 GB...that will take time...and then try to open the file...that will take time

but indeed interessting do know what is in there

you could use the dd command to copy a part and look in that new file

example this will copy the first 100 MB of the file

Code: Select all

cd /share/1000/minidlna/database
dd bs=1M count=100 if=minidlna.log of=output1.log

I copied the the first 100MB of the log and it's filled with lines like the one below. Over 6000 times per second. I have no idea what may have caused this, some device or application perhaps?

Code: Select all

[2014/09/01 17:32:18] minidlna.c:1294: error: accept(http): Too many open files

Thank you for this feedback.

That seems to be a known issue : viewtopic.php?f=11&t=1592

But currently we do not yet explain this behaviour: only an assumption

Jocko wrote:Glad to heard this rafesl :-D

So maybe as minidlna didn't know where the pid file was saved without the patch, it didn't succeed to find its child threads and close the opened files...

Which seems to be confirmed as your issue happened when minidlna had crashed and maybe it knew no longer where is the pid file.