commit | f286d627ef026a4d04b41ae5917d58ddf243c3c5 | [log] [tgz] |
---|---|---|
author | Andreas Gruenbacher <agruenba@redhat.com> | Mon Jan 13 21:21:49 2020 +0100 |
committer | Andreas Gruenbacher <agruenba@redhat.com> | Fri Jun 05 20:19:20 2020 +0200 |
tree | fac5959649e646e708c3d6412c984cc86d10221a | |
parent | 15f2547b4157a1e7e4d75bec5df097c1436f6cbd [diff] |
gfs2: Keep track of deleted inode generations in LVBs When deleting an inode, keep track of the generation of the deleted inode in the inode glock Lock Value Block (LVB). When trying to delete an inode remotely, check the last-known inode generation against the deleted inode generation to skip duplicate remote deletes. This avoids taking the resource group glock in order to verify the block type. Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>