Back to bug 1325760

Who When What Removed Added
Red Hat Bugzilla Rules Engine 2016-04-11 06:48:45 UTC Keywords ZStream
Rahul Hinduja 2016-04-12 11:59:16 UTC Keywords Regression
Aravinda VK 2016-04-13 06:01:18 UTC Status NEW ASSIGNED
CC avishwan
Assignee rhs-bugs rgowdapp
Milind Changire 2016-04-19 06:35:31 UTC CC mchangir
Rahul Hinduja 2016-04-19 06:54:56 UTC Blocks 1311817
Alok 2016-04-19 09:48:58 UTC CC asrivast
Red Hat Bugzilla Rules Engine 2016-04-19 09:55:31 UTC Target Release --- RHGS 3.1.3
Rahul Hinduja 2016-04-21 08:10:41 UTC QA Contact storage-qa-internal rhinduja
Raghavendra G 2016-05-02 06:36:29 UTC Component glusterfs-geo-replication gluster-dht
Assignee rgowdapp rhs-bugs
QA Contact rhinduja storage-qa-internal
Nithya Balachandran 2016-05-05 10:19:02 UTC CC nbalacha
Nithya Balachandran 2016-05-09 04:12:55 UTC Assignee rhs-bugs rgowdapp
Raghavendra G 2016-05-09 04:55:39 UTC Blocks 1334164
Atin Mukherjee 2016-05-13 04:38:58 UTC Status ASSIGNED POST
CC amukherj
Raghavendra G 2016-05-16 06:00:40 UTC Blocks 1336284
Raghavendra G 2016-05-16 06:02:06 UTC Blocks 1336285
Raghavendra G 2016-05-17 03:19:38 UTC Status POST MODIFIED
errata-xmlrpc 2016-05-17 08:54:23 UTC Status MODIFIED ON_QA
Milind Changire 2016-05-17 09:58:11 UTC Fixed In Version glusterfs-3.7.9-5
Rahul Hinduja 2016-05-17 11:23:47 UTC QA Contact storage-qa-internal rhinduja
Raghavendra G 2016-05-20 07:32:14 UTC Doc Text Cause: Failure in dht-selfheal resulted in a proper layout not being set in the inode. Without a proper layout, future directory entry operations on that directory inode would fail. The reason for failure of dht selfheal was the usage of an invalid inode for all the operations used in dht selfheal.

Consequence: Directory operations fail on the directory

Fix: The inode used was invalid as it was not linked into inode table _yet_ during dht selfheal. Current fix is to link the inode in inode table before proceeding with selfheal.

Result: No problem with execution of directory operations like create, mkdir, rename etc.
Raghavendra G 2016-05-20 07:33:27 UTC Doc Text Cause: Failure in dht-selfheal resulted in a proper layout not being set in the inode. Without a proper layout, future directory entry operations on that directory inode would fail. The reason for failure of dht selfheal was the usage of an invalid inode for all the operations used in dht selfheal.

Consequence: Directory operations fail on the directory

Fix: The inode used was invalid as it was not linked into inode table _yet_ during dht selfheal. Current fix is to link the inode in inode table before proceeding with selfheal.

Result: No problem with execution of directory operations like create, mkdir, rename etc.
Cause: Failure in dht-selfheal resulted in a incomplete layout being set in the inode. Without a proper layout, future directory entry operations on that directory inode would fail. The reason for failure of dht selfheal was the usage of an invalid inode for all the operations used in dht selfheal.

Consequence: Directory operations fail on the directory

Fix: The inode used was invalid as it was not linked into inode table _yet_ during dht selfheal. Current fix is to link the inode in inode table before proceeding with selfheal.

Result: No problem with execution of directory operations like create, mkdir, rename etc.
Raghavendra G 2016-05-20 07:34:33 UTC Doc Text Cause: Failure in dht-selfheal resulted in a incomplete layout being set in the inode. Without a proper layout, future directory entry operations on that directory inode would fail. The reason for failure of dht selfheal was the usage of an invalid inode for all the operations used in dht selfheal.

Consequence: Directory operations fail on the directory

Fix: The inode used was invalid as it was not linked into inode table _yet_ during dht selfheal. Current fix is to link the inode in inode table before proceeding with selfheal.

Result: No problem with execution of directory operations like create, mkdir, rename etc.
Cause: Failure in dht-selfheal resulted in an incomplete layout being set in the inode. Without a proper layout, future directory entry operations on that directory inode would fail. The reason for failure of dht selfheal was the usage of an invalid inode for all the operations used in dht selfheal.

Consequence: Directory operations like create, mknod, mkdir, rename, link etc fail on the directory

Fix: The inode used was invalid as it was not linked into inode table _yet_ during dht selfheal. Current fix is to link the inode in inode table before proceeding with selfheal.

Result: No problem with execution of directory operations like create, mkdir, rename etc.
Rahul Hinduja 2016-05-24 06:48:43 UTC Status ON_QA VERIFIED
Laura Bailey 2016-06-06 01:36:28 UTC CC rgowdapp
Doc Text Cause: Failure in dht-selfheal resulted in an incomplete layout being set in the inode. Without a proper layout, future directory entry operations on that directory inode would fail. The reason for failure of dht selfheal was the usage of an invalid inode for all the operations used in dht selfheal.

Consequence: Directory operations like create, mknod, mkdir, rename, link etc fail on the directory

Fix: The inode used was invalid as it was not linked into inode table _yet_ during dht selfheal. Current fix is to link the inode in inode table before proceeding with selfheal.

Result: No problem with execution of directory operations like create, mkdir, rename etc.
An invalid inode that was not yet linked in the inode table could be used for a Distributed Hash Table self-heal operation. This caused self-heal to fail, and an incomplete directory layout to be set in the inode. This meant directory operations such as create, mknod, mkdir, rename, and link failed on that directory. This update ensures that inodes are linked in the inode table prior to performing self-heal operations, so directory operations succeed.
Flags needinfo?(rgowdapp)
Raghavendra G 2016-06-10 04:24:19 UTC Flags needinfo?(rgowdapp) needinfo+
Raghavendra G 2016-06-20 04:48:33 UTC Blocks 1348060
errata-xmlrpc 2016-06-23 00:52:20 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-06-23 05:16:34 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-06-23 01:16:34 UTC

Back to bug 1325760