I don't understand why there's such a complicated process to recover when I
can just look at both files, decide which one I need and delete another one.
On Thu, Sep 11, 2014 at 7:56 AM, Pranith Kumar Karampuri
pkara...@redhat.com wrote:
On 09/11/2014 09:29 AM, Ilya Ivanov wrote:
Right...
On 09/11/2014 11:37 AM, Ilya Ivanov wrote:
I don't understand why there's such a complicated process to recover
when I can just look at both files, decide which one I need and delete
another one.
If the file needs to be deleted the whole file needs to be copied which
is fine for small files
To fix these Coverity issues , please check the below link for guidelines:
http://www.gluster.org/community/documentation/index.php/Fixing_Issues_Reported_By_Tools_For_Static_Code_Analysis#Coverity
Original Message
Subject:New Defects reported by Coverity Scan for
Hello list,
What would that kind of message mean ?
[2014-09-10 21:49:15.360499] W
[client-rpc-fops.c:1480:client3_3_fstat_cbk] 0-mailer-client-1: remote
operation failed: Operation not permitted
[2014-09-10 21:49:15.360780] W
[client-rpc-fops.c:1480:client3_3_fstat_cbk] 0-mailer-client-0: remote
Makes some sense. Yes, I meant make a backup and delete, rather than just
delete.
If I may suggest, putting that debug link somewhere more visible would be
be good, too. I wouldn't find without your help.
Thank you for the assistance.
On Thu, Sep 11, 2014 at 9:14 AM, Pranith Kumar Karampuri
On 09/11/2014 01:13 PM, Ilya Ivanov wrote:
Makes some sense. Yes, I meant make a backup and delete, rather than
just delete.
If I may suggest, putting that debug link somewhere more visible would
be be good, too. I wouldn't find without your help.
Justin, where shall we put the doc?
On 11/09/2014, at 9:44 AM, Pranith Kumar Karampuri wrote:
On 09/11/2014 01:13 PM, Ilya Ivanov wrote:
Makes some sense. Yes, I meant make a backup and delete, rather than just
delete.
If I may suggest, putting that debug link somewhere more visible would be be
good, too. I wouldn't find
Bala,
I think using Salt as the orchestration framework is a good idea.
We would still need to have a consistent distributed store. I hope
Salt has the provision to use one of our choice. It could be consul
or something that satisfies the criteria for choosing alternate technology.
I would wait
- Original Message -
From: Krishnan Parthasarathi kpart...@redhat.com
To: Balamurugan Arumugam barum...@redhat.com
Cc: gluster-users@gluster.org, Gluster Devel gluster-de...@gluster.org
Sent: Thursday, September 11, 2014 2:25:45 PM
Subject: Re: [Gluster-users] [Gluster-devel]
On 11/09/2014, at 10:16 AM, Balamurugan Arumugam wrote:
snip
For distributed store, I would think of MongoDB which provides
distributed/replicated/highly available/master read-write/slave read-only
database. Lets get what community think about SaltStack and/or MongoDB.
Is this relevant for
- Original Message -
From: Justin Clift jus...@gluster.org
To: Balamurugan Arumugam b...@gluster.com
Cc: Krishnan Parthasarathi kpart...@redhat.com,
gluster-users@gluster.org, Gluster Devel
gluster-de...@gluster.org
Sent: Thursday, September 11, 2014 2:48:41 PM
Subject: Re:
- Original Message -
From: Justin Clift jus...@gluster.org
To: Balamurugan Arumugam b...@gluster.com
Cc: Krishnan Parthasarathi kpart...@redhat.com,
gluster-users@gluster.org, Gluster Devel
gluster-de...@gluster.org
Sent: Thursday, September 11, 2014 2:48:41 PM
Subject: Re:
Yes. I came across Salt currently for unified management for storage to
manage gluster and ceph which is still in planning phase. I could think of
a complete requirement of infra requirement to solve from glusterd to
unified management. Calamari ceph management already uses Salt. It would
For distributed store, I would think of MongoDB which provides
distributed/replicated/highly available/master read-write/slave read-only
database. Lets get what community think about SaltStack and/or MongoDB.
I definitely do not think MongoDB is the right tool for this job. I'm
not one of
I really hope whatever the outcome and final choice is ... as an end user I
hope that Gluster stays as simple to deploy as it is today.
Yes, the peers and volume files would be nice to be in one cloud storage
(chicken and egg problem - gluster is a cloud storage but it unable to
bootstrap its
I'm so glad to read this. I was thinking the same thing.
On Sep 11, 2014, at 7:22 AM, Jeff Darcy jda...@redhat.com wrote:
For distributed store, I would think of MongoDB which provides
distributed/replicated/highly available/master read-write/slave read-only
database. Lets get what community
On Thu, Sep 11, 2014 at 4:55 AM, Krishnan Parthasarathi
kpart...@redhat.com wrote:
I think using Salt as the orchestration framework is a good idea.
We would still need to have a consistent distributed store. I hope
Salt has the provision to use one of our choice. It could be consul
or
On Thu, Sep 11, 2014 at 12:01 PM, Prasad, Nirmal npra...@idirect.net wrote:
I really hope whatever the outcome and final choice is ... as an end user I
hope that Gluster stays as simple to deploy as it is today.
I think it's pretty simple already with puppet-gluster. It takes me
around 15
On 09/10/2014 08:32 AM, French Teddy wrote:
I have a very simple two nodes setup.
After I rebooted one the nodes, a directory deep inside the hierarchy on
the other node has become dead. By dead I mean any process trying to
access its content becomes stuck.
Absolutly nothing appears on the
Any more to this thread? I don't mean to nag, but this seems like a pretty
serious issue.
How can I help?
On Sep 7, 2014, at 9:51 AM, mike m...@luminatewireless.com wrote:
I don't think I have these enabled. How can I confirm that?
On Sep 7, 2014, at 12:57 AM, Anand Avati av...@gluster.org
On 09/11/2014 11:38 PM, mike wrote:
Any more to this thread? I don't mean to nag, but this seems like a
pretty serious issue.
Most probably the issue is in write-behind according to my tests. The
people who know that xlator are Avati/Raghavendra G/Niels
CCed all of them
Pranith
How can I
I apologize for not replying earlier.
Such functionality is not planned for libgfapi.
We plan to keep it restricted to only data path.
Projects in https://forge.gluster.org/ may be helpful to you.
On Tue, Sep 2, 2014 at 8:05 PM, Prasad, Nirmal npra...@idirect.net wrote:
Thanks for the
Hello Shyam. Thanks for the reply. Please see my reply below, starting with
[paul:]
Please add me in address list besides gluster-uses when replying so that I can
easier
reply since I subscribed gluster-users with the digest mode (No other choice if
I
remember correctly.)
Date: Wed, 10 Sep
- Original Message -
On Thu, Sep 11, 2014 at 4:55 AM, Krishnan Parthasarathi
kpart...@redhat.com wrote:
I think using Salt as the orchestration framework is a good idea.
We would still need to have a consistent distributed store. I hope
Salt has the provision to use one of our
24 matches
Mail list logo
