FYI, we will move the ClusterLabs mailing lists to an upgraded server
this weekend (most likely Sunday). If anyone has problems sending or
receiving mail from the lists next week, feel free to e-mail me
directly (address in signature below).
--
Ken Gaillot
I sent this to the drbd list too, but it's possible that someone here may know.
This is a WEIRD one.
Why would one drbd volume be trimmable and the other one not?
Here you can see me issuing the trim command against two different filesystems.
It works on one but fails on the other.
ha11a:~ #
On Thu, 2018-01-25 at 17:45 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 24 Jan 2018 17:42:56 -0600
> Ken Gaillot wrote:
>
> > On Fri, 2018-01-19 at 00:37 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Thu, 18 Jan 2018 10:54:33 -0600
> > > Ken Gaillot
On 2018-01-25 01:28 PM, Ken Gaillot wrote:
> On Thu, 2018-01-25 at 13:06 -0500, Digimer wrote:
>> On 2018-01-25 11:11 AM, Ken Gaillot wrote:
>>> On Wed, 2018-01-24 at 20:58 +0100, Jehan-Guillaume de Rorthais
>>> wrote:
On Wed, 24 Jan 2018 13:28:03 -0600
Ken Gaillot
On Thu, 2018-01-25 at 13:06 -0500, Digimer wrote:
> On 2018-01-25 11:11 AM, Ken Gaillot wrote:
> > On Wed, 2018-01-24 at 20:58 +0100, Jehan-Guillaume de Rorthais
> > wrote:
> > > On Wed, 24 Jan 2018 13:28:03 -0600
> > > Ken Gaillot wrote:
> > >
> > > > I think there's enough
On 2018-01-25 11:11 AM, Ken Gaillot wrote:
> On Wed, 2018-01-24 at 20:58 +0100, Jehan-Guillaume de Rorthais wrote:
>> On Wed, 24 Jan 2018 13:28:03 -0600
>> Ken Gaillot wrote:
>>
>>> I think there's enough sentiment for "promoted"/"started" as the
>>> role
>>> names, since it
On 2018-01-25 11:59 AM, Jan Friesse wrote:
> I am pleased to announce the first testing (Alpha 1) release of Corosync
> 3.0 (codename Camelback) available immediately from our website at
> http://build.clusterlabs.org/corosync/releases/ as corosync-2.99.0.
>
> Corosync 3.0 contains many
On Wed, 24 Jan 2018 17:42:56 -0600
Ken Gaillot wrote:
> On Fri, 2018-01-19 at 00:37 +0100, Jehan-Guillaume de Rorthais wrote:
> > On Thu, 18 Jan 2018 10:54:33 -0600
> > Ken Gaillot wrote:
> >
> > > On Thu, 2018-01-18 at 16:15 +0100, Jehan-Guillaume
On Wed, 2018-01-24 at 20:58 +0100, Jehan-Guillaume de Rorthais wrote:
> On Wed, 24 Jan 2018 13:28:03 -0600
> Ken Gaillot wrote:
>
> > I think there's enough sentiment for "promoted"/"started" as the
> > role
> > names, since it most directly reflects how pacemaker uses them.
On Thu, 2018-01-25 at 11:31 +0100, Jehan-Guillaume de Rorthais wrote:
> On Thu, 25 Jan 2018 11:28:16 +0100
> Jehan-Guillaume de Rorthais wrote:
>
> > On Thu, 25 Jan 2018 10:03:34 +0100
> > Ivan Devát wrote:
> >
> > > > I think there's enough sentiment for
On Thu, 25 Jan 2018 11:28:16 +0100
Jehan-Guillaume de Rorthais wrote:
> On Thu, 25 Jan 2018 10:03:34 +0100
> Ivan Devát wrote:
>
> > > I think there's enough sentiment for "promoted"/"started" as the role
> > > names, since it most directly reflects how
On Thu, 25 Jan 2018 10:03:34 +0100
Ivan Devát wrote:
> > I think there's enough sentiment for "promoted"/"started" as the role
> > names, since it most directly reflects how pacemaker uses them.
> >
> Just a question.
> The property "role" of a resource operation can have
Hi,
I think there's enough sentiment for "promoted"/"started" as the role
names, since it most directly reflects how pacemaker uses them.
Just a question.
The property "role" of a resource operation can have values: "Stopped",
"Started" and in the case of multi-state resources, "Slave" and
13 matches
Mail list logo