test for directory fsync after adding
hard links
On Tue, Feb 24, 2015 at 05:40:05PM -0600, Eric Sandeen wrote:
On 2/24/15 5:29 PM, Filipe Manana wrote:
diff --git a/tests/generic/060 b/tests/generic/060
new file mode 100755
index 000..0d459fa
--- /dev/null
+++ b
On 2/24/15 5:29 PM, Filipe Manana wrote:
This test is motivated by an fsync issue discovered in btrfs.
The issue was that after adding a new hard link to an existing file
(one that was created in a past transaction) and fsync'ing the parent
directory of the new hard link, after the fsync log
On Tue, Feb 24, 2015 at 05:40:05PM -0600, Eric Sandeen wrote:
On 2/24/15 5:29 PM, Filipe Manana wrote:
diff --git a/tests/generic/060 b/tests/generic/060
new file mode 100755
index 000..0d459fa
--- /dev/null
+++ b/tests/generic/060
@@ -0,0 +1,175 @@
+#! /bin/bash
+# FS QA
This test is motivated by an fsync issue discovered in btrfs.
The issue was that after adding a new hard link to an existing file
(one that was created in a past transaction) and fsync'ing the parent
directory of the new hard link, after the fsync log replay the file's
inode link count did not get
