search for: drop_writes

Displaying 4 results from an estimated 4 matches for "drop_writes".

Did you mean: drop_write
2013 Oct 28
0
[PATCH] xfstests: add generic/320 to test fsync() on directories V2
...e received a copy of the GNU General Public License +# along with this program; if not, write the Free Software Foundation, +# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA +# +# +# common functions for setting up and tearing down a dmflakey device + +FLAKEY_ALLOW_WRITES=0 +FLAKEY_DROP_WRITES=1 + +_init_flakey() +{ + local BLK_DEV_SIZE=`blockdev --getsz $SCRATCH_DEV` + FLAKEY_DEV=/dev/mapper/flakey-test + FLAKEY_TABLE="0 $BLK_DEV_SIZE flakey $SCRATCH_DEV 0 180 0" + FLAKEY_TABLE_DROP="0 $BLK_DEV_SIZE flakey $SCRATCH_DEV 0 0 180 1 drop_writes" + $DMSETUP_PROG create fl...
2013 Nov 15
7
[PATCH 1/2] xfstests: add generic/321 to test fsync() on directories V2
...build" rm -f $seqres.full -BLK_DEV_SIZE=`blockdev --getsz $SCRATCH_DEV` -FLAKEY_DEV=/dev/mapper/flakey-test SEED=1 testfile=$SCRATCH_MNT/$seq.fsync -FLAKEY_TABLE="0 $BLK_DEV_SIZE flakey $SCRATCH_DEV 0 180 0" -FLAKEY_TABLE_DROP="0 $BLK_DEV_SIZE flakey $SCRATCH_DEV 0 0 180 1 drop_writes" -_TEST_OPTIONS="" - -_mount_flakey() -{ - mount -t $FSTYP $MOUNT_OPTIONS $FLAKEY_DEV $SCRATCH_MNT -} - -_unmount_flakey() -{ - $UMOUNT_PROG $SCRATCH_MNT -} - -_load_flakey_table() -{ - # _load_flakey_table <table> - - table="$FLAKEY_TABLE" - [ $1 -eq 1 ] && t...
2013 Apr 25
10
[PATCH v4 0/3] Btrfs: quota rescan for 3.10
The kernel side for rescan, which is needed if you want to enable qgroup tracking on a non-empty volume. The first patch splits btrfs_qgroup_account_ref into readable ans reusable units. The second patch adds the rescan implementation (refer to its commit message for a description of the algorithm). The third patch starts an automatic rescan when qgroups are enabled. It is only separated to
2013 Feb 22
0
[PATCH 2/2] Btrfs: disable the qgroup level 0 for userspace use
From: Wang Shilong <wangsl-fnst@cn.fujitsu.com> This patch tries to stop users to create/destroy qgroup level 0, users can only create/destroy qgroup level more than 0. See the fact: a subvolume/snapshot qgroup was created automatically when creating subvolume/snapshot, so creating a qgroup level 0 can''t be a subvolume/snapshot qgroup, the only way to use it is that assigning