[Bugs] [Bug 1236032] Tiering: unlink failed with error "Invaid argument"

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1236032

Mohammed Rafi KC <rkavunga at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|dlambrig at redhat.com         |rkavunga at redhat.com



--- Comment #4 from Mohammed Rafi KC <rkavunga at redhat.com> ---
RCA.

Since, all of the fops will be hashed to hot_tier after attach-tier (unless
explicitly set the "rule" option), the lookups sent to directory, will
eventually search the directory using readdirp, and will populate inode_ctx for
the inodes based on the output, in respective dht_xlators. So the readdirp will
populate inodes_ctx for the files (that is already being present in volume
before attaching) in cold-dht, only because it got the entries from the
cold-tier.

So when an unlink comes on such an inode, the lookup associated with the unlink
will be send as a re validate request to cold-tier only, since already a lookup
was performed on the inode, and the new lookup will succeed. So from the unlink
of dht, it will hash to cold-tier but the cached_subvol will be cold, since
there is a mismatch in hash and cach , it chose hashed subvolume and will sent
the fop to hot dht, and the fops fail with EINVAL from the hot-dht since it
does not have inode_ctx stored for that inode (because, no lookup was performed
from hot-dht).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.