All shares lost - reboot required - error: unlink_node - 80 occurrences in last 131 days

It might help if you post the rest of the syslog, to see if there's something in common happening just before, this issue has usually been linked with other things interacting with /mnt/user, like a docker that directly manipulate files, e.g., renaming or moving them, also recently there was a case that was apparently caused by unmounting a remote share.

Try removing the recycle bin plugin.

Thanks for the replies. Appreciate it.

I do not have the recycle bin plugin installed.

I do not have any remote shares that are being locally mounted - this is the only NFS/SMB/AFP server on the network.

Full syslog from 6 separate occurrences attached in tgz. 

 

If you can recommend a way of identifying 

Quote

this issue has usually been linked with other things interacting with /mnt/user, like a docker that directly manipulate files, e.g., renaming or moving them,

Please advise. 

It would also be nice to see some progress on the actual bug fix. 

Cheers

syslog.tgz

I would guess because of this (presumably this has happened more than once)

Dec 25 20:12:34 fallout emhttpd: unclean shutdown detected

You've now got some cache pool problems

Dec 25 20:14:23 fallout kernel: BTRFS info (device sdo1): bdev /dev/sdo1 errs: wr 20410, rd 13244, flush 4, corrupt 0, gen 0
Dec 25 20:14:23 fallout kernel: BTRFS info (device sdo1): bdev /dev/sdp1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0
Dec 25 20:14:23 fallout kernel: BTRFS info (device sdo1): bdev /dev/nvme0n1p1 errs: wr 0, rd 17, flush 0, corrupt 0, gen 0

 

Those errors suggest one or more the devices dropped offline, see here for more info and better pool monitoring.