Displaying 5 results from an estimated 5 matches for "9a77".
Did you mean:
977
2018 Jan 26
0
samba-tool dbcheck failing
...ebad4,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=mydomain,DC=edu,DC=na'
Remove DN link? [YES]
Failed to remove deleted DN attribute lastKnownParent : (65,
"objectclass_attrs: at least one mandatory attribute ('fromServer') on
entry
'CN=5e962046-c645-4154-9a77-c7e31325c32e,CN=LostAndFoundConfig,CN=Configuration,DC=mydomain,DC=edu,DC=na'
wasn't specified!")
CN=5e962046-c645-4154-9a77-c7e31325c32e,CN=LostAndFoundConfig,CN=Configuration,DC=mydomain,DC=edu,DC=na:
0x0009030e
CN=5e962046-c645-4154-9a77-c7e31325c32e,CN=LostAndFoundConfig,CN=Configu...
2018 Feb 27
2
Quorum in distributed-replicate volume
...change,
> and since it is a live system you may end up in data unavailability or data
> loss.
> Can you give the output of "gluster volume info <volname>"
> and which brick is of what size.
Volume Name: palantir
Type: Distributed-Replicate
Volume ID: 48379a50-3210-41b4-9a77-ae143c8bcac0
Status: Started
Snapshot Count: 0
Number of Bricks: 3 x 2 = 6
Transport-type: tcp
Bricks:
Brick1: saruman:/var/local/brick0/data
Brick2: gandalf:/var/local/brick0/data
Brick3: azathoth:/var/local/brick0/data
Brick4: yog-sothoth:/var/local/brick0/data
Brick5: cthulhu:/var/local/brick0/d...
2018 Feb 27
0
Quorum in distributed-replicate volume
...stem you may end up in data unavailability or
> data
> > loss.
> > Can you give the output of "gluster volume info <volname>"
> > and which brick is of what size.
>
> Volume Name: palantir
> Type: Distributed-Replicate
> Volume ID: 48379a50-3210-41b4-9a77-ae143c8bcac0
> Status: Started
> Snapshot Count: 0
> Number of Bricks: 3 x 2 = 6
> Transport-type: tcp
> Bricks:
> Brick1: saruman:/var/local/brick0/data
> Brick2: gandalf:/var/local/brick0/data
> Brick3: azathoth:/var/local/brick0/data
> Brick4: yog-sothoth:/var/local/br...
2018 Feb 27
0
Quorum in distributed-replicate volume
On Mon, Feb 26, 2018 at 6:14 PM, Dave Sherohman <dave at sherohman.org> wrote:
> On Mon, Feb 26, 2018 at 05:45:27PM +0530, Karthik Subrahmanya wrote:
> > > "In a replica 2 volume... If we set the client-quorum option to
> > > auto, then the first brick must always be up, irrespective of the
> > > status of the second brick. If only the second brick is up,
2018 Feb 26
2
Quorum in distributed-replicate volume
On Mon, Feb 26, 2018 at 05:45:27PM +0530, Karthik Subrahmanya wrote:
> > "In a replica 2 volume... If we set the client-quorum option to
> > auto, then the first brick must always be up, irrespective of the
> > status of the second brick. If only the second brick is up, the
> > subvolume becomes read-only."
> >
> By default client-quorum is