-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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 diff" is unable to determine path or stats for an object #948
Comments
The Arguably we should disable the |
This is actually on Linux 3.5.3, so I don't imagine it's running into the same issue you're thinking of. I often use |
That is surprising then. It would be helpful if you were able to |
Yes; this is the end portion where it fails on running
|
Here is a second report from quite a different system.
|
Same issue here after a selinux relabel. Linux xeon2.home 3.14.4-200.fc20.x86_64 #1 SMP Tue May 13 13:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux execve("/sbin/zfs", ["zfs", "diff", "tank/oldraid@zfs-auto-snap_hourl"...], [/* 18 vars _/]) = 0 |
@behlendorf Why is this marked 'Documentation"? |
Changed to bug. When I originally categorized this issue I thought @chungy was using a kernel which didn't support the .zfs snapshot support. That appears to not be the case. Has anyone tried to reproduce this in the latest code? |
It's been over a year since I've had the system this bug was even an issue on. I can't reproduce it anywhere anymore, but assuming others can, the bug may as well remain open. |
Not sure it is completely fixed. I just had a chance to run another test - changing the SELinux context for a couple files and running a zfs diff. Now it doesn't complain -- but it doesn't show a difference in the file system either. Steps to reproduce: [root@xeon2 git]# ll -Z [root@xeon2 git]# chcon -R -t samba_share_t * [root@xeon2 git]# ll -Z (The snapshot was taken before the chcon) |
@pdemarino It sounds like we have addressed the crash but there's another open issue, #2081, regarding changes not appearing in |
I'm closing this issue out. The crash was addressed but there's clearly still an issue here which need to be fixed in the context of #2081. |
If you create a ciphered dataset with 'dnodesize=auto', the result of the command 'zfs diff' is quite wrong after any update of the dataset . |
@Bernard-Limogne the issue you're describing sounds like the issue addressed by #9343. The fix for this is queued up for 0.8.3. |
…ration fails assertion (openzfs#948)
I have a filesystem I'm using to host a CentOS 5 container within, but when I try to use
zfs diff
I get an error; I have performed azpool scrub
that returned precisely zero errors in the pool, but it did not resolve this situation. No messages appear in dmesg about it, either.Example run:
Sorry for the quite possible lack of information to reproduce it (short of myself running it), but I'll be happy to respond with more info if I'm asked to (and how).
The text was updated successfully, but these errors were encountered: