Displaying 4 results from an estimated 4 matches for "zalma".
Did you mean:
zalm
2016 Nov 03
6
CTDB and locking issues in 4.4.6 (Classic domain)
...oes your system have consistent inodes and device ids? Does
>
> stat /some/shared/file
>
> give exactly the same information on all nodes, in particular the
> Device/Inode fields?
>
> Volker
Thanks Volker,
No, it seems it's OK on two servers but not on the third:
[root at zalma ~]# stat testfile
...
Size: 1286700 Blocks: 2514 IO Block: 65536 regular file
Device: 29h/41d Inode: 35820037 Links: 1
Access: (0774/-rwxrwxr--) Uid: ( 3535/ jh3) Gid: ( 513/Domain Users)
Access: 2016-11-03 19:51:46.000000000 +0000
Modify: 2016-11-01 13:06:04.000000000...
2016 Nov 03
0
CTDB and locking issues in 4.4.6 (Classic domain)
...No, it seems it's OK on two servers but not on the third:
Ah, well that explains a lot :-).
Samba uses the device/ino pair to determine if two files
are the same. If they're different - to smbd then they're
different files.
That's why the locking doesn't work.
> [root at zalma ~]# stat testfile
> ...
> Size: 1286700 Blocks: 2514 IO Block: 65536 regular file
> Device: 29h/41d Inode: 35820037 Links: 1
> Access: (0774/-rwxrwxr--) Uid: ( 3535/ jh3) Gid: ( 513/Domain Users)
> Access: 2016-11-03 19:51:46.000000000 +0000
> Modify:...
2016 Nov 04
2
CTDB and locking issues in 4.4.6 (Classic domain)
On 04/11/16 07:12, Volker Lendecke wrote:
> On Thu, Nov 03, 2016 at 09:21:46PM +0000, Alex Crow via samba wrote:
>> [root at zalma ~]# stat testfile
>> ...
>> Size: 1286700 Blocks: 2514 IO Block: 65536 regular file
>> Device: 29h/41d Inode: 35820037 Links: 1
>> Access: (0774/-rwxrwxr--) Uid: ( 3535/ jh3) Gid: ( 513/Domain Users)
>> Access: 2016-11-03 19:51:46.000000000...
2016 Nov 03
2
CTDB and locking issues in 4.4.6 (Classic domain)
On 03/11/16 14:28, Ralph Böhme wrote:
>
>> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man
>> smb.conf" this should be set, but I don't remember seeing it on the wiki
>> pages.
> if it's not set, the default is used which works in many cases, but
> not in mine. If the default wasn't working in your setup,