On Thu, Sep 22, 2016 at 8:33 PM, Pasi Kärkkäinen wrote:
> On Thu, Sep 22, 2016 at 07:20:26PM +0530, Pranith Kumar Karampuri wrote:
> >On Thu, Sep 22, 2016 at 12:51 PM, Ravishankar N
> ><[1]ravishan...@redhat.com> wrote:
> >
> > On 09/22/2016 12:38 PM, Pasi KÀrkkÀinen
On Thu, Sep 22, 2016 at 07:20:26PM +0530, Pranith Kumar Karampuri wrote:
>On Thu, Sep 22, 2016 at 12:51 PM, Ravishankar N
><[1]ravishan...@redhat.com> wrote:
>
> On 09/22/2016 12:38 PM, Pasi KÀrkkÀinen wrote:
>
>On Thu, Sep 22, 2016 at 09:58:25AM +0530, Ravishankar N
On Thu, Sep 22, 2016 at 12:51 PM, Ravishankar N
wrote:
> On 09/22/2016 12:38 PM, Pasi Kärkkäinen wrote:
>
>> On Thu, Sep 22, 2016 at 09:58:25AM +0530, Ravishankar N wrote:
>>
>>> On 09/21/2016 10:54 PM, Pasi Kärkkäinen wrote:
>>>
Let's see.
# getfattr -m .
On 09/22/2016 12:38 PM, Pasi Kärkkäinen wrote:
On Thu, Sep 22, 2016 at 09:58:25AM +0530, Ravishankar N wrote:
On 09/21/2016 10:54 PM, Pasi Kärkkäinen wrote:
Let's see.
# getfattr -m . -d -e hex /bricks/vol1/brick1/foo
getfattr: Removing leading '/' from absolute path names
# file:
On Thu, Sep 22, 2016 at 09:58:25AM +0530, Ravishankar N wrote:
> On 09/21/2016 10:54 PM, Pasi Kärkkäinen wrote:
> >Let's see.
> >
> ># getfattr -m . -d -e hex /bricks/vol1/brick1/foo
> >getfattr: Removing leading '/' from absolute path names
> ># file: bricks/vol1/brick1/foo
>
On 09/21/2016 10:54 PM, Pasi Kärkkäinen wrote:
Let's see.
# getfattr -m . -d -e hex /bricks/vol1/brick1/foo
getfattr: Removing leading '/' from absolute path names
# file: bricks/vol1/brick1/foo
security.selinux=0x756e636f6e66696e65645f753a6f626a6563745f723a756e6c6162656c65645f743a733000
So
Hi,
On Wed, Sep 21, 2016 at 10:12:44PM +0530, Ravishankar N wrote:
> On 09/21/2016 06:45 PM, Pasi Kärkkäinen wrote:
> >Hello,
> >
> >I have a pretty basic two-node gluster 3.7 setup, with a volume
> >replicated/mirrored to both servers.
> >
> >One of the servers was down for hardware
On 09/21/2016 06:45 PM, Pasi Kärkkäinen wrote:
Hello,
I have a pretty basic two-node gluster 3.7 setup, with a volume
replicated/mirrored to both servers.
One of the servers was down for hardware maintenance, and later when it got
back up, the healing process started, re-syncing files.
In
Hello,
I have a pretty basic two-node gluster 3.7 setup, with a volume
replicated/mirrored to both servers.
One of the servers was down for hardware maintenance, and later when it got
back up, the healing process started, re-syncing files.
In the beginning there was some 200 files that need to