From e884d2ed4c783f7a360c7d92d76bcb32f18ecfea Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Fri, 5 Aug 2022 16:17:09 +0000 Subject: [PATCH] Added a comment --- ...t_8_0d34bfeab48421e35c6880bca639cbb2._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_8_0d34bfeab48421e35c6880bca639cbb2._comment diff --git a/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_8_0d34bfeab48421e35c6880bca639cbb2._comment b/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_8_0d34bfeab48421e35c6880bca639cbb2._comment new file mode 100644 index 0000000000..8e059a15ea --- /dev/null +++ b/doc/bugs/crippled_filesystem__58___SQLite3_returned_ErrorBusy/comment_8_0d34bfeab48421e35c6880bca639cbb2._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 8" + date="2022-08-05T16:17:09Z" + content=""" +We have got user of cifs filesystem mount [reprorting](https://github.com/datalad/datalad/issues/6917#issuecomment-1206358866) that setting pidlock didn't help while using git-annex 10.20220504-g35cafb7 and cifs mount with options + +``` +type cifs (rw,relatime,vers=default,sec=krb5,cache=strict,multiuser,uid=164445,noforceuid,gid=100513,noforcegid,addr=172.19 +``` + +Please advise to how to troubleshoot such situation. + +NB I might later try similarish cifs mount of our local HPC which I believe might expose it similarly. +"""]]