diff options
| author | Raghavendra Bhat <raghavendra@redhat.com> | 2018-04-20 14:54:33 -0400 |
|---|---|---|
| committer | Amar Tumballi <amarts@redhat.com> | 2018-05-04 11:13:57 +0000 |
| commit | b42a048d3a76c7f377399f18d30f0a8a930f9d05 (patch) | |
| tree | b400225db569fdd1b3251105024bec73690da175 /api/src/gfapi.aliases | |
| parent | bef654f48c14bfd7ce20702edff41052f6f54bdc (diff) | |
| download | glusterfs-b42a048d3a76c7f377399f18d30f0a8a930f9d05.tar.gz glusterfs-b42a048d3a76c7f377399f18d30f0a8a930f9d05.tar.xz glusterfs-b42a048d3a76c7f377399f18d30f0a8a930f9d05.zip | |
features/bitrot: print the path of the corrupted objects
Currently "gluster volume bitrot <volume name> scrub status"
gives the list of the corrupted objects (files as of now).
But only the gfids of those corrupted objects are seen and
one has to do getfattr, find etc operations to get the actual
path of those objects for removal etc.
This change makes an attempt to print the path of those files
as much as possible.
* Try to get the path using the on disk gfid2path xattr.
* If the above operation fails, then go for in memory path
(provided that the object has its dentry
properly created and linked in the inode table of the brick where
the corrupted object is present) So the gfid to path resolution is
a soft resolution, i.e. based on the inode and dentry cache in the
brick's memory. If the path cannot be obtained via inode table also,
then only gfid is printed.
Change-Id: Ie9a30307f43a49a2a9225821803c7d40d231de68
fixes: bz#1570962
Signed-off-by: Raghavendra Bhat <raghavendra@redhat.com>
Diffstat (limited to 'api/src/gfapi.aliases')
0 files changed, 0 insertions, 0 deletions