Displaying 3 results from an estimated 3 matches for "4aa5".
Did you mean:
4aa1
2013 Jul 09
1
tips/nest practices for gluster rdma?
...me was created:
gluster volume create holyscratch transport rdma,tcp
holyscratch01-ib:/holyscratch01/brick
for i in `seq -w 2 10` ; do gluster volume add-brick holyscratch
holyscratch${i}-ib:/holyscratch${i}/brick; done
yielding:
Volume Name: holyscratch
Type: Distribute
Volume ID: 788e74dc-6ae2-4aa5-8252-2f30262f0141
Status: Started
Number of Bricks: 10
Transport-type: tcp,rdma
Bricks:
Brick1: holyscratch01-ib:/holyscratch01/brick
Brick2: holyscratch02-ib:/holyscratch02/brick
Brick3: holyscratch03-ib:/holyscratch03/brick
Brick4: holyscratch04-ib:/holyscratch04/brick
Brick5: holyscratch05-ib:/h...
2019 May 16
0
Error smb_panic(): calling panic action [/bin/sleep 999999999]
...for your problem.
>
>
> SAMBA-TOOL drs showrepl on affected Host /slave)
>
> [root at s4slave ~]# samba-tool drs showrepl
> Default-First-Site-Name\S4SLAVE
> DSA Options: 0x00000001
> DSA object GUID: cce36cb1-5fcd-46f2-a49c-f0d51b72e08b
> DSA invocationId: 47c91612-b1d1-4aa5-ae70-9eb32fb5b6a9
>
Everything looks okay there.
Rowland
2019 May 16
3
Error smb_panic(): calling panic action [/bin/sleep 999999999]
No I can not upgrade now it is a working system with x users.
The master dc with the same config is working without any issues.
So when I upgrade I must do the uprgade on both replicating samba server and the samba fileservers?
No hint form e to repair:
May 16 14:00:12 s4slave smbd[7141]: [2019/05/16 14:00:12.438121, 0] ../source3/lib/util.c:801(smb_panic_s3)
May 16 14:00:12 s4slave smbd[7141]: