summaryrefslogtreecommitdiff
path: root/doc/bugs/creating_a_plain_directory_where_a_mountpoint_should_have_been
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY <Vincent@web>2013-07-24 14:19:01 +0000
committerGravatar admin <admin@branchable.com>2013-07-24 14:19:01 +0000
commit2acb3105a266b736e83221a72c0ab4b68528c342 (patch)
treecec37df1a64020e1f6910d70277ac499ed1c92ff /doc/bugs/creating_a_plain_directory_where_a_mountpoint_should_have_been
parentc9bdb9dfa3e3994f0495ce8b0347017a3185df91 (diff)
Added a comment
Diffstat (limited to 'doc/bugs/creating_a_plain_directory_where_a_mountpoint_should_have_been')
-rw-r--r--doc/bugs/creating_a_plain_directory_where_a_mountpoint_should_have_been/comment_4_73848a9c783ecf3d9fccdd41b20fbe36._comment56
1 files changed, 56 insertions, 0 deletions
diff --git a/doc/bugs/creating_a_plain_directory_where_a_mountpoint_should_have_been/comment_4_73848a9c783ecf3d9fccdd41b20fbe36._comment b/doc/bugs/creating_a_plain_directory_where_a_mountpoint_should_have_been/comment_4_73848a9c783ecf3d9fccdd41b20fbe36._comment
new file mode 100644
index 000000000..7b588ecc7
--- /dev/null
+++ b/doc/bugs/creating_a_plain_directory_where_a_mountpoint_should_have_been/comment_4_73848a9c783ecf3d9fccdd41b20fbe36._comment
@@ -0,0 +1,56 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawkfHTPsiAcHEEN7Xl7WxiZmYq-vX7azxFY"
+ nickname="Vincent"
+ subject="comment 4"
+ date="2013-07-24T14:19:01Z"
+ content="""
+I saw this too, today. The repo in my case was created via the webapp, using the 'usb key' option.
+I was messing about with deleting repos and had turned off synchronisation for the repo on the key as I didn't have it inserted.
+
+I only just stumbled on this bug report after removing the repository from the key entirely, so it's difficult to define the reproduction steps.
+
+* create a 'usb key' repo via webapp, transfer type
+* let it sync
+* disable sync
+* change a file in another repo, so there is something to sync
+* unmount key, unplug key
+* turn on sync again - should see 'failed ot sync with ...' in webapp dashboard
+* reinsert key
+* let it sync
+* unplug key without properly unmounting
+* change a file in another repo, so there is something to sync
+
+I just did this. The key was mounting at /Volumes/VERBATIM4. Just after unplugging without unmounting, that directory was gone.
+When I made the change that could be synced, I got a /Volumes/VERBATIM4 directory. The directory tree structure is similar to but different
+from the structure on the usb key, see below.
+
+Now when I try to plug it in again os/x will spot the potential conflict and mount the key at /Volumes/VERBATIM4\ 1.
+
+If I instead rm -rf /Volumes/VERBATIM4 and then replug the usb key, everything syncs as expected.
+
+Version: 4.20130723-ge023649 (os/x 10.8)
+
+Build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
+
+Tree structure of the phantom directory:
+
+ /Volumes/VERBATIM4/annex/
+ └── annex
+ ├── journal.lck
+ ├── objects
+ │   └── df3
+ │   └── 043
+ │   └── SHA256E-s17363--4c5ef74b4fcb9ecd962c6ecac694f87277e580836335e57924654762668a5448
+ │   └── SHA256E-s17363--4c5ef74b4fcb9ecd962c6ecac694f87277e580836335e57924654762668a5448
+ ├── tmp
+ └── transfer
+ ├── download
+ │   └── adf30a67-777a-45a6-a658-e2266770f01b
+ └── failed
+ └── download
+ └── adf30a67-777a-45a6-a658-e2266770f01b
+ └── SHA256E-s17363--4c5ef74b4fcb9ecd962c6ecac694f87277e580836335e57924654762668a5448
+
+ 12 directories, 3 files
+
+"""]]