On 11/12/2014 10:31 PM, Dennis Schafroth wrote:
Is it know whether the fix will work for other filesystems like btrfs
and HFS+
hi Dennis,
This problem happens because of the way gluster handles 64-bit
offsets introduced in ext4.
Pranith
cheers,
:-Dennis
On 12 Nov 2014, at 13:22 , Pran
+1, excellent idea, this will definitely give an additional comfort zone
for learning glusterfs faster.
On 11/12/2014 05:47 PM, Krishnan Parthasarathi wrote:
> All,
>
> We have come across behaviours and features of GlusterFS that are left
> unexplained for various reasons. Thanks to Justin Clift
Community meeting minutes:
http://meetbot.fedoraproject.org/gluster-meeting/2014-11-12/gluster-meeting.2014-11-12-12.03.html
Highlights:
3.6.2 is out
3.5.3 and 3.4.6 release imminent, released to maintainers for packaging
Upcoming discussions for future features, Bitrot detection up first
Is it know whether the fix will work for other filesystems like btrfs and HFS+
cheers,
:-Dennis
> On 12 Nov 2014, at 13:22 , Pranith Kumar Karampuri
> wrote:
>
>>> n Wed, 12 Nov 2014 09:41:17 AM you wrote:
I have seen weirdness with ext4 and replicated volumes, see thread
"[Gluster
Greetings,
We are excited to announce the launch of planning for GlusterFS 3.7 and
GlusterFS 4.0 releases!
GlusterFS 3.7 will continue the work already ongoing in the 3.x
series,extending the current architecture and foundations to their
limits. We expect 3.7 to be released in April 2015. De
On Wed, 12 Nov 2014 07:17:25 -0500 (EST)
Krishnan Parthasarathi wrote:
> All,
>
> We have come across behaviours and features of GlusterFS that are left
> unexplained for various reasons. Thanks to Justin Clift for
> encouraging me to come up with a document that tries to fill this gap
> increme
On 11/12/2014 05:41 PM, Pranith Kumar Karampuri wrote:
On 11/12/2014 03:35 PM, Lindsay Mathieson wrote:
On Wed, 12 Nov 2014 09:41:17 AM you wrote:
I have seen weirdness with ext4 and replicated volumes, see thread
"[Gluster-devel] Duplicate entries and other weirdness in a 3*4 volume"
started
All,
We have come across behaviours and features of GlusterFS that are left
unexplained for various reasons. Thanks to Justin Clift for encouraging me to
come up with a document that tries to fill this gap incrementally. We have
decided
to call it "did-you-know.md" and for a reason. We'd love to
On 11/12/2014 03:35 PM, Lindsay Mathieson wrote:
On Wed, 12 Nov 2014 09:41:17 AM you wrote:
I have seen weirdness with ext4 and replicated volumes, see thread
"[Gluster-devel] Duplicate entries and other weirdness in a 3*4 volume"
started at 17 July.
Interesting, thanks.
It is a bug in gluste
The glusterfs volume configuration lives in /var/lib/glusterd . You'll
need to backup/restore the complete directory to get your
functionality.
/etc/glusterfs contains a simple volfile needed to start glusterd,
which would be installed by the glusterfs package in most cases.
You'll need this as we
[Adding gluster-users]
On 10/29/2014 12:11 PM, Raghavendra Bhat wrote:
On Monday 27 October 2014 06:34 PM, Vijay Bellur wrote:
Hi All,
As we move closer to the release of 3.6.0, we are looking to add a
release maintainer for the 3.6.0 development branch (release-3.6).
Primary requirements for
On Wed, Nov 12, 2014 at 10:03:36AM +0100, Florian Knorn wrote:
> Dear Niels,
>
> Many thanks for your quick reply.
>
> Indeed, after running “service glusterfs-server stop” (which is
> essentially one of the first executed on shutdown), if I use “lsof” on
> the brick directory I get many hits for
Hi,
As I previously described, my root file system is located in RAM so I'll lose
the
gluster volume definition(s) in case of a reboot. However, I would like to
backup the
required files to a mounted disk so that they can be restored to /etc after the
reboot. Which files would I have to backup/r
Hi Pedro,
On 11/12/2014 10:56 AM, Pedro Serotto wrote:
Hi Xavi,
what about if I need to add more bricks than 3 ?
Currently the number of bricks in a disperse set is fixed, as it is in a
replica set.
Basically you decide the level of reliability of the volume when you
create it (proportion
On Wed, 12 Nov 2014 09:41:17 AM you wrote:
> I have seen weirdness with ext4 and replicated volumes, see thread
> "[Gluster-devel] Duplicate entries and other weirdness in a 3*4 volume"
> started at 17 July.
Interesting, thanks.
--
Lindsay
signature.asc
Description: This is a digitally signed
Hi Xavi,
what about if I need to add more bricks than 3 ?
BR
Pedro
El Miércoles 12 de noviembre de 2014 10:09, Xavier Hernandez
escribió:
Hi Pedro,
you can create a dispersed volume with 3 bricks and 1 of redundancy (or
parity, like in RAID5) using the following command:
gluster volume
Hi Pedro,
you can create a dispersed volume with 3 bricks and 1 of redundancy (or
parity, like in RAID5) using the following command:
gluster volume create disperse 3 redundancy 1
A RAID6-like configuration would use 2 as a redundancy value, and at
least 5 bricks are needed.
The numb
On Wed, Nov 12, 2014 at 09:07:46AM +0100, Florian Knorn wrote:
> Hi,
>
> I have an issue where I can’t reboot or shutdown my server with
> gluster running. The setup:
>
> Debian 7.7, Gluster - 3.5.2, 1 volume with 1 brick mounted via iSCSI,
> using multipath-tools.
>
> On shutdown / reboot, the
On 2014-11-12 05:54, Ravishankar N wrote:
> On 11/12/2014 03:21 AM, Lindsay Mathieson wrote:
>> Just wondering about the usecases. In all my testing ext4 has been
>> consistently faster for sustained and random read/writes on large files (VM
>> images).
>>
>> Tested with/without external ssd journ
Hi,
I have an issue where I can’t reboot or shutdown my server with
gluster running. The setup:
Debian 7.7, Gluster - 3.5.2, 1 volume with 1 brick mounted via iSCSI,
using multipath-tools.
On shutdown / reboot, the system hangs at “Unmounting local
filesystems”, see this screenshot:
https://www
20 matches
Mail list logo
