Bug 1237375

Summary:	Trashcan broken on Distribute-Replicate volume
Product:	[Community] GlusterFS	Reporter:	kevinallan81
Component:	trash-xlator	Assignee:	Anoop C S <anoopcs>
Status:	CLOSED EOL	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.7.2	CC:	anoopcs, bugs, jthottan, kevinallan81, nlevinki, rkavunga, sasundar, vbellur
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-08 10:52:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description kevinallan81 2015-07-01 00:34:41 UTC

Description of problem:
When the trashcan feature is turned on, deleted files are not appearing in the .trashcan folder (however the appropriate folder is created). Files deleted in the root of the volume show up on the brick correctly, but files in any folder that are deleted show up in on a brick with ------T permissions and 0 file size. Doing an 'ls' to where the file should be on the mount gives 'Stale file handle' error.

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

How reproducible:
Every time

Steps to Reproduce:
1. Turn on trashcan with Distribute-Replicate volume
2. Delete a file
3. Look for it in .trashcan folder

Actual results:
File is not in .trashcan folder and doing an 'ls' to where it should be gives 'Stale file handle' error

Expected results:
Deleted file should be in the .trashcan folder

Additional info:

Comment 2 SATHEESARAN 2015-07-01 02:59:06 UTC

Looks like this issue is filed for 3.7.2 version of glusterfs community product. Trash feature is not yet supported in 'Red Hat Gluster Storage' product. 

If you are using upstream version of glusterfs, please choose 'GlusterFS' as a product, while filing bugs

Comment 3 Anoop C S 2017-02-21 07:29:30 UTC

Can you please try the reproducer on a more recent version and see if the issue still exists?

Comment 4 Kaushal 2017-03-08 10:52:04 UTC

This bug is getting closed because GlusteFS-3.7 has reached its end-of-life.

Note: This bug is being closed using a script. No verification has been performed to check if it still exists on newer releases of GlusterFS.
If this bug still exists in newer GlusterFS releases, please reopen this bug against the newer release.

Comment 5 Red Hat Bugzilla 2023-09-14 03:01:24 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days