Rename-overwrites over NFS work with a "silly rename" over the
network, so the nlink count stays at 1 instead of dropping to 0.
This is expected behavior for NFS, so we should use a different
golden output file to account for this.
See the NFS faq at: nfs.sourceforge.net/#faq_d2 for more
information about silly renames.
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>
/dmapi/src/suite2/src/test_rights
# Symlinked files
/dmapi/src/suite2/src/test_rights
# Symlinked files
/tests/xfs/033.out
/tests/xfs/071.out
/tests/xfs/096.out
/tests/xfs/033.out
/tests/xfs/071.out
/tests/xfs/096.out
local features
if [ $# -eq 0 ]; then
local features
if [ $# -eq 0 ]; then
- features="$(_get_os_name)"
+ features="$(_get_os_name),$FSTYP"
if [ -n "$MOUNT_OPTIONS" ]; then
features=$features,${MOUNT_OPTIONS##"-o "}
fi
if [ -n "$MOUNT_OPTIONS" ]; then
features=$features,${MOUNT_OPTIONS##"-o "}
fi
#
# Check overwriting rename system call
#
#
# Check overwriting rename system call
#
seq=`basename $0`
seqres=$RESULT_DIR/$seq
echo "QA output created by $seq"
seq=`basename $0`
seqres=$RESULT_DIR/$seq
echo "QA output created by $seq"
+# Select appropriate golden output based on fstype
+_link_out_file
+
# real QA test starts here
rename_dir=$TEST_DIR/$$
# real QA test starts here
rename_dir=$TEST_DIR/$$
+++ /dev/null
-QA output created by 035
-overwriting regular file:
-overwriting directory:
--- /dev/null
+QA output created by 035
+overwriting regular file:
+overwriting directory:
--- /dev/null
+QA output created by 035
+overwriting regular file:
+nlink is 1, should be 0
+overwriting directory:
+t_rename_overwrite: fstat(3): Stale file handle