diff options
| author |  http://joeyh.name/ <http://joeyh.name/@web> | 2013-07-23 14:45:05 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2013-07-23 14:45:05 +0000 |
| commit | a667fda7e0bd3bb573552a5d3e2244daea1a7c87 (patch) | |
| tree | bf0a1f1aacc12d5b9b9cd817155fc4e2b8c98aa1 | |
| parent | c5209ac6ecfe3ba08982106a07b3d3915acf96ab (diff) | |
Added a comment
| -rw-r--r-- | doc/forum/How_to_destroy_a_master_annex_and_all_remotes_with_git_annex_assistant_and_ext4/comment_1_42ca6cfbbb79fe63514805b8119ac16b._comment | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/forum/How_to_destroy_a_master_annex_and_all_remotes_with_git_annex_assistant_and_ext4/comment_1_42ca6cfbbb79fe63514805b8119ac16b._comment b/doc/forum/How_to_destroy_a_master_annex_and_all_remotes_with_git_annex_assistant_and_ext4/comment_1_42ca6cfbbb79fe63514805b8119ac16b._comment new file mode 100644 index 000000000..f6d8396b7 --- /dev/null +++ b/doc/forum/How_to_destroy_a_master_annex_and_all_remotes_with_git_annex_assistant_and_ext4/comment_1_42ca6cfbbb79fe63514805b8119ac16b._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="2001:4978:f:21a::2" + subject="comment 1" + date="2013-07-23T14:45:05Z" + content=""" +It seems to me that it would be better to avoid using kernel features that crash. And, set up a git repository on another machine, which will serve as a real backup if something goes catostrophically wrong. The only potential failure mode then would be if a kernel/hardware issue zeroed some of your files, in direct mode the assistant might commit those new corrupt files and ship them over to the backup. But, if your offsite backup is accumulating old versions of files, you can recover from this by reverting the bad commit. +"""]] |