Hi Daniel
It looks indeed like a kernel panic, mostly happening under some load. I've checked the logs for the latest connection logs before (manual) reset, and here are the results:
26-10, 02:00: Freeze when scanning folders for music files, logs taken at 07:13:
Quote:
[2012/10/26 02:00:49.934090, 1] smbd/vfs.c:932(check_reduced_name)
check_reduced_name: couldn't get realpath for
24-10, 16:10: Freeze when re-applying security rights, logs taken at 16:50:
Quote:
[2012/10/24 04:00:39.437702, 1] smbd/vfs.c:932(check_reduced_name)
check_reduced_name: couldn't get realpath for
Quote:
[2012/10/24 16:10:18.187779, 0] modules/vfs_posixacl.c:349(smb_acl_to_posix):
smb_acl_to_posix: ACL is invalid for set (Invalid argument)
23-10, 00:21: Freeze, not clear what triggered the panic, logs taken at 07:40:
Quote:
[2012/10/23 00:01:35.570535, 1] smbd/vfs.c:932(check_reduced_name)
check_reduced_name: couldn't get realpath
Quote:
[2012/10/23 08:05:50.234214, 1] smbd/vfs.c:932(check_reduced_name)
check_reduced_name: couldn't get realpath
22-10, 15:06, Freeze, not clear what triggered the panic, logs taken at 21:54
Quote:
[2012/10/22 14:29:51.344227, 1] smbd/vfs.c:932(check_reduced_name)
check_reduced_name: couldn't get realpath for
Admittedly, when bringing the machine back up, I did not always run the filesystem check: there was simply not enough time for that.
Could any FS errors cause a kernel panic?