FCP reports OOM

[FreeMan]

Fix Common Problems has reported OOM errors and recommended I post diagnostics here.

 

Suggestions?

nas-diagnostics-20191222-1203.zip

[Frank1940]

 

 

 

 

I would suspect that one of your Dockers, plugins, or VM's is writing files to Unraid's RAM disk. (The boot process of Unraid sets up a RAM disk and installs Unraid onto that RAM disk.  To you, as a Linux user, and the Linux OS, this RAM disk appears to be a physical disk.  You (and the OS) can read ans write to it the same as a physical disk.)   Post up the results of these two commands:

 

ls -al /mnt

ls -al /mnt/user

You should also look through all of your Dockers, plugins, and VM's and make sure that any mapping that are used for any type of data storage are pointed at /mnt      If it is not, it is most likely pointed to the RAM disk!     

 

By the way, the events all happened about 22:00:16 on December 19th.  If you look in the syslog at that time, you can see it. 

[trurl]

Also note that any mapping to an Unassigned Device that isn't mounted is also in RAM.

[FreeMan]

root@NAS:/mnt/user# ls -al /mnt
total 32
drwxr-xr-x 13 root   root  260 Dec 13 08:02 ./
drwxr-xr-x 20 root   root  440 Dec 22 12:02 ../
drwxrwxrwx  1 nobody users  26 Dec 22 04:30 cache/
drwxrwxrwx 11 nobody users 169 Dec 22 04:30 disk1/
drwxrwxrwx  8 nobody users 117 Dec 22 04:30 disk2/
drwxrwxrwx  8 nobody users 117 Dec 22 04:30 disk3/
drwxrwxrwx  7 nobody users 101 Dec 22 04:30 disk4/
drwxrwxrwx 12 nobody users 187 Dec 22 04:30 disk5/
drwxrwxrwx  8 nobody users 117 Dec 22 04:31 disk6/
drwxrwxrwx  7 nobody users  95 Dec 22 04:31 disk7/
drwxrwxrwt  2 nobody users  40 Dec 13 08:02 disks/
drwxrwxrwx  1 nobody users  26 Dec 22 04:31 user/
drwxrwxrwx  1 nobody users 169 Dec 22 04:31 user0/

root@NAS:/mnt/user# ls -al /mnt/user
total 96
drwxrwxrwx  1 nobody users    26 Dec 22 04:31 ./
drwxr-xr-x 13 root   root    260 Dec 13 08:02 ../
drwxrwxrwx  1 nobody users   123 Jan  5  2019 Audio/
drwxrwxrwx  1 nobody users   153 Jul 27 13:11 Backups/
drwxrwxrwx  1 nobody users 20480 Jan  5  2019 Books/
drwxrwxrwx  1 nobody users    17 Jan 28  2019 Data/
drwxrwxrwx  1 nobody users  4096 Aug  1 04:20 Home\ Movies/
drwxrwxrwx  1 nobody users    89 Jun 20  2019 ISOs/
drwxrwxrwx  1 nobody users 20480 Dec 16 11:38 Movies/
drwxrwxrwx  1 nobody users    37 Jul 27 10:56 Photos/
drwxrwxrwx  1 nobody users  4096 Jul 26 18:48 Sport/
drwxrwxrwx  1 nobody users  8192 Sep 18 17:58 TV/
drwxrwxrwx  1 nobody users   608 Dec 14 20:00 appdata/
drwxrwxrwx  1 nobody users    80 Aug 20 18:52 domains/
drwxrwxrwx  1 nobody users    14 Jul 30  2018 system/

Nothing out of the ordinary, as far as I can see.

[Frank1940]

Have a look at    /mnt/disks   and be sure that any folders/directories are actual physical disks that are currently mounted.  Otherwise, the data will be on the RAM disk in memory.

[FreeMan]

Is empty:

drwxrwxrwt  2 nobody users  40 Dec 13 08:02 disks/

root@NAS:/mnt/user# ls -la /mnt/disks
total 0
drwxrwxrwt  2 nobody users  40 Dec 13 08:02 ./
drwxr-xr-x 13 root   root  260 Dec 13 08:02 ../

 

[trurl]

So do you have any dockers mapped to an Unassigned Device or anything else that might be trying to use one?

[FreeMan]

No. I have UD installed, and I have one remote SMB share mapped to my backup server, however, I'm not using it, even for the backups. I've switched to using rsync for that.

 

The only docker change I've made in several months (other than updates to existing ones) is the addition of Home Assistant, and after fiddling with it for a few minutes, I stopped it because I don't have any devices for it to control, and it's properly mapped to /mnt/cache...

 

[FreeMan]

14 hours ago, trurl said:

Also note that any mapping to an Unassigned Device that isn't mounted is also in RAM.

If I mount "MyExternalDrive" via UD, then unplug the device, but retain the docker mapping, unRAID will automatically write to a virtual "MyExternalDrive" that exists as, effectively, a RAM disk? That's handy, yet insidious!

[Frank1940]

6 minutes ago, FreeMan said:

If I mount "MyExternalDrive" via UD, then unplug the device, but retain the docker mapping, unRAID will automatically write to a virtual "MyExternalDrive" that exists as, effectively, a RAM disk? That's handy, yet insidious!

Like a two-headed snake...