Bug #1324
closed
cfuse: 2-MDS snaptest2 doesn't let client unmount
Added by Greg Farnum almost 13 years ago.
Updated over 7 years ago.
Description
On occasions when running snaptests-2 doesn't hit #1323, the client will happily unmount from the filesystem but the process won't exit because there are inodes still in the cache. It's probably a ref-counting bug. Logs in kai:~gregf/logs/snaptest2shutdownfail.
- Status changed from In Progress to 7
queue_cap_snap takes a reference to the inode that's never put by anything as best I can tell. I've added one to the end of finish_cap_snap which I presume should handle it. Testing now.
Okay, that's not correct. Sage says this put() should be happening in handle_cap_flushsnap_ack, which is just never being called. Which makes sense for a 2-MDS issue.
And it turns out the client is unconditionally setting mseq to 0 and then the MDS is rejecting it if the auth has changed. Testing now.
- Status changed from 7 to Resolved
Pushed in commit:022c5261800ba6f9642b1f8dc7e44c91b12956eb
- Project changed from Ceph to CephFS
- Category deleted (
11)
- Target version deleted (
v0.32)
Bulk updating project=ceph category=ceph-fuse issues to move to fs project so that we can remove the ceph-fuse category from the ceph project
Also available in: Atom
PDF