8000 Symbolic links · Issue #8 · Doloops/mcachefs · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Symbolic links #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
isarandi opened this issue Mar 11, 2019 · 3 comments
Open

Symbolic links #8

isarandi opened this issue Mar 11, 2019 · 3 comments

Comments

@isarandi
Copy link

I'm using mcachefs to cache sshfs. The sshfs option follow_symlinks enables me to traverse symlinks on the actual sshfs mount. However the mcachefs cached mount says "cannot read symbolic link h36m: Invalid argument".
@isarandi isarandi changed the title Sybolic links Symbolic links Mar 11, 2019
@hradec
Copy link
hradec commented Mar 29, 2019 •
edited
Loading

I had a problem related to symlinks, but when you mount using then.

for example, if you mount a backend filesystem mounted on /tmp/backend to /atomo, but /atomo is actually a symlink to /RAID/atomo.
mcachefs /tmp/backend /atomo

When I first did that, something weird happened, and mcachefs got into a weird never-ending loop which made my machine load average plumb to 9000 after a few minutes!

it was fixed by calling:
mcachefs /tmp/backed /RAID/atomo

using the actual path the /atomo symbolic link pointed to (/RAID/atomo) instead of the symlink.

not sure if there's something to do with your problem, but I thought it was a relevant piece of info anyways...

so... KIDS, never mount mcachefs to a symlink!!

@cde-jq cde-jq mentioned this issue Mar 29, 2019
Closed
@Doloops
Copy link
Owner
Doloops commented Apr 3, 2019

@isarandi Could you please share your usecase, more information on your symlink content ?

I assume that's an absolute symlink within the backend filesystem, or at least a relative one pointing outside of the scope of the backend filesystem.
This should imply mcachefs is able to transform the backend symlink to a locally-understandable symlink. Which it doesn't.

Otherwise, purely relative symlinks do work, if they are relative and inside of in the backend mount point.
For example, if I have a folder 'a' and a symlink 'b' pointing to 'a', this symlink will be displayed and resolved correctly on the local filesystem as well.

@isarandi
Copy link
Author
isarandi commented Apr 4, 2019 •
edited
Loading

On the remote machine the content is mounted via NFS from a third machine. The symlink was absolute I think (but I don't remember exactly), pointing back to a different directory of the same NFS mount. The NFS mount is mounted directly one level under the root.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hradec @Doloops @isarandi
0