search for: 8394642

...root root 0 Apr 28 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. So my question here is, is it possible that this is a stale file which just forgot to get deleted from the indices/xattrop file by gluster for some unknown reason? If yes is it safe for me to delete these two files? or what would be the correct process in...

...c-9bda-1fbbf781c397 > 2798404 ---------- 2 root root 0 Apr 28 22:51 > xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 > > > > I tried to find the real file on my brick where this xattrop file > points to using its inode number (command: find > /data/myvolume/brick/data -inum 8394642) but it does not find any > associated file. > > So my question here is, is it possible that this is a stale file which > just forgot to get deleted from the indices/xattrop file by gluster > for some unknown reason? If yes is it safe for me to delete these two > files? or wha...

...8 22:51 29e0d13e-1217-41cc-9bda-1fbbf781c397 >> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >> So my question here is, is it possible that this is a stale file which just forgot to get deleted from the indices/xattrop file by gluster for some unknown reason? If yes is it safe for me to delete these two files? or what would be the correct pr...

...0 Apr 28 22:51 >>> xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>> >>> >>> >>> I tried to find the real file on my brick where this xattrop file >>> points to using its inode number (command: find >>> /data/myvolume/brick/data -inum 8394642) but it does not find any >>> associated file. >>> >>> So my question here is, is it possible that this is a stale file >>> which just forgot to get deleted from the indices/xattrop file by >>> gluster for some unknown reason? If yes is it safe for me...

...-1217-41cc-9bda-1fbbf781c397 >>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>>> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >>>> So my question here is, is it possible that this is a stale file which just forgot to get deleted from the indices/xattrop file by gluster for some unknown reason? If yes is it safe for me to delete these two files? or what would be the co...

...dd-4ec2-9246-7b302ab92d38 >>>>> >>>>> >>>>> >>>>> I tried to find the real file on my brick where this xattrop file >>>>> points to using its inode number (command: find >>>>> /data/myvolume/brick/data -inum 8394642) but it does not find any >>>>> associated file. >>>>> >>>>> So my question here is, is it possible that this is a stale file >>>>> which just forgot to get deleted from the indices/xattrop file by >>>>> gluster for some...

...1fbbf781c397 >>>>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>>>>> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >>>>>> So my question here is, is it possible that this is a stale file which just forgot to get deleted from the indices/xattrop file by gluster for some unknown reason? If yes is it safe for me to delete these two files? or what would b...

...t;> >>>>>>> >>>>>>> >>>>>>> I tried to find the real file on my brick where this xattrop >>>>>>> file points to using its inode number (command: find >>>>>>> /data/myvolume/brick/data -inum 8394642) but it does not find >>>>>>> any associated file. >>>>>>> >>>>>>> So my question here is, is it possible that this is a stale file >>>>>>> which just forgot to get deleted from the indices/xattrop file >>&...

...;>>>>>>> 2798404 ---------- 2 root root 0 Apr 28 22:51 xattrop-6fa49ad5-71dd-4ec2-9246-7b302ab92d38 >>>>>>>> I tried to find the real file on my brick where this xattrop file points to using its inode number (command: find /data/myvolume/brick/data -inum 8394642) but it does not find any associated file. >>>>>>>> So my question here is, is it possible that this is a stale file which just forgot to get deleted from the indices/xattrop file by gluster for some unknown reason? If yes is it safe for me to delete these two files? or what...

...gt; >>>>>>>>> >>>>>>>>> I tried to find the real file on my brick where this xattrop >>>>>>>>> file points to using its inode number (command: find >>>>>>>>> /data/myvolume/brick/data -inum 8394642) but it does not find >>>>>>>>> any associated file. >>>>>>>>> >>>>>>>>> So my question here is, is it possible that this is a stale >>>>>>>>> file which just forgot to get deleted from the...