Commit ea51f94b authored by Trond Myklebust's avatar Trond Myklebust Committed by Anna Schumaker

pNFS: Treat RECALLCONFLICT like DELAY...

Yes, it is possible to get trapped in a loop, but the server should be
administratively revoking the recalled layout if it never gets returned.
Signed-off-by: default avatarTrond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: default avatarAnna Schumaker <Anna.Schumaker@Netapp.com>
parent ecf84026
...@@ -1982,15 +1982,6 @@ pnfs_update_layout(struct inode *ino, ...@@ -1982,15 +1982,6 @@ pnfs_update_layout(struct inode *ino,
lseg = NULL; lseg = NULL;
break; break;
case -ERECALLCONFLICT: case -ERECALLCONFLICT:
/* Huh? We hold no layouts, how is there a recall? */
if (first) {
lseg = NULL;
break;
}
/* Destroy the existing layout and start over */
if (time_after(jiffies, giveup))
pnfs_destroy_layout(NFS_I(ino));
/* Fallthrough */
case -EAGAIN: case -EAGAIN:
break; break;
default: default:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment