Back to bug 1235633

Who When What Removed Added
Sakshi 2015-06-30 09:31:51 UTC CC sabansal
Rejy M Cyriac 2015-07-03 06:23:27 UTC Keywords ZStream
Rahul Hinduja 2015-07-08 06:56:21 UTC Severity high urgent
Rahul Hinduja 2015-07-08 06:59:37 UTC QA Contact storage-qa-internal rhinduja
Nithya Balachandran 2015-07-16 05:37:17 UTC CC nbalacha
Doc Text Cause: Concurrent rmdir and lookup operations on a directory during a recursive remove can prevent the directory from being deleted on some bricks.

Consequence:
The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.


Workaround (if any):
Unmount the volume and delete the contents of the directory in question on each brick.

Result:
Doc Type Bug Fix Known Issue
Nithya Balachandran 2015-07-16 10:13:33 UTC Blocks 1216951
Nithya Balachandran 2015-07-16 10:15:08 UTC Doc Text Cause: Concurrent rmdir and lookup operations on a directory during a recursive remove can prevent the directory from being deleted on some bricks.

Consequence:
The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.


Workaround (if any):
Unmount the volume and delete the contents of the directory in question on each brick.

Result:
Cause: Concurrent rmdir and lookup operations on a directory during a recursive remove can prevent the directory from being deleted on some bricks.

Consequence:
The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.


Workaround (if any):
Unmount the volume and delete the contents of the directory in question on each brick.

If the affected slave is a geo-replication slave volume, run "stop geo-rep session" before the deleting the contents of the directory on the bricks.

Result:
Aravinda VK 2015-07-21 13:34:09 UTC Blocks 1238068
monti lawrence 2015-07-22 19:19:55 UTC CC mlawrenc, rhs-bugs
Doc Text Cause: Concurrent rmdir and lookup operations on a directory during a recursive remove can prevent the directory from being deleted on some bricks.

Consequence:
The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.


Workaround (if any):
Unmount the volume and delete the contents of the directory in question on each brick.

If the affected slave is a geo-replication slave volume, run "stop geo-rep session" before the deleting the contents of the directory on the bricks.

Result:
Concurrent rmdir and lookup operations on a directory during a recursive remove may prevent the directory from being deleted on some bricks. The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.

Workaround:
Unmount the volume and delete the contents of the directory on each brick. If the affected slave is a geo-replication slave volume, run "stop geo-rep session" before deleting the contents of the directory on the bricks.
Flags needinfo?(rhs-bugs)
Sakshi 2015-07-23 09:51:12 UTC Depends On 1245065
Anjana Suparna Sriram 2015-07-25 17:43:27 UTC CC asriram
Nithya Balachandran 2015-07-27 05:06:49 UTC Doc Text Concurrent rmdir and lookup operations on a directory during a recursive remove may prevent the directory from being deleted on some bricks. The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.

Workaround:
Unmount the volume and delete the contents of the directory on each brick. If the affected slave is a geo-replication slave volume, run "stop geo-rep session" before deleting the contents of the directory on the bricks.
Concurrent rmdir and lookup operations on a directory during a recursive remove may prevent the directory from being deleted on some bricks. The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.

Workaround:
Unmount the volume and delete the contents of the directory on each brick. If the affected volume is a geo-replication slave volume, run "stop geo-rep session" before deleting the contents of the directory on the bricks.
Anjana Suparna Sriram 2015-07-28 02:57:21 UTC Flags needinfo?(rhs-bugs)
Anoop 2015-08-04 05:06:49 UTC CC annair
Alok 2015-08-05 05:38:50 UTC CC asrivast
Rejy M Cyriac 2015-08-07 06:58:27 UTC Target Release --- RHGS 3.1.1
monti lawrence 2015-08-07 13:23:51 UTC CC mlawrenc
Rejy M Cyriac 2015-08-10 04:11:36 UTC Blocks 1251815
Nithya Balachandran 2015-08-12 05:12:56 UTC Assignee rhs-bugs sabansal
Susant Kumar Palai 2015-08-18 06:51:28 UTC Status NEW POST
CC spalai
Susant Kumar Palai 2015-08-26 07:09:18 UTC Doc Text Concurrent rmdir and lookup operations on a directory during a recursive remove may prevent the directory from being deleted on some bricks. The recursive remove operation fails with "Directory not empty" errors even though the directory listing from the mount point shows no entries.

Workaround:
Unmount the volume and delete the contents of the directory on each brick. If the affected volume is a geo-replication slave volume, run "stop geo-rep session" before deleting the contents of the directory on the bricks.
Doc Type Known Issue Bug Fix
Sakshi 2015-08-28 10:49:09 UTC Depends On 1257894
Vivek Agarwal 2015-08-31 09:33:46 UTC CC vagarwal
Blocks 1251815
Red Hat Bugzilla Rules Engine 2015-08-31 09:33:48 UTC Target Release RHGS 3.1.1 ---
Vivek Agarwal 2015-09-29 12:36:13 UTC Blocks 1260783
Vivek Agarwal 2015-10-09 11:25:15 UTC Blocks 1260783
John Skeoch 2016-02-18 00:13:56 UTC CC vagarwal sankarshan
Rejy M Cyriac 2016-02-19 16:52:05 UTC Blocks 1299184
Satish Mohan 2016-03-08 11:51:02 UTC CC smohan
Red Hat Bugzilla Rules Engine 2016-03-08 12:18:21 UTC Target Release --- RHGS 3.1.3
Satish Mohan 2016-03-15 10:31:35 UTC Status POST CLOSED
Resolution --- DUPLICATE
Last Closed 2016-03-15 06:31:35 UTC
Rejy M Cyriac 2016-03-17 16:18:40 UTC Target Release RHGS 3.1.3 ---
Blocks 1299184

Back to bug 1235633