Back to bug 1387494
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ravishankar N | 2016-10-21 05:54:49 UTC | Keywords | Triaged | |
| Rahul Hinduja | 2016-10-24 07:01:49 UTC | CC | rhinduja | |
| Blocks | 1351528 | |||
| Red Hat Bugzilla Rules Engine | 2016-10-25 14:38:00 UTC | Target Release | --- | RHGS 3.2.0 |
| Ravishankar N | 2016-11-12 07:52:40 UTC | Flags | needinfo?(ksandha) | |
| Karan Sandha | 2016-11-14 06:05:08 UTC | Summary | Files not deleted from data brick after deletion from the mount point. | Files not deleted from arbiter brick after deletion from the mount point. |
| Flags | needinfo?(ksandha) | |||
| Atin Mukherjee | 2016-11-14 13:41:56 UTC | CC | amukherj | |
| Atin Mukherjee | 2016-11-16 11:22:37 UTC | Target Release | RHGS 3.2.0 | --- |
| Blocks | 1351528 | |||
| Atin Mukherjee | 2016-11-16 12:08:59 UTC | CC | ravishankar | |
| Doc Type | If docs needed, set a value | Known Issue | ||
| Flags | needinfo?(ravishankar) | |||
| Ravishankar N | 2016-11-16 14:00:49 UTC | Environment | If the data bricks of the arbiter volume get filled up, further creation of new entries might succeed in the arbiter brick despite failing on the data bricks with ENOSPC and the application (client) itself receiving an error on the mount point. Thus the arbiter bricks might have more entries. Now when an rm -rf is performed from the client, if the readdir (as a part of rm -rf) gets served on the data brick, it might delete only those entries and not the ones present only in the arbiter. When the rmdir on the parent dir of these entries comes, it won't succeed on the arbiter (errors out with ENOTEMPTY), leading to it not being removed from arbiter. Workaround: If the deletion from the mount did not complain but the bricks still contain the directories, we would need to remove the directory and its associated gfid symlink from the back end. If the directory contains files, they (file + its gfid hardlink) would need to be removed too. |
|
| Ravishankar N | 2016-11-16 14:01:41 UTC | Blocks | 1351530 | |
| Ravishankar N | 2016-11-16 14:02:45 UTC | Flags | needinfo?(ravishankar) | |
| Rejy M Cyriac | 2016-11-23 05:12:39 UTC | CC | rcyriac | |
| Ravishankar N | 2017-02-16 05:54:43 UTC | Blocks | 1417147 | |
| Alok | 2017-02-28 06:02:14 UTC | CC | asrivast | |
| Red Hat Bugzilla Rules Engine | 2017-02-28 10:15:16 UTC | Target Release | --- | RHGS 3.3.0 |
| Ravishankar N | 2017-03-02 01:40:22 UTC | Environment | If the data bricks of the arbiter volume get filled up, further creation of new entries might succeed in the arbiter brick despite failing on the data bricks with ENOSPC and the application (client) itself receiving an error on the mount point. Thus the arbiter bricks might have more entries. Now when an rm -rf is performed from the client, if the readdir (as a part of rm -rf) gets served on the data brick, it might delete only those entries and not the ones present only in the arbiter. When the rmdir on the parent dir of these entries comes, it won't succeed on the arbiter (errors out with ENOTEMPTY), leading to it not being removed from arbiter. Workaround: If the deletion from the mount did not complain but the bricks still contain the directories, we would need to remove the directory and its associated gfid symlink from the back end. If the directory contains files, they (file + its gfid hardlink) would need to be removed too. | |
| Doc Text | If the data bricks of the arbiter volume get filled up, further creation of new entries might succeed in the arbiter brick despite failing on the data bricks with ENOSPC and the application (client) itself receiving an error on the mount point. Thus the arbiter bricks might have more entries. Now when an rm -rf is performed from the client, if the readdir (as a part of rm -rf) gets served on the data brick, it might delete only those entries and not the ones present only in the arbiter. When the rmdir on the parent dir of these entries comes, it won't succeed on the arbiter (errors out with ENOTEMPTY), leading to it not being removed from arbiter. Workaround: If the deletion from the mount did not complain but the bricks still contain the directories, we would need to remove the directory and its associated gfid symlink from the back end. If the directory contains files, they (file + its gfid hardlink) would need to be removed too. |
|||
| Atin Mukherjee | 2017-05-17 12:28:14 UTC | Target Release | RHGS 3.3.0 | --- |
| Blocks | 1417147 | |||
| Ravishankar N | 2017-05-24 12:53:52 UTC | CC | nchilaka | |
| Red Hat Bugzilla Rules Engine | 2017-06-28 09:06:15 UTC | Keywords | ZStream | |
| Ravishankar N | 2017-08-30 05:02:25 UTC | Priority | unspecified | low |
| Ravishankar N | 2017-08-30 05:09:53 UTC | Priority | low | medium |
| PnT Account Manager | 2018-02-08 00:13:39 UTC | CC | asrivast | |
| Matthias Muench | 2018-05-03 09:06:50 UTC | CC | mmuench | |
| Ravishankar N | 2018-11-19 05:33:10 UTC | Status | NEW | CLOSED |
| Resolution | --- | WONTFIX | ||
| Last Closed | 2018-11-19 00:33:10 UTC |
Back to bug 1387494