[Samba] Index Corruption xBase database
julius_ahenobarbus at yahoo.co.uk
Thu Nov 22 17:34:59 UTC 2018
from smbstatus man page:
causes smbstatus to include byte range locks.
the fact is that 4 different connections are opening the same byte
range in 'MOVCTA.cdx'
That's about all that I can get from your command result dump.
On 2018-11-22 9:21 a.m., Jose Concha wrote:
> Using oplocks = no makes the communication extremely slow. For testing
> we have set level2 oplocks = no, but it haven't made much difference.
> Any clue about the smbstatus -B output?
> El jue., 22 de nov. de 2018 14:00, Ray Klassen via samba
> <samba at lists.samba.org <mailto:samba at lists.samba.org>> escribió:
> Are the shares set to oplocks = no ? That sometimes has a role in
> database corruption.
> On 2018-11-22 6:31 a.m., Jose Concha via samba wrote:
> > Hello,
> > I've been working with a xBase database (similar to dBase) in a
> > application. There are like 40 users working on the database on
> the same
> > time reading and like 10 writing information.
> > Sometimes the CDX files (Index Files) get corrupted and is it's
> > to pack the tables (rebuild the indexes).
> > I have notice using the smbstatus -B command the following
> > Pid dev:inode R/W start
> size name
> > 4429 80a:b60b34:0 W 1073746530 1
> > 3627 80a:b60b1d:0 PW 2147483646 1 MOVCTA.cdx
> > 3445 80a:b60b1d:0 PW 2147483646 1 MOVCTA.cdx
> > 6078 80a:b60b1d:0 PW 2147483646 1 MOVCTA.cdx
> > 4429 80a:b60b1d:0 PW 2147483646 1 MOVCTA.cdx
> > Everytime PW appears and the start number 2147483646 indexes get
> > I've been searching documentation about smbstatus -B without
> success, so I
> > do not know what start means or what can be causing the problem.
> > I am running in a Giga ethernet LAN with Cat 6. I am using
> version 4.5.12
> > on Debian 9
> > Thanks for your help
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
More information about the samba