From: Joey Hess <joeyh@joeyh.name>
Date: Fri, 13 Nov 2015 20:34:54 +0000 (-0400)
Subject: devblog
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~324^2~13
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=6dfdc377380256827287b437d72a17192d9f70da;p=git-annex.git

devblog
---

diff --git a/doc/devblog/day_337__who_needs_POSIX.mdwn b/doc/devblog/day_337__who_needs_POSIX.mdwn
new file mode 100644
index 0000000000..3ab185cc91
--- /dev/null
+++ b/doc/devblog/day_337__who_needs_POSIX.mdwn
@@ -0,0 +1,21 @@
+Got the pid locks working pretty easily, as expected.
+
+But then... Detoured into some truely insane behavior of the Lustre
+filesystem. It seems that Lustre is perfectly happy to let link()
+succeed even when there's a file there that it would overwrite. Rather than
+overwriting the file, Lustre picks an even more crazy way to violate
+POSIX.. It lets there be 2 files in a directory with the **same name**, but
+different contents. Has to be seen to be believed:
+
+	hess$ ls pidlock
+	-r--r--r--  1 hess root    70 Nov 13 15:07 pidlock
+	-r--r--r--  1 hess root    70 Nov 13 15:07 pidlock
+	hess$ rm pidlock; ls pidlock
+	-r--r--r--  1 hess root    74 Nov 13 14:35 pidlock	
+
+git-annex's pid locking code now detects this and seems to work
+even on Lustre. Eep.
+
+I'm clutching my "NO WARRANTY" disclaimer pretty hard though, if anyone
+wants to use git-annex on Lustre. When POSIX is being violated this badly,
+it's hard to anticipate what other strangeness might result.