[SOLVED] RAMDisk Full
-
- New here
- Posts: 7
- Joined: Wed Jul 16, 2014 8:49 am
Re: [SOLVED] RAMDisk Full
I've also contacted Qnap support and sent a ticket on Sunday but it seems no one works at Qnap? Also their "live" support button does not ever seem to be enabled.
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: [SOLVED] RAMDisk Full
Certainly not on a Sunday - opened the ticket on http://helpdesk.qnap.com/ and have received a confirmation with a support ID?yourstruly5o1 wrote:I've also contacted Qnap support and sent a ticket on Sunday but it seems no one works at Qnap?
As everywhere, there are only limited support slots available for live chat. No idea, as it's available in very few markets only anyway.yourstruly5o1 wrote:Also their "live" support button does not ever seem to be enabled.
-
- New here
- Posts: 7
- Joined: Wed Jul 16, 2014 8:49 am
Re: [SOLVED] RAMDisk Full
ok, i've submitted another one on Sunday, let's see if they ever reply which I don't have faith in
-
- New here
- Posts: 7
- Joined: Wed Jul 16, 2014 8:49 am
Re: [SOLVED] RAMDisk Full
Here's my DF -H output
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 32.9M 0 100% /
tmpfs 32.0M 80.0k 31.9M 0% /tmp
/dev/sda4 371.0M 326.2M 44.8M 88% /mnt/ext
/dev/md9 509.5M 473.2M 36.3M 93% /mnt/HDA_ROOT
/dev/md0 1.8T 418.5G 1.4T 23% /share/MD0_DATA
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
tmpfs 32.0M 80.0k 31.9M 0% /tmp
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 32.9M 0 100% /
tmpfs 32.0M 80.0k 31.9M 0% /tmp
/dev/sda4 371.0M 326.2M 44.8M 88% /mnt/ext
/dev/md9 509.5M 473.2M 36.3M 93% /mnt/HDA_ROOT
/dev/md0 1.8T 418.5G 1.4T 23% /share/MD0_DATA
tmpfs 32.0M 0 32.0M 0% /.eaccelerator.tmp
tmpfs 32.0M 80.0k 31.9M 0% /tmp
- doktornotor
- Ask me anything
- Posts: 7472
- Joined: Tue Apr 24, 2012 5:44 am
Re: [SOLVED] RAMDisk Full
Yes, your tmpfs is 100% full. Go bug QNAP about it, I have been complaining about stupid design for "only" 2+ years, they don't care, hence they need to be flooded with support tickets resulting from this.yourstruly5o1 wrote:Here's my DF -H output
Filesystem Size Used Available Use% Mounted on
/dev/ram0 32.9M 32.9M 0 100% /
I'm gone from this forum till QNAP stop wasting volunteers' time. Get help from QNAP helpdesk instead.
Warning: offensive signature and materials damaging QNAP reputation follow:
QNAP's FW security issues
QNAP's hardware compatibility list madness
QNAP's new logo competition
Dear QNAP, kindly fire your clueless incompetent forum "admin" And while at it, don't forget the webmaster!
Warning: offensive signature and materials damaging QNAP reputation follow:
QNAP's FW security issues
QNAP's hardware compatibility list madness
QNAP's new logo competition
Dear QNAP, kindly fire your clueless incompetent forum "admin" And while at it, don't forget the webmaster!
- oyvindo
- Experience counts
- Posts: 1399
- Joined: Tue May 19, 2009 2:08 am
- Location: Norway, Oslo
[Not Solved] RAMDisk Full
How come this thread so abruptly stopped in 2014? The problem was definitely not solved...
I saw pwilson said earlier that the RAM disk could not be extended beyond 32Mb ?!? But why is that? (Obviously ; By design). But we are not at version 4.2 of QTS. Internal memory on most QNAP servers today are 2-4-6 or 8Gb. The cost of memory is the least of our problem now in 2016. Is this limitation still 32Mb? Is this because QNAP doesn't care or do not know how, or is it a 'defect' built into every Linux system that the system admin cannot decide how much RAM disk to set aside?
Anyway, My ramdisk exhausted when i began streaming radio to Kodi 15.2 using LMS 7.9 and the squeeze2UPnP bridge plugin made by philippe. Playing mp3 files can go on for ever, but streaming radio steadily fills up the Ram disk until the settings file can no longer be saved and the stream breaks. This is what the LMS log shows:
0006: [16-02-21 08:25:58.5818] Slim::Control::Request::execute (1888) Error: While trying to run function coderef [Slim::Control::Queries::songinfoQuery]: [Can't call method "playingSong" on an undefined value at /share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Player/Protocols/HTTP.pm line 672.
0005: [16-02-21 08:25:58.5813] Slim::Player::Protocols::HTTP::getMetadataFor (663) Metadata provider Slim::Plugin::RadioTime::Metadata::provider failed: Can't call method "master" on an undefined value at /share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Plugin/RadioTime/Metadata.pm line 88.
0004: [16-02-21 08:25:58.3979] Slim::Plugin::CLI::Plugin::cli_process (634) Request [songinfo] failed with error: Bad dispatch!
And this is what my DF -H looks like:
Filesystem Size Used Available Use% Mounted on
none 200.0M 169.2M 30.8M 85% /
devtmpfs 944.2M 8.0k 944.2M 0% /dev
tmpfs 64.0M 64.0M 0 100% /tmp
tmpfs 949.8M 24.0k 949.8M 0% /dev/shm
/dev/md9 509.5M 120.3M 389.1M 24% /mnt/HDA_ROOT
cgroup_root 949.8M 0 949.8M 0% /sys/fs/cgroup
/dev/mapper/cachedev1 3.5T 746.8G 2.8T 21% /share/CACHEDEV1_DATA
/dev/md13 364.2M 286.5M 77.7M 79% /mnt/ext
tmpfs 1.0M 0 1.0M 0% /mnt/rf/nd
tmpfs 64.0M 64.0M 0 100% /share/CACHEDEV1_DATA/.qpkg/HD_Station/tmp
/dev/md9 509.5M 120.3M 389.1M 24% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/config
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/home/httpd/RSS/images
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/init.d
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/rcS.d
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/rcK.d
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/default_config
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/platform.conf
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/hal_util.conf
/dev/mapper/cachedev1 3.5T 746.8G 2.8T 21% /share/CACHEDEV1_DATA/.qpkg/HD_Station/share/CACHEDEV1_DATA
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/sys/fs/cgroup
udev 944.2M 8.0k 944.2M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/dev
tmpfs 949.8M 496.0k 949.4M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run/shm
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run/lock
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run/user
Clearly the cache is full. But I do not know why and what to do with it. To me this problem is therefore marked [Unsolved]
I saw pwilson said earlier that the RAM disk could not be extended beyond 32Mb ?!? But why is that? (Obviously ; By design). But we are not at version 4.2 of QTS. Internal memory on most QNAP servers today are 2-4-6 or 8Gb. The cost of memory is the least of our problem now in 2016. Is this limitation still 32Mb? Is this because QNAP doesn't care or do not know how, or is it a 'defect' built into every Linux system that the system admin cannot decide how much RAM disk to set aside?
Anyway, My ramdisk exhausted when i began streaming radio to Kodi 15.2 using LMS 7.9 and the squeeze2UPnP bridge plugin made by philippe. Playing mp3 files can go on for ever, but streaming radio steadily fills up the Ram disk until the settings file can no longer be saved and the stream breaks. This is what the LMS log shows:
0006: [16-02-21 08:25:58.5818] Slim::Control::Request::execute (1888) Error: While trying to run function coderef [Slim::Control::Queries::songinfoQuery]: [Can't call method "playingSong" on an undefined value at /share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Player/Protocols/HTTP.pm line 672.
0005: [16-02-21 08:25:58.5813] Slim::Player::Protocols::HTTP::getMetadataFor (663) Metadata provider Slim::Plugin::RadioTime::Metadata::provider failed: Can't call method "master" on an undefined value at /share/CACHEDEV1_DATA/.qpkg/LogitechMediaServer/var/home/SqueezeboxServer/Slim/Plugin/RadioTime/Metadata.pm line 88.
0004: [16-02-21 08:25:58.3979] Slim::Plugin::CLI::Plugin::cli_process (634) Request [songinfo] failed with error: Bad dispatch!
And this is what my DF -H looks like:
Filesystem Size Used Available Use% Mounted on
none 200.0M 169.2M 30.8M 85% /
devtmpfs 944.2M 8.0k 944.2M 0% /dev
tmpfs 64.0M 64.0M 0 100% /tmp
tmpfs 949.8M 24.0k 949.8M 0% /dev/shm
/dev/md9 509.5M 120.3M 389.1M 24% /mnt/HDA_ROOT
cgroup_root 949.8M 0 949.8M 0% /sys/fs/cgroup
/dev/mapper/cachedev1 3.5T 746.8G 2.8T 21% /share/CACHEDEV1_DATA
/dev/md13 364.2M 286.5M 77.7M 79% /mnt/ext
tmpfs 1.0M 0 1.0M 0% /mnt/rf/nd
tmpfs 64.0M 64.0M 0 100% /share/CACHEDEV1_DATA/.qpkg/HD_Station/tmp
/dev/md9 509.5M 120.3M 389.1M 24% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/config
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/home/httpd/RSS/images
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/init.d
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/rcS.d
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/rcK.d
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/default_config
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/platform.conf
none 200.0M 169.2M 30.8M 85% /share/CACHEDEV1_DATA/.qpkg/HD_Station/etc/hal_util.conf
/dev/mapper/cachedev1 3.5T 746.8G 2.8T 21% /share/CACHEDEV1_DATA/.qpkg/HD_Station/share/CACHEDEV1_DATA
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/sys/fs/cgroup
udev 944.2M 8.0k 944.2M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/dev
tmpfs 949.8M 496.0k 949.4M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run/shm
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run/lock
none 949.8M 0 949.8M 0% /share/CACHEDEV1_DATA/.qpkg/HD_Station/run/user
Clearly the cache is full. But I do not know why and what to do with it. To me this problem is therefore marked [Unsolved]
-
- Experience counts
- Posts: 2415
- Joined: Wed Jan 08, 2014 10:34 pm
Re: [SOLVED] RAMDisk Full
Clearly something is misusing the area.Clearly the cache is full. But I do not know why and what to do with it
Making it larger would simply extend the time till it fails.
Why not take a look inside it to see what's consuming the space, to get an idea of the root cause rather than the symptom?
TS-431+ for storage and media and a bunch of IP cams under Surveillance Station. TVS-473 as files backup and QVR Pro.
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: [SOLVED] RAMDisk Full
It is. The subject RAMdisk space it the NAS root RAM disk - not the /tmpoyvindo wrote:How come this thread so abruptly stopped in 2014? The problem was definitely not solved...
QNAP extended the root RAMdisk to 200 MB.oyvindo wrote:I saw pwilson said earlier that the RAM disk could not be extended beyond 32Mb ?!? But why is that? (Obviously ; By design).
Neither LMS nor squeeze2UPnP is neither created nor maintained by QNAP. If these apps are abusing limited /tmp it's not a QNAP QTS issue.oyvindo wrote:My ramdisk exhausted when i began streaming radio to Kodi 15.2 using LMS 7.9 and the squeeze2UPnP bridge plugin made by philippe. Playing mp3 files can go on for ever, but streaming radio steadily fills up the Ram disk until the settings file can no longer be saved and the stream breaks. This is what the LMS log shows:
- oyvindo
- Experience counts
- Posts: 1399
- Joined: Tue May 19, 2009 2:08 am
- Location: Norway, Oslo
Re: [SOLVED] RAMDisk Full
Hey schumaku, good to see you - always on the watch - eh?
So if I understand you correctly, NAS root RAMdisk is not the same as /tmp ?
If so, from my DF -H list above, the "none 200.0M 169.2M 30.8M 85% /" is the RAMdisk (=200Mb)?
And the "tmpfs 64.0M 64.0M 0 100% /tmp" is my /tmp cache (=64Mb)?
Correct?
In addition, there seem to be another one named "tmpfs 64.0M 64.0M 0 100% /share/CACHEDEV1_DATA/.qpkg/HD_Station/tmp" which is also struggling? Is this just a symlink or another cache?
Which one caused QTS to start pumping out "Setting file cannot be saved..." (I seem to recall it mentioning /tmp) ?
So if I understand you correctly, NAS root RAMdisk is not the same as /tmp ?
If so, from my DF -H list above, the "none 200.0M 169.2M 30.8M 85% /" is the RAMdisk (=200Mb)?
And the "tmpfs 64.0M 64.0M 0 100% /tmp" is my /tmp cache (=64Mb)?
Correct?
In addition, there seem to be another one named "tmpfs 64.0M 64.0M 0 100% /share/CACHEDEV1_DATA/.qpkg/HD_Station/tmp" which is also struggling? Is this just a symlink or another cache?
Which one caused QTS to start pumping out "Setting file cannot be saved..." (I seem to recall it mentioning /tmp) ?
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: [SOLVED] RAMDisk Full
Yesoyvindo wrote:If so, from my DF -H list above, the "none 200.0M 169.2M 30.8M 85% /" is the RAMdisk (=200Mb)?
Yes, /tmp ...oyvindo wrote:And the "tmpfs 64.0M 64.0M 0 100% /tmp" is my /tmp cache (=64Mb)?
/tmp again ... and this is the same.oyvindo wrote:In addition, there seem to be another one named "tmpfs 64.0M 64.0M 0 100% /share/CACHEDEV1_DATA/.qpkg/HD_Station/tmp" which is also struggling?
Both can case issues - but it's the root RAM disk.oyvindo wrote:Which one caused QTS to start pumping out "Setting file cannot be saved..." (I seem to recall it mentioning /tmp) ?
- oyvindo
- Experience counts
- Posts: 1399
- Joined: Tue May 19, 2009 2:08 am
- Location: Norway, Oslo
Re: [SOLVED] RAMDisk Full
Aha, let me repeat that - just to make sure I got it right:
Despite the fact that the root RAMdisk with 200Mb is "only" 85% full, it is the one causing the problem, and NOT the 64Mb /tmp which is 100% full?
Despite the fact that the root RAMdisk with 200Mb is "only" 85% full, it is the one causing the problem, and NOT the 64Mb /tmp which is 100% full?
- schumaku
- Guru
- Posts: 43579
- Joined: Mon Jan 21, 2008 4:41 pm
- Location: Kloten (Zurich), Switzerland -- Skype: schumaku
- Contact:
Re: [SOLVED] RAMDisk Full
The root @85% does not cause issues - but the usage can grow temporarily. The 100% of /tmp is fatal enough for many apps, too.
- oyvindo
- Experience counts
- Posts: 1399
- Joined: Tue May 19, 2009 2:08 am
- Location: Norway, Oslo
Re: [SOLVED] RAMDisk Full
OK, that figures. Many thanks. I guess there is a way to find out what App and file is causing this, but is it worth the trouble to hunt it down as long the problem is random and can be solved by rebooting (at least for a while)?
-
- Experience counts
- Posts: 2415
- Joined: Wed Jan 08, 2014 10:34 pm
Re: [SOLVED] RAMDisk Full
Why not take a look inside it to see what's consuming the space, to get an idea of the root cause rather than the symptom?
TS-431+ for storage and media and a bunch of IP cams under Surveillance Station. TVS-473 as files backup and QVR Pro.
- oyvindo
- Experience counts
- Posts: 1399
- Joined: Tue May 19, 2009 2:08 am
- Location: Norway, Oslo
Re: [SOLVED] RAMDisk Full
... if I only knew how....