From 608313abb185ed508997c5b6327a8d4993e0d28e Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Mon, 11 Jan 2016 21:17:10 +0100 Subject: [PATCH] Auto update --- faq.html | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/faq.html b/faq.html index 0e8f71cc..00e262c4 100644 --- a/faq.html +++ b/faq.html @@ -145,6 +145,7 @@ Frequently Asked Questions for SnapRAID.
  • In Linux SnapRAID aborts without any error message
  • Running 'sync' I get the error 'Failed to grow parity file 'xxx' to size xxx due lack of space.'
  • I get the error 'Internal inode xxx incosistency...'
    • +
  • I get the error 'Data change at file...' for .xls files
    • @@ -1253,6 +1254,36 @@ Theoretically inodes (FileIndex) are but this condition was already seen in the field.

    +

    I get the error 'Data change at file...' for .xls files

    + +

    +Unfortunately the Excel application does dirty tricks when handling .xls files, +that may cause the folllowing data error. +

    + +
    +Data change at file '/xxx/xxx.xls' at position '0'
+WARNING! Unexpected data modification of a file without parity!
+
    + + +

    +This happens because Excel modifies the files after opening them, even you don't press 'Save'. +It stores the name of the last user that opened them, to be able to report it, if another user tries +to open the same file at the same time. +But to avoid to have the file triggered as modified, it restores the timestamp to its original value. +

    + +

    +You have then a file with the same timestamp but different content. And this is not good for SnapRAID. +

    + +

    +To workaround the problem you can see +How to prevent Excel from modifying the file on exit?, +or you can switch to the .xlsx format. +

    +