From: "briangpowell ." <briangpowellms@gmail.com>
To: Nick Dokos <ndokos@gmail.com>, Brian Powell <briangpowellms@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [OT] Git plus Syncthing: breaking hard links
Date: Tue, 5 Apr 2016 19:29:35 -0400 [thread overview]
Message-ID: <CAFm0skFOxdN9O7p3BGQDexSNha+P33Ern3NtdFH_qOJePckp1w@mail.gmail.com> (raw)
In-Reply-To: <87bn5o1ax5.fsf@pierrot.dokosmarshall.org>
[-- Attachment #1: Type: text/plain, Size: 3188 bytes --]
* Strongly recommend you pay close attention to Nick Dokos--he's
brilliant--agree totally with his suggestions; "hardlinks cannot span
filesystems" etc.
** "hardlinks breaking"--in rsync I throw -H to include/follow hard links
across filesystems when syncing.
*** I'm with Nick though again--not sure what you mean by "hardlinks
breaking"
* Thanks for the "syncthing" link and comments--its open source:
"Syncthing
https://syncthing.net/
Syncthing replaces proprietary sync and cloud services with something open,
trustworthy and decentralized. Your data is your data alone and you deserve
to ..."
** Sounds great, hope its easy to implement, thanks.
*** I prefer rsync for such problems at the moment.
* Suggest you use FuseFS and sshfs---and on her MacOS she can use BREW to
install the FUSE .DMG package and use OSX shell to get to the filesystems
that you're willing to share (you mentioned you were worried about
providing too much).
** Not recommending SAMBA+CIFS protocol--especially right now, since there
is a vulnerability to be revealed on 12APR16
** Or you alone could use FuseFS and sshfs the dirs you want her to have
access to on the machine you both share/access (you seem to indicate she
has full and comfortable access to those dirs already--so installing the
FUSE .DMG package is probably overkill).
On Tue, Apr 5, 2016 at 8:45 AM, Nick Dokos <ndokos@gmail.com> wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
> > This isn't really a Org question at all, but you all are smart and
> > friendly people, and are likely to have run into this situation before.
> > So I'm trying here before I turn to StackOverflow!
> >
> > I have Org files in a git repo, synced across two Linux machines. At the
> > same time, I have a few directories on these computers that I sync with
> > colleagues, via Syncthing.
> >
> > One of these colleagues also uses Org, so instead of giving her access
> > to my Org git repo, which would be a bit too much exposure, I hardlink
> > some of the Org files into the Syncthing directories, and she accesses
> > them there. With auto-revert-mode turned on, it's not too bad.
> >
> > Except that the hardlinks keep breaking! There are so many different
> > systems interacting here that I have no idea where to even start
> > looking. She's on a Mac, not Linux, and uses a fairly recent version of
> > Emacs, plus Org from the ELPA package. She is *not* using git on her
> > machine, just Syncthing and Emacs.
> >
>
> How do the hardlinks break exactly?
>
> Hardlinks to a file are limited to the same filesystem: a file with
> inode number N has essentially two or more directory entries, with
> different names associated to the same inode number. Syncthing certainly
> cannot maintain that as it copies the file to the cloud and back, so
> there seem to be plenty of opportunities for breakage, but it's not
> clear which one(s) obtain.
>
> > I'm inclined to blame Syncthing, but I really don't know where to start
> > debugging. If any of you have any relevant experience, or any advice
> > about where to look, that would be much appreciated. Otherwise, please
> > excuse the off-topic post...
> >
>
> --
> Nick
>
>
>
[-- Attachment #2: Type: text/html, Size: 4271 bytes --]
next prev parent reply other threads:[~2016-04-05 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 6:34 [OT] Git plus Syncthing: breaking hard links Eric Abrahamsen
2016-04-05 7:58 ` Eric S Fraga
2016-04-05 8:04 ` Eric Abrahamsen
2016-04-05 12:45 ` Nick Dokos
2016-04-05 23:29 ` briangpowell . [this message]
2016-04-05 22:53 ` Tim Howes
2016-04-06 6:41 ` Eric Abrahamsen
2016-04-06 23:38 ` Adam Porter
2016-04-06 23:47 ` Adam Porter
2016-04-07 0:48 ` Eric Abrahamsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFm0skFOxdN9O7p3BGQDexSNha+P33Ern3NtdFH_qOJePckp1w@mail.gmail.com \
--to=briangpowellms@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).