Displaying 4 results from an estimated 4 matches for "smbd_smb2_setinfo_send".
Did you mean:
smbd_smb2_getinfo_send
2016 Mar 25
0
Setting FS Quota against SAMBA share from windows2k12
...rror for the
> SMB2 setinfo request. Attached the packet capture for your reference.
>
> SAMBA version 4.3.4
>
> The below is the corresponding debug log
>
> [2016/03/25 10:38:21.333815, 10, pid=17987, effective(0, 110000513),
> real(0, 0)] ../source3/smbd/smb2_setinfo.c:379(smbd_smb2_setinfo_send)
> smbd_smb2_setinfo_send: $Extend/$Quota:$Q:$INDEX_ALLOCATION - fnum
> 2762575723
> [2016/03/25 10:38:21.333824, 10, pid=17987, effective(0, 110000513),
> real(0, 0)] ../source3/smbd/smb2_server.c:2789(smbd_smb2_request_error_ex)
> smbd_smb2_request_error_ex: idx[1] status[NT_ST...
2016 Mar 30
0
Fwd: Fwd: Setting FS Quota against SAMBA share from windows2k12
...t; > > > SAMBA version 4.3.4
> > > >
> > > > The below is the corresponding debug log
> > > >
> > > > [2016/03/25 10:38:21.333815, 10, pid=17987, effective(0, 110000513),
> > > > real(0, 0)]
> ../source3/smbd/smb2_setinfo.c:379(smbd_smb2_setinfo_send)
> > > > smbd_smb2_setinfo_send: $Extend/$Quota:$Q:$INDEX_ALLOCATION - fnum
> > > > 2762575723
> > > > [2016/03/25 10:38:21.333824, 10, pid=17987, effective(0, 110000513),
> > > > real(0, 0)]
> > > ../source3/smbd/smb2_server.c:2789(smbd_sm...
2015 Jul 10
0
Constant error messages about failure to remove oplock
.../source3/smbd/smb2_server.c:2511(smbd_smb2_request_done_ex)
smbd_smb2_request_done_ex: idx[1] status[NT_STATUS_OK] body[2] dyn[no:0]
at ../source3/smbd/smb2_setinfo.c:150
[2015/06/25 03:05:30.434676, 10, pid=1581, effective(2030299, 2000514),
real(2030299, 0)] ../source3/smbd/smb2_setinfo.c:185(smbd_smb2_setinfo_send)
smbd_smb2_setinfo_send: ~test.pst.tmp - fnum 3983022690
[2015/06/25 03:05:30.434731, 3, pid=1581, effective(2030299, 2000514),
real(2030299, 0)] ../source3/smbd/trans2.c:7907(smbd_do_setfilepathinfo)
smbd_do_setfilepathinfo: ~test.pst.tmp (fnum 3983022690) info_level=1019
totdata=8
[2015/06/2...
2015 Jul 09
2
Constant error messages about failure to remove oplock
On Thu, Jul 09, 2015 at 01:09:05PM +0530, Shyam Kaushik wrote:
> Hi Volker,
>
> Yes this problem happens when we have "kernel oplocks = no". This happened
> constantly in one of production systems & so we disabled level2-oplock
> /set kernel-oplocks=yes (to avoid this issue). So unfortunately don’t have
> an environment where it reproduces now & cannot capture