summaryrefslogtreecommitdiff
path: root/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment
diff options
context:
space:
mode:
Diffstat (limited to 'doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment')
-rw-r--r--doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment
new file mode 100644
index 000000000..15dde50f8
--- /dev/null
+++ b/doc/bugs/unable_to_decommit_memory__58___Invalid_argument/comment_10_b21a337256c58953e1440317c0c1db80._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 10"""
+ date="2016-12-19T19:53:11Z"
+ content="""
+The only way the files could be in lost+found is if the system crashed or
+there was a disk error etc. Can't be due to this bug. So, it may be that
+this bug did not actually cause any data loss. The screwed up symlinks could
+have been caused by a disk error.
+"""]]