Just upgraded to 6.7.0....

The link in your PM isn't working for me. Please email the logs in as per the instructions.

The samba problem is not a regression as you've been experiencing it on older firmware. Best to keep that discussion to the thread you just linked to.

I have just send my logs by email, as described by the procedure.

After performing OS reinstallation yesterday I was changing some options for volumes and shares and Frontview died again.

At the moment I am performing backup of the data from my NAS, before doing OS reinstallation again.

I have received this answer from your mail server after sending you logs downlaoded from the NAS as ZIP, 4MB filesize:: 

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error.

SMTP error from remote mail server after end of data
host mxa-001f3e01.gslb.pphosted.com [148.163.159.230]:
550 5.7.0 Message Size Violation

mdgm-ntgr In my case, an upgrade from 6.6.1 to 6.7.0 resulted in the RN104 running for a while, steadily getting more and more bogged down (noticable in SSH session, with Admin Page becoming unavailable, and RAIDar no longer able to connect, etc.), until the SSH connections hang altogether and the system eventually seems to crash with this:

bfq_lookup_next_entity+dc

on the LCD display.  I don't think it's gone more than an hour, and has been as quickly as ~15min., before things grind to a halt.  Have had to power-cycle a few times, as clean shutdown/reboot (by cmd line or power button) seems impossible by the time things really bog down.

While the system is churning, CPU seems to be split between kswapd0 (~40+%) and high I/O wait time.  Here is the last 'top' screen from one of the SSH sessions before it hung:

top - 12:24:13 up 49 min, 2 users, load average: 26.96, 24.60, 19.38
Tasks: 227 total, 2 running, 224 sleeping, 0 stopped, 1 zombie
%Cpu(s): 0.2 us, 89.0 sy, 0.0 ni, 0.0 id, 8.9 wa, 0.0 hi, 1.9 si, 0.0 st
KiB Mem: 508436 total, 492028 used, 16408 free, 220 buffers
KiB Swap: 1046524 total, 86516 used, 960008 free. 15224 cached Mem

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
415 root 20 0 0 0 0 R 42.4 0.0 14:43.05 kswapd0
2410 root 19 -1 232560 1152 168 S 2.8 0.2 2:14.20 readynasd
5603 root 19 -1 5396 288 80 D 1.9 0.1 0:01.54 msmtp
5604 root 20 0 8364 76 0 S 1.8 0.0 0:01.00 systemctl
1057 root 20 0 23676 280 168 D 1.6 0.1 0:20.32 systemd-jour+
1 root 20 0 27816 264 0 S 1.5 0.1 0:25.09 systemd
1027 root 0 -20 0 0 0 S 1.5 0.0 0:35.05 kworker/0:1H
5601 root 20 0 33292 316 0 D 1.4 0.1 0:01.31 afpd
3897 root 20 0 5684 960 608 R 1.2 0.2 0:40.14 top
2377 root 20 0 25312 448 332 D 1.2 0.1 0:24.56 nmbd
2808 root 20 0 17044 1308 824 D 1.2 0.3 0:53.16 apache2
2224 root 20 0 0 0 0 D 1.1 0.0 2:27.86 btrfs-cleaner
5569 root 20 0 33428 684 196 D 1.0 0.1 0:02.45 afpd
5462 admin 20 0 16668 644 308 D 0.8 0.1 0:06.64 apache2

The logs do show "Out of memory" errors, e.g.:

Apr 11 11:56:57 NASbox kernel: Out of memory: Kill process 2263 (forked-daapd) score 3 or sacrifice child
Apr 11 11:56:58 NASbox kernel: Killed process 2263 (forked-daapd) total-vm:75696kB, anon-rss:104kB, file-rss:0kB
Apr 11 11:56:58 NASbox kernel: readynasd invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=-1000
Apr 11 11:56:58 NASbox kernel: readynasd cpuset=/ mems_allowed=0

Have not been able to download logs from either Admin Page or RAIDar until finally booting read-only.  Can I send those logs to you?

thanks!

---

capaz wrote:

load average: 26.96, 24.60, 19.38

---

That's quite high... Also, your NAS is swapping memory then crashing out of memory. Uses too much CPU, too much RAM.

There's most likely some cleaning up to do, like disable the unused services, clean up the BTRFS volume, etc.

Use the link in mdgm signature to send him the logs.

msnasx you could check the logs zip to see if there are e.g. large backup job logs or something and perhaps split the logs into two separate zip files or let us know which log files you've left out in case we need them.

---

mdgm wrote:

msnasx you could check the logs zip to see if there are e.g. large backup job logs or something and perhaps split the logs into two separate zip files or let us know which log files you've left out in case we need them.

---

I have sent logs splitted in 2 emails. I don't have backup jobs. I still haven't rebooted my NAS but from time to time with is again not accessible and again after some time it comes back to normal. Definitely something isn't correct in this FW version. I'm looking forward to your feedback.