Bug 1377052 - Disperse volume, the deleted file show abnormality in the trashcan,and can't be deleted [NEEDINFO]
Summary: Disperse volume, the deleted file show abnormality in the trashcan,and can't ...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: trash-xlator
Version: 3.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Anoop C S
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-18 03:45 UTC by Kano
Modified: 2017-11-07 10:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-07 10:39:47 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
anoopcs: needinfo? (vovlvfp)


Attachments (Terms of Use)
The deleted file show abnormality (6.15 KB, image/png)
2016-09-18 03:45 UTC, Kano
no flags Details

Description Kano 2016-09-18 03:45:11 UTC
Created attachment 1202078 [details]
The deleted file show abnormality

Description of problem:

Only disperse volume has this bug, the deleted files show abnormality in the trashcan,as attributes and time ,and the file can't be deleted


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:

1.Create a disperse volume,use three nodes, and open the transhcan function;

2.Mount the disperse volume to a client,and cope some files to the mount point;

3.Delete the files in the mount point;

4.Turn into the transhcan(.transhcan) directory, look the attributes and time of the deleted files.

Actual results:

The attributes and time of the deleted files show abnormality,and the file can't be deleted from the transhcan again!


Expected results:


Additional info:

Comment 1 Anoop C S 2017-03-24 06:23:55 UTC
Hi,

Can you be more specific on what abnormality was seen with help of some output? Otherwise it very hard to guess the error.

Comment 2 Niels de Vos 2017-11-07 10:39:47 UTC
This bug is getting closed because the 3.8 version is marked End-Of-Life. There will be no further updates to this version. Please open a new bug against a version that still receives bugfixes if you are still facing this issue in a more current release.


Note You need to log in before you can comment on or make changes to this bug.