On Mon, Aug 8, 2016 at 5:24 PM, Joe Julian wrote:
>
>
> On 08/08/2016 02:56 PM, David Gossage wrote:
>
> On Mon, Aug 8, 2016 at 4:37 PM, David Gossage > wrote:
>
>> On Mon, Aug 8, 2016 at 4:23 PM, Joe Julian wrote:
>>
On Tue, Aug 9, 2016 at 2:18 AM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On 9 August 2016 at 12:23, David Gossage
> wrote:
> > Since my dev is now on 3.8 and has granular enabled I'm feeling too lazy
> to
> > roll back so will just wait till 3.8.2 is
On 9 August 2016 at 12:23, David Gossage wrote:
> Since my dev is now on 3.8 and has granular enabled I'm feeling too lazy to
> roll back so will just wait till 3.8.2 is released in few days that fixes
> the bugs mentioned to me and then test this few times on my dev.
On Mon, Aug 8, 2016 at 9:15 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On 9 August 2016 at 07:23, Joe Julian wrote:
> > Just kill (-15) the brick process. That'll close the TCP connections and
> the
> > clients will just go right on functioning off the
On 9 August 2016 at 07:23, Joe Julian wrote:
> Just kill (-15) the brick process. That'll close the TCP connections and the
> clients will just go right on functioning off the remaining replica. When
> you format and recreate your filesystem, it'll be missing the volume-id
On Mon, Aug 8, 2016 at 5:24 PM, Joe Julian wrote:
>
>
> On 08/08/2016 02:56 PM, David Gossage wrote:
>
> On Mon, Aug 8, 2016 at 4:37 PM, David Gossage > wrote:
>
>> On Mon, Aug 8, 2016 at 4:23 PM, Joe Julian wrote:
>>
On 08/08/2016 02:56 PM, David Gossage wrote:
On Mon, Aug 8, 2016 at 4:37 PM, David Gossage
> wrote:
On Mon, Aug 8, 2016 at 4:23 PM, Joe Julian > wrote:
On
On 08/08/2016 02:37 PM, David Gossage wrote:
On Mon, Aug 8, 2016 at 4:23 PM, Joe Julian > wrote:
On 08/08/2016 01:39 PM, David Gossage wrote:
So now that I have my cluster on 3.7.14 and sharded and working I
am of course
On Mon, Aug 8, 2016 at 4:37 PM, David Gossage
wrote:
> On Mon, Aug 8, 2016 at 4:23 PM, Joe Julian wrote:
>
>>
>>
>> On 08/08/2016 01:39 PM, David Gossage wrote:
>>
>> So now that I have my cluster on 3.7.14 and sharded and working I am of
>>
On Mon, Aug 8, 2016 at 4:23 PM, Joe Julian wrote:
>
>
> On 08/08/2016 01:39 PM, David Gossage wrote:
>
> So now that I have my cluster on 3.7.14 and sharded and working I am of
> course looking for what to break next.
>
> Currently each of 3 nodes is on a 6 disk (WD Red
On Mon, Aug 8, 2016 at 4:06 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> On 9/08/2016 6:39 AM, David Gossage wrote:
>
>> Currently each of 3 nodes is on a 6 disk (WD Red 1TB) raidz6 (zil on
>> mirrored ssd), which I am thinking is more protection than I may need with
>> a 3 way
On 08/08/2016 01:39 PM, David Gossage wrote:
So now that I have my cluster on 3.7.14 and sharded and working I am
of course looking for what to break next.
Currently each of 3 nodes is on a 6 disk (WD Red 1TB) raidz6 (zil on
mirrored ssd), which I am thinking is more protection than I may
On 9/08/2016 6:39 AM, David Gossage wrote:
Currently each of 3 nodes is on a 6 disk (WD Red 1TB) raidz6 (zil on
mirrored ssd), which I am thinking is more protection than I may need
with a 3 way replica. I was going to one by one change them to
basically raid10 letting it heal in between.
So now that I have my cluster on 3.7.14 and sharded and working I am of
course looking for what to break next.
Currently each of 3 nodes is on a 6 disk (WD Red 1TB) raidz6 (zil on
mirrored ssd), which I am thinking is more protection than I may need with
a 3 way replica. I was going to one by
14 matches
Mail list logo