mirror of
https://github.com/ceph/ceph
synced 2024-12-11 14:09:09 +00:00
3d10b34074
The client is allowed to not send a snapflush if there is no dirty metadata to write for a given snap. However, the mds can only look up inodes by the last snapid in the interval. So, when doing a null_snapflush (filling in for snapflushes the client didn't send), we have to walk forward through intervening snaps until we find the right inode. Note that this means we will call _do_snap_update multiple times on the same inode, but with different snapids. Add unit test to check this. Signed-off-by: Sage Weil <sage@newdream.net> |
||
|---|---|---|
| .. | ||
| blogbench.sh | ||
| bonnie.sh | ||
| dbench.sh | ||
| ffsb.sh | ||
| fsx.sh | ||
| iozone.sh | ||
| kernel_untar_build.sh | ||
| pjd.sh | ||
| random_write.32.ffsb | ||
| snap-rm-diff.sh | ||
| snaptest-0.sh | ||
| snaptest-1.sh | ||
| snaptest-2.sh | ||
| snaptest-authwb.sh | ||
| snaptest-capwb.sh | ||
| snaptest-dir-rename.sh | ||
| snaptest-double-null.sh | ||
| snaptest-estale.sh | ||
| snaptest-git-ceph.sh | ||
| snaptest-multiple-capsnaps.sh | ||
| snaptest-parents.sh | ||
| snaptest-snap-rm-cmp.sh | ||
| snaptest-upchildrealms.sh | ||
| snaptest-xattrwb.sh | ||
| trivial_sync.sh | ||
| untar_snap_rm.sh | ||