-
Notifications
You must be signed in to change notification settings - Fork 39
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
Config is un use #21
Comments
I always get this issue now. I am not sure if it appears for the / root or /home config. It seems the / root is transmitted (it takes time) and then when it tried to load the /home settings it fails:
The message it a btrfs message. I did a reboot and it does not help. |
It's a snapper message and it looks like its with the root configuration. What's the output of |
|
Are you sure that |
I have no idea... |
I think you are using a setup with |
Yes it is:
Also it worked before. I did not change anything in the setup. But snapper updated to 0.4.1. Maybe that is the issue? |
This is the problem:
|
Interesting. See this openSUSE thread. It might give you some ideas for troubleshooting, but I don't see a solution from it. |
Closing as a snapper issue. |
This only seem to happen with the root config:
|
I am not sure why this happens. Snapper list gives me those entries:
I think moved the data a bit. The first mountpoint was somehwere at
/run/media/name
and now ismnt2
. Before the folder on the partition wastest
and now is the root (i moved the data with mv).This might have caused trouble:
The text was updated successfully, but these errors were encountered: