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 diff showing impossible changes #17103

Open
eharris opened this issue Feb 28, 2025 · 0 comments
Open

zfs diff showing impossible changes #17103

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

Comments

@eharris
Copy link
Contributor

eharris commented Feb 28, 2025

System information

Type Version/Name
Distribution Name Debian
Distribution Version 12 (bookworm)
Kernel Version 6.1.0-30-amd64
Architecture amd64
OpenZFS Version zfs-2.2.7-1~bpo12+1

Describe the problem you're observing

I've come across an instance of zfs diff showing an impossible sequence of events, given the state of the starting snapshot.
It is reporting a directory as moved, and then later reporting files that moved from within the original directory location to within the new (moved) location. The files it is reporting as moved are within the directory before it is moved in the starting snapshot, and the directory they are shown as moved to doesn't exist before the directory is moved (that is, in the starting snapshot).

No matter what order these records are ordered in, they can't be reconciled. What it looks like is the file move records were somehow generated using source paths of the original directory location, but destination paths of the directory in its new location.

Heres the relevant zfs diff output:

1688418153.587271441    R       /       /home/test/zvib/z  /home/test/proj/vib/z
...
1688418130.251130632    R       F       /home/test/zvib/z/Sam.CSV      /home/test/proj/vib/z/Sam2.CSV
1688418135.107159926    R       F       /home/test/zvib/z/Sam.txt      /home/test/proj/vib/z/Sam2.txt

Describe how to reproduce the problem

No idea. But no relevant errors are being shown by the pool or in the kernel logs, and the pool is otherwise fine.

Include any warning/errors/backtraces from the system logs

@eharris eharris added the Type: Defect Incorrect behavior (e.g. crash, hang) label Feb 28, 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