-
Notifications
You must be signed in to change notification settings - Fork 50
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
zfssnap reports trying to delete pools #67
Comments
hi, I'm hitting this bug too, and it's not clear why. It's a scary error message, so can someone explain more what's happening .. Thanks! |
Execute this and post output: zfSnap -zpool28fix -n -d -p 'hourly-' -p 'daily-' -p 'weekly-' -p 'monthly-' -p 'reboot-' And then execute this and post output sh -x /usr/local/sbin/zfSnap -zpool28fix -n -d -p 'hourly-' -p 'daily-' -p 'weekly-' -p 'monthly-' -p 'reboot-' Note: I think you're missing -zpool28fix flag in daily_zfsnap_delete_flags. Not that it should cause this misbehavior, but still. |
@graudeejs .. The first command returns nothing .. The second one returns http://fpaste.org/250760/ Thanks for helping! |
Weird, 1st command should return list of zfs commands
|
I ran it like 5 times .. nothing at all |
Try latest version from legacy branch, I added few lines in order to see what exactly caused an error. Try with this one: https://raw.githubusercontent.com/zfsnap/zfsnap/17b1f389365a57f04448c0800cde327d47baa02e/zfSnap.sh run: ./zfSnap.sh -zpool28fix -v -d -p 'hourly-' -p 'daily-' -p 'weekly-' -p 'monthly-' -p 'reboot-' This will try to delete snapshot, and If you get that error, we should see why exactly. |
Btw, @kim0, are you using FreeBSD as well? |
@graudeejs Yes I'm on freebsd 10.1 ... I'll try that version next |
@kim0, Any news? |
Closing for now, since no new input has been provided. |
Here is the output that gets mailed to me:
And here is my config:
As stated in the email output, it told me to report the issue, so here I am :) I am running FreeBSD 10.1 with its associated ZFS version.
The text was updated successfully, but these errors were encountered: