We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It panics when perform prefetch command
prefetch
- 235 "\xE2\xE3\xB7席\xB7\xFB\xB3\xB5\xE2\xEF\xE2\u{2cf4}\xE2\xE7\xB7\xFE\xB7\xF4\xE2\xFC\xE2\xF5\xE2\xF6\xB7\xF6ӺӮӼ\xE2\xF8.regular" Inspecting Rafs :> prefetch Prefetched Files: 1 [2022-09-27 12:54:15.946612 +08:00] ERROR [/home/gechangwei/.cargo/registry/src/mirrors.sjtug.sjtu.edu.cn-4f7dbcce21e258a2/log-panics-2.1.0/src/lib.rs:130] thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Custom { kind: NotFound, error: "No such file or directory (os error 2): rafs/src/metadata/direct_v6.rs:820" }': rafs/src/metadata/direct_v6.rs:1163 0: backtrace::capture::Backtrace::create 1: backtrace::capture::Backtrace::new Aborted (core dumped)
The text was updated successfully, but these errors were encountered:
@YushuoEdge PTAL if have any chance :)
Sorry, something went wrong.
The root cause is that the regular file inode does not point to its parent dir. To fix this, must have a way similar to lookup
Successfully merging a pull request may close this issue.
It panics when perform
prefetch
commandThe text was updated successfully, but these errors were encountered: