-
Notifications
You must be signed in to change notification settings - Fork 57
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
Infinite loop in trying to get started #212
Comments
Interesting. |
suggested way to do that? |
do you want to add an echo somewhere in the script? |
two ways to approach this: a) put "set -x" as the second line in the script, to enable debug mode or b) zfs get all rpool/ROOT/pve-1 |grep zrep |
|
|
so it seems like the zrep clear, is leaving behind zrep:dest-fs property? that seems odd. |
I run as root. |
interestingly, in some environments, that isnt enough.
the main point here, is that for everyone else "zrep clear" works, but for
you, in your environment.it does not.
So, you probably need to examine specifically why that is.
Given that you are running zsh instead of bash, like one should with the
latest version of zrep, you may be best off posting in a forum focused on
your specific OS?
Digging deeper, would require you setting -x, then running the zrep clear
to notice exactly what it is calling, then running the calls yourself to
see if it actually works when you run the command directly, vs through zrep.
Im guessing it will work.
If so, then you need to fix the specific runtime environment that you are
kicking off zrep with.
…On Sun, Dec 15, 2024 at 2:44 PM Steve Kirsch ***@***.***> wrote:
I run as root.
—
Reply to this email directly, view it on GitHub
<#212 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANEV6KBAGLMXWOEOC3FFTL2FYA4RAVCNFSM6AAAAABTUNXSRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBUGE2DOMJUG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Groundhog day :)
The text was updated successfully, but these errors were encountered: