Displaying 2 results from an estimated 2 matches for "update_num_read_oplock".
Did you mean:
update_num_read_oplocks
2016 Apr 07
0
PANIC on update_num_read_oplocks
...64):
> Mar 7 15:18:54 xxxxxx smbd_audit[51710]: connect to service xxxxxxxxx by user XXXXXXXX\xxxxxxxx
> Mar 7 15:18:54 xxxxxx smbd_audit[51710]: open XXXXXXXXX/XXXXXXXXX.ods (fd 9)
> Mar 7 15:18:54 xxxxxx smbd_audit[51710]: [2016/03/07 15:18:54.364808, 0] ../source3/smbd/oplock.c:192(update_num_read_oplocks)
> Mar 7 15:18:54 xxxxxx smbd_audit[51710]: PANIC: assert failed at ../source3/smbd/oplock.c(192): d->num_share_modes == 1
> Mar 7 15:18:54 xxxxxx smbd_audit[51710]: [2016/03/07 15:18:54.364846, 0] ../source3/lib/util.c:789(smb_panic_s3)
> Mar 7 15:18:54 xxxxxx smbd_audit[51710]:...
2016 Mar 10
2
Debugging oplock.c core dumps
...now calmed down).
We have samba logging on level 1 at the moment. An output from one of the core dumps is as follows:
[2016/03/10 10:05:58.334288, 0] ../source3/lib/dumpcore.c:318(dump_core)
dumping core in /var/log/samba/cores/smbd
[2016/03/10 10:05:58.620827, 0] ../source3/smbd/oplock.c:192(update_num_read_oplocks)
PANIC: assert failed at ../source3/smbd/oplock.c(192): d->num_share_modes == 1
[2016/03/10 10:05:58.620905, 0] ../source3/lib/util.c:788(smb_panic_s3)
PANIC (pid 25524): assert failed: d->num_share_modes == 1
[2016/03/10 10:05:58.621578, 0] ../source3/lib/util.c:899(log_stack_trace)...