Hi all,
I personally believe that the replicated-distributed requirement to have at
least 2 node during expansion, is not really practical.
It is not practical for low budget user, where might be only able to buy
one machine at time, or add one hard disk at a time.
It is also not practical for h
Hi Chris,
I'm glad someone other than me asked this question :)
I think there are two things at play here.
1) when btrfs is adopted then we inherited block level checksuming from the
filesystem scrub. Since this operates below the file level this type of bit rot
detection will be workload a
Hi Paul,
Great! :)
Thanks for the update.
On Fri, Jan 10, 2014 at 8:26 AM, Paul Cuzner wrote:
> Hi,
>
> Thanks to all for the feedback.
>
> I've applied the following changes to the attached document;
>
>
>- Renamed the doc to "Getting Started with Gluster 3.4"
>- Corrected the multip
Just another +1 for this.
It really distills the important parts... And nothing else .!
> On Jan 9, 2014, at 7:26 PM, Paul Cuzner wrote:
>
> Hi,
>
> Thanks to all for the feedback.
>
> I've applied the following changes to the attached document;
>
> Renamed the doc to "Getting Started with G
On 10.01.2014 00:26, Paul Cuzner wrote:
Hi,
Thanks to all for the feedback.
I've applied the following changes to the attached document;
* Renamed the doc to "Getting Started with Gluster 3.4"
* Corrected the multiprotocol access table
* Added inode32 information for glusterfs mo
Is an optimization possible for Btrfs that avoids GlusterFS level checksums
entirely? Even with data raid0, by default it writes metadata with raid1, and
can determine file corruption. Such corruptions are reported by pathtofile by
Btrfs. If that can be communicated to glusterfs, glusterfs could
Thanks Niels, I'll take a look.
- Original Message -
> From: "Niels de Vos"
> To: "Paul Cuzner"
> Cc: "Gluster Devel"
> Sent: Thursday, 9 January, 2014 9:34:04 PM
> Subject: Re: [Gluster-devel] Fedora Gluster 'role'
> On Thu, Jan 09, 2014 at 02:31:00AM -0500, Paul Cuzner wrote:
> > H
On 09.01.2014 04:15, Justin Clift wrote:
> Ahhh, this is probably due to the updated OpenSSL stuff in EL 6.5.
Yes...
> Maybe we need to do separate sets of RPMs for EL 6.0-6.4, and
> a different set for 6.5 onwards.
It would seem, this is how things were done with the previous release (3.4.1-2).
I
On 01/09/2014 09:47 AM, Paul Cuzner wrote:
Hi fellow gluster'ers!
I'm putting together a Pocket Reference guide for glusterfs (draft
attached). It's a tri-fold document, so it should be a handy size to
print on card, fold up and carry around.
I'm still validating some of the detail in there
On Wed, 8 Jan 2014 23:17:26 -0500 (EST)
Paul Cuzner wrote:
> I'm putting together a Pocket Reference guide for glusterfs (draft attached).
> It's a tri-fold document, so it should be a handy size to print on card, fold
> up and carry around.
>
> I'm still validating some of the detail in ther
On Thu, Jan 9, 2014 at 9:47 AM, Paul Cuzner wrote:
>
> Hi fellow gluster'ers!
>
> I'm putting together a Pocket Reference guide for glusterfs (draft
> attached). It's a tri-fold document, so it should be a handy size to print
> on card, fold up and carry around.
>
> I'm still validating some of t
On 8 January 2014 01:15, Paul Cuzner wrote:
> Hi Shishir,
>
> Great to see this being progressed!
>
> Would it make sense to compare the checksums for a file across replica's
> too? ie. in a replicated volume, one the local checksum compare is complete,
> compare the checksum against the file's re
On 7 January 2014 19:04, Venky Shankar wrote:
>
>> 1. Depend on change-log to recompute checksum. This eliminates
>> periodic crawl of brick/volume to update the checksum.
>
>
> Consumption would be very much similar to how Geo-replication makes use of
> journals, i.e. notification after a specifi
On 2 January 2014 19:30, Jeffrey Darcy wrote:
>> I will be starting to work on bit rot detection for glusterfs.
>
> That's magnificent, and not only because it's a valuable feature. It's great
> to see you still exhibiting such initiative. :)
Leaving gluster developement was never my intention
On Wed, 08 Jan 2014 19:31:23 -0500
"Mikhail T." wrote:
> On 08.01.2014 18:24, Joe Julian wrote:
> > Yum makes that so much easier. It will resolve the dependencies for you.
> I am using yum -- after placing all of those RPMs into my own special repo
> (one
> for all external RPMs we are using).
Hi,
I think the 32bit inode tuning is not in the reference, right?
I believe this information is important to be included in the reference.
Thanks.
On Thu, Jan 9, 2014 at 12:17 PM, Paul Cuzner wrote:
>
> Hi fellow gluster'ers!
>
> I'm putting together a Pocket Reference guide for glusterfs
On Thu, Jan 09, 2014 at 02:31:00AM -0500, Paul Cuzner wrote:
> Hi,
>
> I see during the installation of Fedora, different roles can be
> adopted - web server, virt, infrastructure etc
>
> Does anyone know what the process would be for a storage role within
> the fedora project that focused on
17 matches
Mail list logo
