a632079
Members
-
Joined
-
Last visited
Everything posted by a632079
-
AS the image shown, as the ipv6 prefix changed, the network setting will be broken —— Thus the br0(or eth0 here) can't be created as rc.docker start.
-
I found a ssh terminated issue maybe related to previous issues: ssh can't connect. Reason: the ssh terminated and restart: report no address can to listen. After sshd can't start, the /etc/rc.d/rc.sshd restart will report: no parent sshd instance exist and exited. So that the ssh always die since that time point. ``` Aug 31 09:39:30 OuO sshd[19782]: error: Bind to port 22 on 2409:8a20:****:4cff:fee2:3a failed: Cannot assign requested address. Aug 31 09:39:30 OuO sshd[19782]: Server listening on 192.168.63.190 port 22. Aug 31 09:41:32 OuO sshd[3902]: Read error from remote host 192.168.63.172 port 53943: Connection reset by peer Aug 31 09:41:32 OuO sshd[3902]: pam_unix(sshd:session): session closed for user root Aug 31 09:41:32 OuO network: reload service: sshd Aug 31 09:41:32 OuO sshd[19782]: Received signal 15; terminating. Aug 31 09:41:32 OuO sshd[21965]: error: Bind to port 22 on 2409:8a20:****:4cff:fee2:3a failed: Cannot assign requested address. Aug 31 09:41:32 OuO sshd[21965]: fatal: Cannot bind any address. ```
-
As this post points that The docker script will use $IPV6(2409:xxxx:xxxx:5ee0::4b8/128) to get $SUBNET6(2409:xxxx:xxxx:5ee0::/64) via ip -6 route show dev $NETWORK $IPV6|awk '{print $1;exit}' It will case $SUBNET6 be null, and $GATEWAY6 always be 1 —— So that it leads to br0: ipv6 is disabled in docker network inspect.
-
I have figured out what is occurred this issue. More detail you can find at In a short, it might be a Unraid bug.
-
I meet another issue, the subnet6 is not match with ipv6 in your scripts, and lead to gateway6 always be 1. The key script block: The Current result, subnet and ipv6: As this block done, the result is like: And the script's GATEWAY6 will always be “1” So I think, that is a bug, isn't that?
-
I have figured out what lead to this issue. —— Enabled Host access to custom networks. --------------- It created a interface, called shim-br0, and do network configuration(configure route, etc) manually. But, Why? Why disable ipv6 is needed to in favor of this feature in unraid 6.12, however, it is not in 6.11? @JorgeB
-
I faced this issue too. But the official support engineer is not responded, as it not happened.
-
Maybe is gateway issue?
-
You can see: Here, the enableIpv6 is false, while the bridge network is enabled. This is my unraid docker config. Output of ip a & ip r Output of docker version & docker info
-
Hi, I woke up in the morning and found that Unraid NAS cannot respond to any requests, including SSH, SMB, WEBUI. The following is the system log I rescued (the log is written to Flash). The NAS has a screen and keyboard plugged into it. At this time, the screen does not respond (no signal), the keyboard light is on, but typing CTRL+ALT+DELETE cannot complete the restart operation. Aug 3 01:57:28 OuO avahi-daemon[15911]: Withdrawing address record for 2409:8a20:5214:4c90::4b8 on br0. Aug 3 01:57:31 OuO ntpd[6698]: Deleting interface #3 br0, 2409:8a20:5214:4c90::4b8#123, interface stats: received=0, sent=0, dropped=0, active_time=28179 secs Aug 3 02:01:02 OuO rpc.statd[1522]: Version 2.6.2 starting Aug 3 02:01:02 OuO sm-notify[1523]: Version 2.6.2 starting Aug 3 02:01:02 OuO sm-notify[1523]: Already notifying clients; Exiting! Aug 3 02:01:02 OuO rpc.mountd[6575]: Caught signal 15, un-registering and exiting. Aug 3 02:01:03 OuO kernel: nfsd: last server has exited, flushing export cache Aug 3 02:01:05 OuO kernel: NFSD: Using UMH upcall client tracking operations. Aug 3 02:01:05 OuO kernel: NFSD: starting 90-second grace period (net f0000000) Aug 3 02:01:05 OuO rpc.mountd[1679]: Version 2.6.2 starting Aug 3 02:01:05 OuO ntpd[6698]: ntpd exiting on signal 1 (Hangup) Aug 3 02:01:05 OuO ntpd[6698]: 127.127.1.0 local addr 127.0.0.1 -> <null> Aug 3 02:01:05 OuO ntpd[6698]: 106.55.184.199 local addr 192.168.63.190 -> <null> Aug 3 02:01:05 OuO ntpd[6698]: 203.107.6.88 local addr 192.168.63.190 -> <null> Aug 3 02:01:05 OuO ntpd[6698]: 40.119.6.228 local addr 192.168.63.190 -> <null> Aug 3 02:01:05 OuO ntpd[6698]: 216.239.35.12 local addr 192.168.63.190 -> <null> Aug 3 02:01:05 OuO ntpd[1798]: ntpd [email protected] Tue Jun 6 17:07:37 UTC 2023 (1): Starting Aug 3 02:01:05 OuO ntpd[1798]: Command line: /usr/sbin/ntpd -g -u ntp:ntp Aug 3 02:01:05 OuO ntpd[1798]: ---------------------------------------------------- Aug 3 02:01:05 OuO ntpd[1798]: ntp-4 is maintained by Network Time Foundation, Aug 3 02:01:05 OuO ntpd[1798]: Inc. (NTF), a non-profit 501(c)(3) public-benefit Aug 3 02:01:05 OuO ntpd[1798]: corporation. Support and training for ntp-4 are Aug 3 02:01:05 OuO ntpd[1798]: available at https://www.nwtime.org/support Aug 3 02:01:05 OuO ntpd[1798]: ---------------------------------------------------- Aug 3 02:01:05 OuO ntpd[1798]: DEBUG behavior is enabled - a violation of any Aug 3 02:01:05 OuO ntpd[1798]: diagnostic assertion will cause ntpd to abort Aug 3 02:01:05 OuO ntpd[1800]: proto: precision = 0.065 usec (-24) Aug 3 02:01:05 OuO ntpd[1800]: basedate set to 2023-05-25 Aug 3 02:01:05 OuO ntpd[1800]: gps base set to 2023-05-28 (week 2264) Aug 3 02:01:05 OuO ntpd[1800]: initial drift restored to 21.963000 Aug 3 02:01:05 OuO ntpd[1800]: Listen normally on 0 lo 127.0.0.1:123 Aug 3 02:01:05 OuO ntpd[1800]: Listen normally on 1 br0 192.168.63.190:123 Aug 3 02:01:05 OuO ntpd[1800]: Listen normally on 2 lo [::1]:123 Aug 3 02:01:05 OuO ntpd[1800]: Listen normally on 3 br0 [2409:8a20:5214:4c90:2e0:4cff:fee2:3a]:123 Aug 3 02:01:05 OuO ntpd[1800]: Listening on routing socket on fd #20 for interface updates Aug 3 02:01:05 OuO ntpd[1800]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Aug 3 02:01:05 OuO ntpd[1800]: kernel reports TIME_ERROR: 0x2041: Clock Unsynchronized Aug 3 02:01:06 OuO rpc.mountd[1679]: v4.2 client attached: 0x6de53e6564ca99e0 from "192.168.63.201:720" Aug 3 02:01:09 OuO sshd[7103]: Received signal 15; terminating. Aug 3 02:01:09 OuO sshd[2125]: Server listening on 2409:8a20:5214:4c90:2e0:4cff:fee2:3a port 22. Aug 3 02:01:09 OuO sshd[2125]: Server listening on 192.168.63.190 port 22. Aug 3 02:01:09 OuO winbindd[6023]: [2023/08/03 02:01:09.840967, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Aug 3 02:01:09 OuO winbindd[6023]: Got sig[15] terminate (is_parent=0) Aug 3 02:01:09 OuO wsdd2[15828]: 'Terminated' signal received. Aug 3 02:01:09 OuO winbindd[15834]: [2023/08/03 02:01:09.842757, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Aug 3 02:01:09 OuO winbindd[15834]: Got sig[15] terminate (is_parent=0) Aug 3 02:01:09 OuO winbindd[15831]: [2023/08/03 02:01:09.842772, 0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler) Aug 3 02:01:09 OuO winbindd[15831]: Got sig[15] terminate (is_parent=1) Aug 3 02:01:09 OuO wsdd2[15828]: terminating. Aug 3 02:01:09 OuO smbd[2277]: [2023/08/03 02:01:09.938190, 0] ../../source3/smbd/server.c:1741(main) Aug 3 02:01:09 OuO smbd[2277]: smbd version 4.17.7 started. Aug 3 02:01:09 OuO smbd[2277]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Aug 3 02:01:10 OuO wsdd2[2291]: starting. Aug 3 02:01:10 OuO winbindd[2292]: [2023/08/03 02:01:10.068837, 0] ../../source3/winbindd/winbindd.c:1440(main) Aug 3 02:01:10 OuO winbindd[2292]: winbindd version 4.17.7 started. Aug 3 02:01:10 OuO winbindd[2292]: Copyright Andrew Tridgell and the Samba Team 1992-2022 Aug 3 02:01:10 OuO winbindd[2294]: [2023/08/03 02:01:10.075578, 0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache) Aug 3 02:01:10 OuO winbindd[2294]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 In addition, this machine also encountered the problem of nginx not responding yesterday (old problem). The following is the diary when nginx encountered problems at that time, maybe it will help with this problem? (Only part of the diary is intercepted) Aug 2 13:26:57 OuO kernel: nginx[6095]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 13 (core 3, socket 0) Aug 2 13:26:57 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:57 OuO emhttpd: error: publish, 172: Connection reset by peer (104): read Aug 2 13:26:57 OuO nginx: 2023/08/02 13:26:57 [alert] 6811#6811: worker process 6095 exited on signal 11 Aug 2 13:26:57 OuO kernel: nginx[6099]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 5 (core 8, socket 0) Aug 2 13:26:57 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:57 OuO nginx: 2023/08/02 13:26:57 [alert] 6811#6811: worker process 6099 exited on signal 11 Aug 2 13:26:58 OuO kernel: nginx[6100]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 1 (core 1, socket 0) Aug 2 13:26:58 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:58 OuO nginx: 2023/08/02 13:26:58 [alert] 6811#6811: worker process 6100 exited on signal 11 Aug 2 13:26:58 OuO kernel: nginx[6115]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 13 (core 3, socket 0) Aug 2 13:26:58 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:58 OuO nginx: 2023/08/02 13:26:58 [alert] 6811#6811: worker process 6115 exited on signal 11 Aug 2 13:26:58 OuO kernel: nginx[6116]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 2 (core 2, socket 0) Aug 2 13:26:58 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:58 OuO nginx: 2023/08/02 13:26:58 [alert] 6811#6811: worker process 6116 exited on signal 11 Aug 2 13:26:58 OuO kernel: nginx[6120]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 16 (core 9, socket 0) Aug 2 13:26:58 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:58 OuO emhttpd: error: publish, 172: Connection reset by peer (104): read Aug 2 13:26:58 OuO nginx: 2023/08/02 13:26:58 [alert] 6811#6811: worker process 6120 exited on signal 11 Aug 2 13:26:58 OuO kernel: nginx[6124]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 16 (core 9, socket 0) Aug 2 13:26:58 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:58 OuO nginx: 2023/08/02 13:26:58 [alert] 6811#6811: worker process 6124 exited on signal 11 Aug 2 13:26:58 OuO kernel: nginx[6171]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 6 (core 9, socket 0) Aug 2 13:26:58 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:58 OuO nginx: 2023/08/02 13:26:58 [alert] 6811#6811: worker process 6171 exited on signal 11 Aug 2 13:26:59 OuO kernel: nginx[6383]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 2 (core 2, socket 0) Aug 2 13:26:59 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:59 OuO nginx: 2023/08/02 13:26:59 [alert] 6811#6811: worker process 6383 exited on signal 11 Aug 2 13:26:59 OuO kernel: nginx[6429]: segfault at 7f8 ip 00000000004e6982 sp 00007ffdfeaee000 error 6 in nginx[424000+110000] likely on CPU 2 (core 2, socket 0) Aug 2 13:26:59 OuO kernel: Code: 31 c0 e8 31 12 f4 ff e9 6f ff ff ff 48 8b 7c 24 08 e8 d2 62 f4 ff 49 89 c6 48 85 c0 0f 88 a4 00 00 00 4c 89 ef e8 de 54 02 00 <4c> 89 70 08 e9 4d fc ff ff be f3 01 00 00 e8 cb 28 f8 ff 48 c7 c0 Aug 2 13:26:59 OuO nginx: 2023/08/02 13:26:59 [alert] 6811#6811: worker process 6429 exited on signal 11 Aug 2 13:26:59 OuO emhttpd: error: publish, 172: Connection reset by peer (104): read Aug 2 13:26:59 OuO nginx: 2023/08/02 13:26:59 [alert] 6811#6811: worker process 6433 exited on signal 11 Aug 2 13:26:59 OuO nginx: 2023/08/02 13:26:59 [alert] 6811#6811: worker process 6437 exited on signal 11 Aug 2 13:26:59 OuO emhttpd: error: publish, 172: Connection reset by peer (104): read Aug 2 13:26:59 OuO emhttpd: error: publish, 172: Connection reset by peer (104): read Aug 2 13:26:59 OuO nginx: 2023/08/02 13:26:59 [alert] 6811#6811: worker process 6438 exited on signal 11 Aug 2 13:26:59 OuO nginx: 2023/08/02 13:26:59 [alert] 6811#6811: worker process 6439 exited on signal 11 Aug 2 13:27:00 OuO nginx: 2023/08/02 13:27:00 [alert] 6811#6811: worker process 6441 exited on signal 11 Aug 2 13:27:00 OuO nginx: 2023/08/02 13:27:00 [alert] 6811#6811: worker process 6443 exited on signal 11 Aug 2 13:27:00 OuO emhttpd: error: publish, 172: Connection reset by peer (104): read Aug 2 13:27:00 OuO nginx: 2023/08/02 13:27:00 [alert] 6811#6811: worker process 6447 exited on signal 11 Aug 2 13:27:00 OuO nginx: 2023/08/02 13:27:00 [alert] 6811#6811: worker process 6451 exited on signal 11 Aug 2 13:27:00 OuO nginx: 2023/08/02 13:27:00 [alert] 6811#6811: worker process 6452 exited on signal 11 Aug 2 13:27:00 OuO nginx: 2023/08/02 13:27:00 [alert] 6811#6811: worker process 6466 exited on signal 11 Aug 2 13:27:01 OuO nginx: 2023/08/02 13:27:01 [alert] 6811#6811: worker process 6497 exited on signal 11 Aug 2 13:27:01 OuO nginx: 2023/08/02 13:27:01 [alert] 6811#6811: worker process 6499 exited on signal 11 Aug 2 13:27:01 OuO emhttpd: error: publish, 172: Connection reset by peer (104): read Aug 2 13:27:01 OuO nginx: 2023/08/02 13:27:01 [alert] 6811#6811: worker process 6503 exited on signal 11 Aug 2 13:27:01 OuO nginx: 2023/08/02 13:27:01 [alert] 6811#6811: worker process 6535 exited on signal 11 Aug 2 13:27:01 OuO nginx: 2023/08/02 13:27:01 [alert] 6811#6811: worker process 6536 exited on signal 11 Aug 2 13:27:02 OuO kernel: show_signal_msg: 15 callbacks suppressed Before this, encountered nginx nchan's memory exhaustion bug (old problem, I had to restart nginx regularly). Frankly, if unraid needs to use websockets, why not try using Swoole? (an event-driven, asynchronous, coroutine-based concurrency library with high performance for PHP) Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [crit] 32748#32748: ngx_slab_alloc() failed: no memory Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [error] 32748#32748: shpool alloc failed Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [error] 32748#32748: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [error] 32748#32748: *254332 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [crit] 32748#32748: ngx_slab_alloc() failed: no memory Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [error] 32748#32748: shpool alloc failed Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [error] 32748#32748: nchan: Out of shared memory while allocating channel /temperature. Increase nchan_max_reserved_memory. Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [alert] 32748#32748: *254333 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:10 OuO kernel: nginx[32748]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 5 (core 8, socket 0) Aug 2 01:21:10 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:10 OuO nginx: 2023/08/02 01:21:10 [alert] 6811#6811: worker process 32748 exited on signal 11 Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [crit] 348#348: ngx_slab_alloc() failed: no memory Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [error] 348#348: shpool alloc failed Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [error] 348#348: nchan: Out of shared memory while allocating channel m/ Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [alert] 348#348: *254335 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:11 OuO kernel: nginx[348]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 8 (core 11, socket 0) Aug 2 01:21:11 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [alert] 6811#6811: worker process 348 exited on signal 11 Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [crit] 350#350: ngx_slab_alloc() failed: no memory Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [error] 350#350: shpool alloc failed Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [error] 350#350: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [error] 350#350: *254337 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [crit] 350#350: ngx_slab_alloc() failed: no memory Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [error] 350#350: shpool alloc failed Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [error] 350#350: nchan: Out of shared memory while allocating channel /temperature. Increase nchan_max_reserved_memory. Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [alert] 350#350: *254338 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:11 OuO kernel: nginx[350]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 18 (core 11, socket 0) Aug 2 01:21:11 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:11 OuO nginx: 2023/08/02 01:21:11 [alert] 6811#6811: worker process 350 exited on signal 11 Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [crit] 354#354: ngx_slab_alloc() failed: no memory Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [error] 354#354: shpool alloc failed Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [error] 354#354: nchan: Out of shared memory while allocating channel m/ Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [alert] 354#354: *254340 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:12 OuO kernel: nginx[354]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 7 (core 10, socket 0) Aug 2 01:21:12 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [alert] 6811#6811: worker process 354 exited on signal 11 Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [crit] 355#355: ngx_slab_alloc() failed: no memory Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [error] 355#355: shpool alloc failed Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [error] 355#355: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:12 OuO nginx: 2023/08/02 01:21:12 [error] 355#355: *254342 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [crit] 355#355: ngx_slab_alloc() failed: no memory Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [error] 355#355: shpool alloc failed Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [error] 355#355: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [error] 355#355: *254343 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [crit] 355#355: ngx_slab_alloc() failed: no memory Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [error] 355#355: shpool alloc failed Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [error] 355#355: nchan: Out of shared memory while allocating channel /temperature. Increase nchan_max_reserved_memory. Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [alert] 355#355: *254344 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:13 OuO kernel: nginx[355]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 5 (core 8, socket 0) Aug 2 01:21:13 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:13 OuO nginx: 2023/08/02 01:21:13 [alert] 6811#6811: worker process 355 exited on signal 11 Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [crit] 443#443: ngx_slab_alloc() failed: no memory Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: shpool alloc failed Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: *254346 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [crit] 443#443: ngx_slab_alloc() failed: no memory Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: shpool alloc failed Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: nchan: Out of shared memory while allocating channel /shares. Increase nchan_max_reserved_memory. Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: *254347 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/shares?buffer_length=1 HTTP/1.1", host: "localhost" Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [crit] 443#443: ngx_slab_alloc() failed: no memory Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: shpool alloc failed Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:14 OuO nginx: 2023/08/02 01:21:14 [error] 443#443: *254348 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [crit] 443#443: ngx_slab_alloc() failed: no memory Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [error] 443#443: shpool alloc failed Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [error] 443#443: nchan: Out of shared memory while allocating channel /temperature. Increase nchan_max_reserved_memory. Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [alert] 443#443: *254349 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:15 OuO kernel: nginx[443]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 0 (core 0, socket 0) Aug 2 01:21:15 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [alert] 6811#6811: worker process 443 exited on signal 11 Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [crit] 447#447: ngx_slab_alloc() failed: no memory Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [error] 447#447: shpool alloc failed Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [error] 447#447: nchan: Out of shared memory while allocating channel m/ Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [alert] 447#447: *254351 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:15 OuO kernel: nginx[447]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 3 (core 3, socket 0) Aug 2 01:21:15 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [alert] 6811#6811: worker process 447 exited on signal 11 Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [crit] 451#451: ngx_slab_alloc() failed: no memory Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [error] 451#451: shpool alloc failed Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [error] 451#451: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:15 OuO nginx: 2023/08/02 01:21:15 [error] 451#451: *254353 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [crit] 451#451: ngx_slab_alloc() failed: no memory Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [error] 451#451: shpool alloc failed Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [error] 451#451: nchan: Out of shared memory while allocating channel m/ Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [alert] 451#451: *254354 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:16 OuO kernel: nginx[451]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 6 (core 9, socket 0) Aug 2 01:21:16 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [alert] 6811#6811: worker process 451 exited on signal 11 Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [crit] 452#452: ngx_slab_alloc() failed: no memory Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [error] 452#452: shpool alloc failed Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [error] 452#452: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:16 OuO nginx: 2023/08/02 01:21:16 [error] 452#452: *254356 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [crit] 452#452: ngx_slab_alloc() failed: no memory Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [error] 452#452: shpool alloc failed Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [error] 452#452: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [error] 452#452: *254357 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost"Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [crit] 452#452: ngx_slab_alloc() failed: no memory Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [error] 452#452: shpool alloc failed Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [error] 452#452: nchan: Out of shared memory while allocating channel /temperature. Increase nchan_max_reserved_memory. Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [alert] 452#452: *254358 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:17 OuO kernel: nginx[452]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 0 (core 0, socket 0) Aug 2 01:21:17 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:17 OuO nginx: 2023/08/02 01:21:17 [alert] 6811#6811: worker process 452 exited on signal 11 Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [crit] 459#459: ngx_slab_alloc() failed: no memory Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [error] 459#459: shpool alloc failed Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [error] 459#459: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [error] 459#459: *254360 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [crit] 459#459: ngx_slab_alloc() failed: no memory Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [error] 459#459: shpool alloc failed Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [error] 459#459: nchan: Out of shared memory while allocating channel m/ Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [alert] 459#459: *254361 header already sent while keepalive, client: 192.168.63.123, server: 192.168.63.190:80 Aug 2 01:21:18 OuO kernel: nginx[459]: segfault at 0 ip 0000000000000000 sp 00007ffdfeaee138 error 14 in nginx[400000+24000] likely on CPU 8 (core 11, socket 0) Aug 2 01:21:18 OuO kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [alert] 6811#6811: worker process 459 exited on signal 11 Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [crit] 463#463: ngx_slab_alloc() failed: no memory Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [error] 463#463: shpool alloc failed Aug 2 01:21:18 OuO nginx: 2023/08/02 01:21:18 [error] 463#463: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory.
-
Firstly, while Docker is enabled, I observed that the system memory usage reported by free -mh shows that 19GB of memory has been used. However, when calculating the memory usage using docker stats and ps -ef commands, the total memory usage doesn't exceed 5GB. So, where did this additional memory go? root@OuO:~# awk '$3=="kB"{if ($2>1024^2){$2=$2/1024^2;$3="GB";} else if ($2>1024){$2=$2/1024;$3="MB";}} 1' /proc/meminfo | column -t MemTotal: 31.2649 GB MemFree: 4.54373 GB MemAvailable: 11.534 GB Buffers: 588 kB Cached: 7.0594 GB SwapCached: 0 kB Active: 1.10014 GB Inactive: 7.43252 GB Active(anon): 262.469 MB Inactive(anon): 1.54342 GB Active(file): 864.074 MB Inactive(file): 5.8891 GB Unevictable: 16 kB Mlocked: 16 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 96 kB Writeback: 0 kB AnonPages: 1.16288 GB Mapped: 5.21825 GB Shmem: 338.344 MB KReclaimable: 722.168 MB Slab: 1.03822 GB SReclaimable: 722.168 MB SUnreclaim: 340.969 MB KernelStack: 15.9609 MB PageTables: 1.1418 GB SecPageTables: 0 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 15.6324 GB Committed_AS: 4.13858 GB VmallocTotal: 32768 GB VmallocUsed: 762.547 MB VmallocChunk: 0 kB Percpu: 10.875 MB AnonHugePages: 596 MB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB FileHugePages: 0 kB FilePmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2 MB Hugetlb: 0 kB DirectMap4k: 238.758 MB DirectMap2M: 9.67188 GB DirectMap1G: 24 GB Please provide the diagnostic report for further analysis. ouo-diagnostics-20230610-2348.zip Afterwards, I disabled the Docker service through the Unraid dashboard, and the memory usage decreased to 16GB. Why does Unraid require such a large amount of memory? So, which component is causing the issue? root@OuO:~# free -m total used free shared buff/cache available Mem: 32015 17014 9140 339 5860 14202 Swap: 0 0 0 root@OuO:~# htop root@OuO:~# cat /proc/meminfo MemTotal: 32783620 kB MemFree: 9367160 kB MemAvailable: 14551840 kB Buffers: 1364 kB Cached: 5622700 kB SwapCached: 0 kB Active: 783700 kB Inactive: 5084084 kB Active(anon): 263784 kB Inactive(anon): 327228 kB Active(file): 519916 kB Inactive(file): 4756856 kB Unevictable: 64 kB Mlocked: 64 kB SwapTotal: 0 kB SwapFree: 0 kB Dirty: 0 kB Writeback: 0 kB AnonPages: 241248 kB Mapped: 94604 kB Shmem: 347292 kB KReclaimable: 377548 kB Slab: 727792 kB SReclaimable: 377548 kB SUnreclaim: 350244 kB KernelStack: 9296 kB PageTables: 8380 kB SecPageTables: 0 kB NFS_Unstable: 0 kB Bounce: 0 kB WritebackTmp: 0 kB CommitLimit: 16391808 kB Committed_AS: 854076 kB VmallocTotal: 34359738367 kB VmallocUsed: 819984 kB VmallocChunk: 0 kB Percpu: 11136 kB AnonHugePages: 47104 kB ShmemHugePages: 0 kB ShmemPmdMapped: 0 kB FileHugePages: 0 kB FilePmdMapped: 0 kB CmaTotal: 0 kB CmaFree: 0 kB HugePages_Total: 0 HugePages_Free: 0 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB Hugetlb: 0 kB DirectMap4k: 244488 kB DirectMap2M: 10141696 kB DirectMap1G: 25165824 kB Please provide the current diagnostic report for further analysis. ouo-diagnostics-20230610-2356.zip ouo-diagnostics-20230610-2356.zip
-
By the way, can we add an additional option to the "Script to run before mover (No checks, always runs)" scripts, or simply introduce a new setting called "Script to run before mover (if filters are not triggered)"? I have a PT (Private Tracker) client running on my server, and the mover regularly checks for mover conditions every day. Since I have allocated a large cache pool, in most cases, the mover is not triggered. However, when the script runs, it pauses my BT (BitTorrent) software, causing me to lose out on continuous seeding rewards. This has been a bit of a concern for me.
-
-
@hugenbdd cc. Hello, since the last time I shared the limitations of ZFS support, I have made further modifications to the plugin and added support for file system detection. I believe that Unraid 6.12-rc6 is now stable enough to ensure that the content of the ZFS capacity query will not be altered (even if it is altered, it will not affect the functionality of the zpool). Here is the function I use to determine the file system type using the findmnt command. If there is a conflict between CACHEPOOLNAME and the name of the mount point, please let me know! I will fix this issue. function is_zfs_mountpoint_fstype() { local result result=`findmnt $1 -o fstype | tail -n 1` [ "$result" = "zfs" ] return } `is_zfs_mountpoint_fstype "cache"` echo $? # it should be return 0 or 1 I added this function to the file /usr/local/emhttp/plugins/ca.mover.tuning/age_mover. In addition, I made modifications in two places regarding the usage of POOLPCTUSED. POOLPATH=/mnt/$(basename "$POOL" .cfg) if is_zfs_mountpoint_fstype "$POOLPATH" ; then mvlogger "$POOLPATH is zfs." POOLPCTUSEDA=`zpool get -o value capacity $(basename "$POOL" .cfg) | tail -n 1 | tr -d '%'` else POOLPCTUSEDA=`df --output=pcent $POOLPATH | tail -n 1 | tr -d '%'` fi if is_zfs_mountpoint_fstype "/mnt/$CACHEPOOLNAME" ; then mvlogger "$CACHEPOOLNAME is zfs." POOLPCTUSED=`zpool get -o value capacity $CACHEPOOLNAME | tail -n 1 | tr -d '%'` else POOLPCTUSED=`df --output=pcent /mnt/$CACHEPOOLNAME | tail -n 1 | tr -d '%'` fi By modifying the above content, mover tuning can now correctly identify the cache partition usage of ZFS and provide compatibility features for Btrfs and XFS. The following is the log content using this configuration. mvlogger: *********************************MOVER START******************************* mvlogger: Age supplied 0 mvlogger: Size supplied mvlogger: Sparness supplied mvlogger: No Skipfiles Argument Supplied mvlogger: No Skipfiles Argument Supplied mvlogger: BEFORESCRIPT: /mnt/user/appdata/Scripts/on_mover_start.sh mvlogger: AFTERSCRIPT: /mnt/user/appdata/Scripts/on_mover_stop.sh mvlogger: CTIME Argument: no mvlogger: CACHE THRESH to Move all Cache-Yes shares to array: 85 mvlogger: No Test Mode Argument Supplied mvlogger: No Ignore Hidden Files Argument Supplied mvlogger: Before script will be executed: /mnt/user/appdata/Scripts/on_mover_start.sh mvlogger: CACHETHRESH: 85 mvlogger: Checking to see if we should all files from share. mvlogger: Move All Cache Threshold: 85 mvlogger: /mnt/cache is zfs. mvlogger: /mnt/cache PCT USED: 82 mvlogger: Done checking Move All from Share mvlogger: Share Name Only: NAS mvlogger: Cache Pool Name: cache mvlogger: cache Threshold Pct: mvlogger: OVERALL Threshold: 35 mvlogger: Share Path: /mnt/cache/NAS mvlogger: cache is zfs. mvlogger: Pool Pct Used: 82 % mvlogger: DFTPCT LIMIT USED FOR SETTING: 35 mvlogger: Threshold Used: 35 mvlogger: Adding Size mvlogger: Size 100 mvlogger: Skipfiletypes string: find "/mnt/cache/NAS" -depth -size +100M mvlogger: Share Name Only: isos mvlogger: Cache Pool Name: cache mvlogger: cache Threshold Pct: mvlogger: OVERALL Threshold: 35 mvlogger: Share Path: /mnt/cache/isos mvlogger: cache is zfs. mvlogger: Pool Pct Used: 82 % mvlogger: DFTPCT LIMIT USED FOR SETTING: 35 mvlogger: Threshold Used: 35 mvlogger: Adding Size mvlogger: Size 100 mvlogger: Skipfiletypes string: find "/mnt/cache/isos" -depth -size +100M mvlogger: after customFilelist mvlogger: After totalsizeFilelist mvlogger: -----------------------------------------Running Array Files to Cache drives----------------------------------------------
-
建议先move到阵列然后干掉 重新格式化或者再试试你想试的方案。 btrfs 不懂随便操作很容易炸。 PP.SS btrfs raid5 模式还没有 stable。状态还是 mostly production。
-
Any updates here recently？
-
需要根据 TOP 以及 iostst -x 的信息来分析的。光看这个看不出具体原因的。
-
网络问题，解决网络问题即可备份。
-
有 ECC 的话也是换 ZFS 比较好，半月前啥都没整，RAID 0 Balance 到了八十九文件系统就自己炸只读了...... 修了半天没修好，恢复数据还丢了 300GiB.
-
Hello, I am using Unraid v6.12.0-rc5 with ZFS based cache pool. The `Pool Pct Used` value always be `1%` because this command just fetch `/mnt/cache`'s percentage usage. The `df -h` messae: ``` cache 142G 128K 142G 1% /mnt/cache cache/appdata 142G 165M 142G 1% /mnt/cache/appdata cache/system 147G 5.9G 142G 4% /mnt/cache/system cache/domains 165G 24G 142G 15% /mnt/cache/domains ``` So, we can't get zpool usage just by df. Maybe we can try zpool command to get usage: ``` zpool get -o value capacity cache | tail -n1 ``` it returns ``` 86% ``` I have temporary changed this line in mover_age: ``` POOLPCTUSED=`df --output=pcent /mnt/$CACHEPOOLNAME | tail -n 1 | tr -d '%'` ``` to ``` POOLPCTUSED=`zpool get -o value capacity cache | tail -n 1 | tr -d '%'` ``` Maybe we should determine which command should be used by judging which fs is used.
