On Thu, Feb 28, 2019 at 9:48 PM Poornima Gurusiddaiah
wrote:
>
>
> On Thu, Feb 28, 2019, 8:44 PM Tami Greene wrote:
>
>> I'm missing some information about how the cluster volume creates the
>> metadata allowing it to see and find the data on the bricks. I've been
>> told not to write anything
Orig file structure to share with gluster is /foo
Volname is testvol
Data exists in foo . You have 2 copies, one on machine a, another on b.
When you create the testvol in gluster, it creates a folder /foo/.glusterfs and
writes all gluster metadata there. There's config data written in gluster o
On Thu, Feb 28, 2019, 8:44 PM Tami Greene wrote:
> I'm missing some information about how the cluster volume creates the
> metadata allowing it to see and find the data on the bricks. I've been
> told not to write anything to the bricks directly as the glusterfs cannot
> create the metadata and
I'm missing some information about how the cluster volume creates the
metadata allowing it to see and find the data on the bricks. I've been
told not to write anything to the bricks directly as the glusterfs cannot
create the metadata and therefore the data doesn't exist in the cluster
world.
So,
It sounds like new bricks were added and they mounted over the top of
existing bricks.
gluster volume status detail
This will give the data you need to find where the real files are. You
can look in those to see the data should be intact.
Stopping the gluster volume is a good first step. Then as
That makes sense. System is made of four data arrays with a hardware RAID
6 and then the distributed volume on top. I honestly don't know how that
works, but the previous administrator said we had redundancy. I'm hoping
there is a way to bypass the safeguard of migrating data when removing a
bri
Keep in mind that gluster is a metadata process. It doesn't really
touch the actual volume files. The exception is the .glusterfs and
.trashcan folders in the very top directory of the gluster volume.
When you create a gluster volume from brick, it doesn't format the
filesystem. It uses what's alre
I sent this and realized I hadn't registered. My apologies for the
duplication
Subject: Added bricks with wrong name and now need to remove them without
destroying volume.
To:
Yes, I broke it. Now I need help fixing it.
I have an existing Gluster Volume, spread over 16 bricks and 4 servers
