search for: share_mode_lock

Hi list, I'm getting a lot of these on a CTDB cluster serving files to Windows clients: [2016/06/24 08:53:55.555485, 1] ../librpc/ndr/ndr.c:578(ndr_pull_error) ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:150) [2016/06/24 08:53:55.555506, 1] ../source3/locking/share_mode_lock.c:141(parse_share_modes) ndr_pull_share_mode_lock failed: Buffer Size Error [2016/06/24 08:53:55.562601, 1] ../librpc/ndr/ndr.c:578(ndr_pull_error) ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:150) [2016/06/24 08:53:55.562618, 1] ../source3/locking/share_mode_lock.c:141(pars...

Upgraded to Samba 4.11.2 and I?ve now too started seeing the message: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY A lot. I modified the source in source3/locking/share_mode_lock.c a bit in order to print out the values of the service path, smb_fname & old_write_time when it fails and it seems they are all NULL? [2019/11/14 14:24:23.358441, 0] ../....

Hello all, after the upgarde from Samba 4.10.7 to 4.11.2 we get lots of these in our logfiles: 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: [2019/11/28 20:40:44.886615, 1] ../../source3/locking/share_mode_lock.c:597(get_share_mode_lock) 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY There are no symptoms accept those errors in the logs. At least none were reported until now. Has anybody seen this before? System is centos7 with...

...m getting a lot of these on a CTDB cluster serving files to Windows > clients: > > [2016/06/24 08:53:55.555485, 1] ../librpc/ndr/ndr.c:578(ndr_pull_error) > ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:150) > [2016/06/24 08:53:55.555506, 1] > ../source3/locking/share_mode_lock.c:141(parse_share_modes) > ndr_pull_share_mode_lock failed: Buffer Size Error > [2016/06/24 08:53:55.562601, 1] ../librpc/ndr/ndr.c:578(ndr_pull_error) > ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:150) > [2016/06/24 08:53:55.562618, 1] > ../source3/locking/shar...

Hi all, hope, its ok, to join here.. Am Donnerstag, 14. November 2019, 14:34:29 CET schrieb Peter Eriksson via samba: > Upgraded to Samba 4.11.2 and I?ve now too started seeing the message: > > get_share_mode_lock: get_static_share_mode_data failed: NT_STATUS_NO_MEMORY > > A lot. I modified the source in source3/locking/share_mode_lock.c a bit in > order to print out the values of the service path, smb_fname & > old_write_time when it fails and it seems they are all NULL? > > > [...

Hello everyone, I hope you are well. Take care of yourself. I have the same problem as describe here: https://lists.samba.org/archive/samba/2014-December/187545.html I migrate a file share from a MAC-OS environment. For its new storage system, the company purchased an ASUSTOR NAS. This NAS works with an operating system based on version 4.14 of the GNU / LINUX x86_64 kernel. This NAS operates a

...ell a bit more about the server. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Peter Eriksson via samba > Verzonden: donderdag 14 november 2019 14:34 > Aan: samba at lists.samba.org > Onderwerp: [Samba] get_share_mode_lock: > get_static_share_mode_data failed: NT_STATUS_NO_MEMORY > > Upgraded to Samba 4.11.2 and I?ve now too started seeing the message: > > get_share_mode_lock: get_static_share_mode_data failed: > NT_STATUS_NO_MEMORY > > A lot. I modified the source in > source3/locki...

...-out messages in the logs. On the new cluster I see the following messages very often: [2013/07/22 15:09:02.594483, 1, pid=9437314] ../librpc/ndr/ndr.c:412(ndr_pull_error) ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:148) [2013/07/22 15:09:02.594636, 1, pid=9437314] locking/share_mode_lock.c:136(parse_share_modes) ndr_pull_share_mode_lock failed I would like to know how I can tell if there is some problem with the locking database in CTDB before I go any farther in testing. I upped the log level and I can see that this happens when getting each entry of a directory in dir.c:s...

On 29/11/2019 08:04, Christian Naumer via samba wrote: > Hello all, > after the upgarde from Samba 4.10.7 to 4.11.2 we get lots of these in > our logfiles: > > > 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: [2019/11/28 > 20:40:44.886615, 1] > ../../source3/locking/share_mode_lock.c:597(get_share_mode_lock) > 2019-11-28T20:40:44+01:00 lx-sv-09 smbd_audit: get_share_mode_lock: > get_static_share_mode_data failed: NT_STATUS_NO_MEMORY > > There are no symptoms accept those errors in the logs. There wouldn't be, it isn't an error ;-) If you look at '/s...

...hanks, i noticed this one also. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: vrijdag 29 november 2019 10:24 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] get_share_mode_lock:, > get_static_share_mode_data failed: NT_STATUS_NO_MEMORY with > Samba 4.11.2 > > On 29/11/2019 08:04, Christian Naumer via samba wrote: > > Hello all, > > after the upgarde from Samba 4.10.7 to 4.11.2 we get lots > of these in > > our logfiles: > > >...

...0 [2018/10/12 12:05:09.533032, 10, pid=3350, effective(1017, 1003), real(1017, 0)] ../lib/dbwrap/dbwrap_tdb.c:143(db_tdb_fetch_locked_internal) Allocated locked data 0x0x559d3f4db0d0 [2018/10/12 12:05:09.533042, 10, pid=3350, effective(1017, 1003), real(1017, 0), class=locking] ../source3/locking/share_mode_lock.c:285(share_mode_memcache_fetch) fetched entry for file . seq 0x1141782026507589052 key fd02:20000056:0 [2018/10/12 12:05:09.533052, 10, pid=3350, effective(1017, 1003), real(1017, 0), class=locking] ../source3/locking/locking.c:1226(find_delete_on_close_token) find_delete_on_close_token: name_...

...> > Louis > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> Peter Eriksson via samba >> Verzonden: donderdag 14 november 2019 14:34 >> Aan: samba at lists.samba.org >> Onderwerp: [Samba] get_share_mode_lock: >> get_static_share_mode_data failed: NT_STATUS_NO_MEMORY >> >> Upgraded to Samba 4.11.2 and I?ve now too started seeing the message: >> >> get_share_mode_lock: get_static_share_mode_data failed: >> NT_STATUS_NO_MEMORY >> >> A lot. I modified t...

...nd running Samba 4.0.3 successfully but with one pretty serious problem. When I try access the folder with 1000 files, the speed is *VERY* slow. After employ log level to 3, log.smbd is flooded with: ============================================= [2013/02/09 23:44:05.910717, 3] ../source3/locking/share_mode_lock.c:408(fetch_share_mode_unlocked) Could not fetch share entry [2013/02/09 23:44:05.911631, 3] ../source3/smbd/dir.c:1136(smbd_dirptr_get_entry) smbd_dirptr_get_entry mask=[*] found ./?? fname=?? (??) [2013/02/09 23:44:05.912607, 3] ../lib/util/charset/convert_string.c:316(convert_string_handle...

Hi The server suddenly changed the uid + gid. this happened to times, yesterday and the week after. The default group at example The samba is a AD member where we have many users (>20 000) and we use autorid in that way [global] security = ads workgroup = CUSTOMER realm = CUSTOMER.COM winbind use default domain = yes winbind enum users = yes winbind enum group = yes

...150(close_directory) Nov 13 13:01:24 ctdb-ho-2 smbd[30956]: close_directory: Could not get share mode lock for 6 Finanzen/B Ausgangsrechnungen bearbeiten/10 Ausgangsrechnung erstellen/2 Kaffee u Material Nov 13 13:01:26 ctdb-ho-2 smbd[30956]: [2020/11/13 13:01:26.458690, 0] ../../source3/locking/share_mode_lock.c:448(share_mode_data_store) Nov 13 13:01:26 ctdb-ho-2 smbd[30956]: PANIC: assert failed at ../../source3/locking/share_mode_lock.c(448): !share_entries_exist Nov 13 13:01:26 ctdb-ho-2 smbd[30956]: [2020/11/13 13:01:26.460269, 0] ../../source3/lib/util.c:830(smb_panic_s3) Nov 13 13:01:26 ctdb-ho...

On Sun, 2019-11-03 at 07:16 +0300, ?????? via samba wrote: > Hi all. help please: > # systemctl status smbd.service > ... > Nov 03 06:53:09 server1.local.my smbd[4585]: [2019/11/03 > 06:53:09.857837, 1] > ../../source3/locking/share_mode_lock.c:597(get_share_mode_lock) > Nov 03 06:53:09 server1.local.my smbd[4585]: get_share_mode_lock: > get_static_share_mode_data failed: NT_STATUS_NO_MEMORY > ... > > current version (but w older too) > # smbd -V > Version 4.11.2 > > client - macos, (time machine session)...

...tia fruit streams_xattr > fruit:aapl = yes > valid users = tmachine > read only = No > inherit acls = yes > > > Expected TimeMachine snapshot: 130GB > Samba share size: 950GB > > smbd.log: > [2018/03/21 11:15:13.589109, 0] > ../source3/locking/share_mode_lock.c:439(share_mode_data_destructor) > store returned NT_STATUS_UNSUCCESSFUL > [2018/03/21 11:15:13.589216, 0] ../source3/lib/util.c:815(smb_panic_s3) > PANIC (pid 933): could not store share mode entry: NT_STATUS_UNSUCCESSFUL > [2018/03/21 11:15:13.590549, 0] ../source3/lib/util.c:9...

...?use?of?`global_id`?and?only?added?a?local?flag?(DBWRAP_REPLACE).?I?wonder?if?there?has?been?any?consideration?to?include?the?persistent?flag?(DBWRAP_PERSISTENT)?as?well. 2.?When?I?change?the?flag?from?`DBWRAP_FLAG_NONE`?to?`DBWRAP_FLAG_PER_REC_PERSISTENT`?in?the?`locking_init_internal`?function?of?share_mode_lock.c,?I?am?unable?to?access?the?shared?folder.?The?error?message??is:?"\192.168.24.8\ph?is?inaccessible.?You?might?not?have?permission?to?use?this?network?resource.?Contact?the?administrator?of?this?server?to?find?out?if?you?have?access?permissions.?The?request?operation?could?not?be?completed?be...

...u have access permissions. The process cannot access the file because it is being used by another process." I can still access the share from Win XP so i'm guessing this is and SMB2 issue. In the server logs is see the following error : [2013/10/09 10:30:30.593372, 1] ../source3/locking/share_mode_lock.c:137(parse_share_modes) ndr_pull_share_mode_lock failed: Bad Array Size [2013/10/09 10:30:30.593402, 0] ../source3/smbd/open.c:2238(open_file_ntcreate) Could not get share mode lock [2013/10/09 10:30:30.594086, 3] ../source3/smbd/vfs.c:1140(check_reduced_name) check_reduced_name [.] [/gpfs...

...r issues until I try to use the sharing for Time Machine backup. In fact, after starting the Time Machine backup after a while, random time like 2-3 hours of backup, I got the following panic error and the backup stops and I need to reboot samba. [2018/12/09 11:43:57.461725, 0] ../source3/locking/share_mode_lock.c:439(share_mode_data_destructor) store returned NT_STATUS_UNSUCCESSFUL [2018/12/09 11:43:57.461915, 0] ../source3/lib/util.c:816(smb_panic_s3) PANIC (pid 32610): could not store share mode entry: NT_STATUS_UNSUCCESSFUL [2018/12/09 11:43:57.463585, 0] ../lib/util/fault.c:261(log_stack_trace) B...