Skip to content
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

ZFS destroyed snapshots still (sort of) linger and numerous ZFS crashes #17035

Open
summerowls0521 opened this issue Feb 7, 2025 · 0 comments
Labels
Type: Defect Incorrect behavior (e.g. crash, hang)

Comments

@summerowls0521
Copy link

summerowls0521 commented Feb 7, 2025

System information

Type Version/Name
Distribution Name Ubuntu
Distribution Version 24.10
Kernel Version 6.11.0-14-generic
Architecture x86_64
OpenZFS Version zfs-2.2.6-1ubuntu1

Describe the problem you're observing

I noticed after I made snapshots named "borg" on all mounted systems (except /var/tmp), took a backup of them then destroyed the snapshots, when I went to take a backup again borg complained that the inode had changed during backup and was a race condition for every single snapshot. Further, when I deleted all the snapshots again, /.zfs/snapshot/borg still exists as an empty directory. Rebooting seems to solve the issue, but when I had a quick look at my syslog to see if there was anything in there about this:

$ grep RIP /var/log/syslog | grep zfs | wc -l
103

The dates are spread out though the last one does look about the time I did the last backup. I'm not sure how much data to supply as there is 103 of those, do you want all of them? I'll update this post with the data you require.

Describe how to reproduce the problem

You could try creating and deleting multiple snapshots at once on a similar system with the same name. I have zfs encryption enabled too.

Include any warning/errors/backtraces from the system logs

Not sure how much data you need here or how to obtain it, I came up with this:

sudo dmesg | awk '/RIP.*zfs/{p=1;print;next} p&&/.*end trace/{print;p=0};p' | wc -l
533

Would you like me to post the output of that awk command? All of it or just some of it? Anything else, do any actions, etc, let me know what to do/post and I'll check back here tomorrow.

@summerowls0521 summerowls0521 added the Type: Defect Incorrect behavior (e.g. crash, hang) label Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Defect Incorrect behavior (e.g. crash, hang)
Projects
None yet
Development

No branches or pull requests

1 participant