Hey @all 

my unraid server just completly filled my log device.

i was able to save a diagnostigs file.

could someone tell me what was happening here?

i've resized the logdev to 4096M but is was filling up again.

 

reboot was only possible with a hard reboot from cli, rebooting in gui did not work. 

Also stopping the array and unmounting usershares did not respond.

 

thanks alot, i'm kinda worried.

tower-diagnostics-20221012-0902.zip

Possibly not the only problem, but it's a problem, so start here:

 

Oct  7 10:21:22 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Oct  7 10:21:22 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

 

Then reboot to clear the logs and post new diags if there are other issues.

2 hours ago, JorgeB said:

Possibly not the only problem, but it's a problem, so start here:

 

Oct  7 10:21:22 Tower kernel: macvlan_broadcast+0x10a/0x150 [macvlan]
Oct  7 10:21:22 Tower kernel: macvlan_process_broadcast+0xbc/0x12f [macvlan]

 

Macvlan call traces are usually the result of having dockers with a custom IP address and will end up crashing the server, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

 

Then reboot to clear the logs and post new diags if there are other issues.

I will do so asap. Will report, thanks 

So, switched to ipvlan and rebooted the server cleanly.

here is the new diag file

tower-diagnostics-20221012-1355.zip

Looks good so far, post new diags if the log starts filling up again.

Perfect, i will do so if...

 

thannks again for your always perfect help jorge