Skip to content
This repository has been archived by the owner on Feb 12, 2019. It is now read-only.

Relative paths error on MacOS #1881

Open
joejacobs opened this issue Oct 30, 2018 · 2 comments
Open

Relative paths error on MacOS #1881

joejacobs opened this issue Oct 30, 2018 · 2 comments

Comments

@joejacobs
Copy link

joejacobs commented Oct 30, 2018

Running the following bash commands

cd /keybase/private/user
mkdir -p a/b/c
cd a
mv b ../
cd ../b
touch ../a/d.txt
mv c ../a/

should create the following files/dirs:

Dir  /keybase/private/user/a
Dir  /keybase/private/user/a/c
File /keybase/private/user/a/d.txt
Dir  /keybase/private/user/b

This works fine on my Linux machine. But when I run it on MacOS 10.13.6, it creates the following dirs instead:

Dir /keybase/private/user/a
Dir /keybase/private/user/a/a
Dir /keybase/private/user/b

And the touch command fails with the following error:

touch: ../a/d.txt: No such file or directory
@strib
Copy link
Contributor

strib commented Oct 30, 2018

Thanks for the succinct repro case, I confirmed it happens to me too. I'll open an internal ticket to track figuring this out, we'll get to it within a few days.

@strib
Copy link
Contributor

strib commented Nov 6, 2018

I think I tracked this down to an osxfuse bug, and I filed this issue: osxfuse/osxfuse#553.

There might be some strategies we can use in KBFS to get around this until it's fixed in osxfuse. I'll you posted.

strib added a commit that referenced this issue Nov 6, 2018
Otherwise, the kernel might still treat it as having the old parent
ID.

Issue: #1881
Issue: KBFS-3576
Issue: osxfuse/osxfuse#553
strib added a commit that referenced this issue Nov 6, 2018
Otherwise, the kernel might still treat it as having the old parent
ID.

This shouldn't mess up any kernel caching or libkbfs garbage
collection, since if the original node for the moved node is still in
use, bazil.org would hold a reference to it.

But it's definitely a little weird that the same node might have two
inodes pointing into it.  We should remove this once the osxfuse issue
is fixed.

Issue: #1881
Issue: KBFS-3576
Issue: osxfuse/osxfuse#553
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants