-
Notifications
You must be signed in to change notification settings - Fork 308
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.
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
syncoid: getting "Too many levels of symbolic links" in snapshot dir on remote host #48
Comments
"too many levels of symlinks" strongly implies that the problem isn't To troubleshoot further, look at an ls -l of the parent directory
Should be followed with:
Also note that the .zfs/snapshots directory is basically a convenience
(Sent from my tablet - please blame any weird errors on autocorrect) On August 21, 2016 14:21:14 jonalbrecht [email protected] wrote:
|
Thanks for the quick reply.
This is from the remote host:
I saw this recent zfsonlinux issue. Maybe the cause of what I'm seeing? |
Possibly. Have you tried accessing the snapshot with mount or clone as I (Sent from my tablet - please blame any weird errors on autocorrect) On August 21, 2016 20:06:31 jonalbrecht [email protected] wrote:
|
Sorry for taking so long to reply.
It all looks good |
Going to close this here; it's not a bug in syncoid. Thanks for the report though. |
I don't think this is a problem with syncoid but I wanted to check if there is a problem either with what I'm doing or with zfs.
I'm on ubuntu 16.04 with the latest updates and I'm using syncoid from master as of Aug 8. After the first incremental syncoid I am getting "Too many levels of symbolic links" errors when trying to list the files in the remote snapshot dir.
Here are the commands I've run with robocat as the source host and roboduck as the remote backup host:
On some other zfs filesystems I've been testing with, I've seen the files on the remote filesystem disappear after the first incremental but I don't have a simple repro for that yet. The snapshot dir errors are the same in both cases. I'm guessing this is a problem with zfs but it would be great if someone could have a quick look in case I'm doing something wrong.
The text was updated successfully, but these errors were encountered: