ceph/qa/workunits/fs/snaps/snaptest-double-null.sh

#!/bin/sh -x

set -e

ceph mds set allow_new_snaps true --yes-i-really-mean-it

# multiple intervening snapshots with no modifications, and thus no
# snapflush client_caps messages.  make sure the mds can handle this.

for f in `seq 1 20` ; do

mkdir a
cat > a/foo &
mkdir a/.snap/one
mkdir a/.snap/two
chmod 777 a/foo
sync   # this might crash the mds
ps
rmdir a/.snap/*
rm a/foo
rmdir a

done

echo OK
mds: fix null_snapflush with multiple intervening snaps 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> 2010-11-11 04:58:49 +00:00			`#!/bin/sh -x`

			`set -e`

qa/workunits/snaps: New allow_new_snaps syntax These were probably just obscuring other failures. Reviewed-by: Sage Weil <sage@inktank.com> Signed-off-by: John Spray <john.spray@inktank.com> 2014-02-05 18:44:40 +00:00			`ceph mds set allow_new_snaps true --yes-i-really-mean-it`
qa: update snaps workunits for allow_new_snaps flag Test that it works in snaptest-0.sh, and set the flag in all the snap workunits so they continue to function. Signed-off-by: Greg Farnum <greg@inktank.com> Reviewed-by: Loic Dachary <loic@dachary.org> 2013-09-25 23:02:02 +00:00
mds: fix null_snapflush with multiple intervening snaps 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> 2010-11-11 04:58:49 +00:00			`# multiple intervening snapshots with no modifications, and thus no`
			`# snapflush client_caps messages. make sure the mds can handle this.`

			for f in `seq 1 20` ; do

			`mkdir a`
			`cat > a/foo &`
			`mkdir a/.snap/one`
			`mkdir a/.snap/two`
			`chmod 777 a/foo`
			`sync # this might crash the mds`
			`ps`
			`rmdir a/.snap/*`
			`rm a/foo`
			`rmdir a`

			`done`

			`echo OK`