Displaying 9 results from an estimated 9 matches for "0000a5ef".
2017 Oct 19
2
gfid entries in volume heal info that do not heal
I've been following this particular thread as I have a similar issue
(RAID6 array failed out with 3 dead drives at once while a 12 TB load
was being copied into one mounted space - what a mess)
I have >700K GFID entries that have no path data:Example:getfattr -d -e
hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421# file:
.glusterfs/00/00/0000a5ef-5af7-401b-84b5-
ff2a51c10421security.selinux=0x73797374656d5f753a6f626a6563745f723a756e
6c6162656c65645f743a733000trusted.bit-
rot.version=0x020000000000000059b1b316000270e7trusted.gfid=0x0000a5ef5a
f7401b84b5ff2a51c10421
[root at bmidata...
2017 Oct 23
2
gfid entries in volume heal info that do not heal
...#39;ve been following this particular thread as I have a similar issue (RAID6 array failed out with 3 dead drives at once while a 12 TB load was being copied into one mounted space - what a mess)
I have >700K GFID entries that have no path data:
Example:
getfattr -d -e hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421
# file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421
security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000
trusted.bit-rot.version=0x020000000000000059b1b316000270e7
trusted.gfid=0x0000a5ef5af7401b84b5ff2a51c10421
[root at bmidat...
2017 Oct 23
0
gfid entries in volume heal info that do not heal
...rticular thread as I have a similar issue
> (RAID6 array failed out with 3 dead drives at once while a 12 TB load was
> being copied into one mounted space - what a mess)
>
> I have >700K GFID entries that have no path data:
> Example:
> getfattr -d -e hex -m . .glusterfs/00/00/0000a5ef-
> 5af7-401b-84b5-ff2a51c10421
> # file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421
> security.selinux=0x73797374656d5f753a6f626a6563
> 745f723a756e6c6162656c65645f743a733000
> trusted.bit-rot.version=0x020000000000000059b1b316000270e7
> trusted.gfid=0x0000a5ef5af7401b8...
2017 Oct 23
0
gfid entries in volume heal info that do not heal
...gt; TB load was being copied into one mounted space - what a mess)
> >
> >
> >
> >
> >
> > I have >700K GFID entries that have no path data:
> >
> >
> > Example:
> >
> >
> > getfattr -d -e hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-84b5-
> > ff2a51c10421
> >
> >
> > # file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421
> >
> >
> > security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c616265
> > 6c65645f743a733000
> >
> >
> > trust...
2017 Oct 24
3
gfid entries in volume heal info that do not heal
...have a similar issue
> (RAID6 array failed out with 3 dead drives at once while a 12 TB load was
> being copied into one mounted space - what a mess)
>
>
>
> I have >700K GFID entries that have no path data:
>
> Example:
>
> getfattr -d -e hex -m . .glusterfs/00/00/0000a5ef-
> 5af7-401b-84b5-ff2a51c10421
>
> # file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421
>
> security.selinux=0x73797374656d5f753a6f626a6563
> 745f723a756e6c6162656c65645f743a733000
>
> trusted.bit-rot.version=0x020000000000000059b1b316000270e7
>
> trusted.gfid...
2017 Oct 24
0
gfid entries in volume heal info that do not heal
...gt; >
> > > >
> > > >
> > > > I have >700K GFID entries that have no path data:
> > > >
> > > >
> > > > Example:
> > > >
> > > >
> > > > getfattr -d -e hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-
> > > > 84b5-ff2a51c10421
> > > >
> > > >
> > > > # file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421
> > > >
> > > >
> > > > security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c61...
2017 Nov 06
0
gfid entries in volume heal info that do not heal
...gt; >
> > > >
> > > >
> > > > I have >700K GFID entries that have no path data:
> > > >
> > > >
> > > > Example:
> > > >
> > > >
> > > > getfattr -d -e hex -m . .glusterfs/00/00/0000a5ef-5af7-401b-
> > > > 84b5-ff2a51c10421
> > > >
> > > >
> > > > # file: .glusterfs/00/00/0000a5ef-5af7-401b-84b5-ff2a51c10421
> > > >
> > > >
> > > > security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c61...
2017 Oct 17
0
gfid entries in volume heal info that do not heal
Attached is the heal log for the volume as well as the shd log.
>> Run these commands on all the bricks of the replica pair to get the attrs set on the backend.
[root at tpc-cent-glus1-081017 ~]# getfattr -d -e hex -m . /exp/b1/gv0/.glusterfs/10/86/108694db-c039-4b7c-bd3d-ad6a15d811a2
getfattr: Removing leading '/' from absolute path names
# file:
2017 Oct 17
3
gfid entries in volume heal info that do not heal
Hi Matt,
Run these commands on all the bricks of the replica pair to get the attrs
set on the backend.
On the bricks of first replica set:
getfattr -d -e hex -m . <brick path>/.glusterfs/10/86/
108694db-c039-4b7c-bd3d-ad6a15d811a2
On the fourth replica set:
getfattr -d -e hex -m . <brick path>/.glusterfs/
e0/c5/e0c56bf7-8bfe-46ca-bde1-e46b92d33df3
Also run the "gluster volume