-
Notifications
You must be signed in to change notification settings - Fork 72
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
dirent to missing inode - inconsistency detected - emergency read only #727
Comments
to debug this, immediately after it occurs you'll want to search through the journal with a command like bcachefs list_journal -t inodes:0:<inode_nr> -t dirents: We need to find the last transaction that either deleted the inode or updated the dirent |
Thank you for the quick help, I couldnt get it to output anything without the -a flag, I hope its still usefull: sudo bcachefs list_journal -at inodes:0:939563958 -t dirents:318536:4303058608615172108:4294967259 /dev/disk/by-label/arch
|
Would you be willing to send me a metadata dump? Join the IRC channel and magic wormhole it to me |
Yes, I would absolutely be open to do that, but I don't quite know how IRC and magic wormhole work. To my understanding, I send you the wormhole passkey via IRC and you pull the file? |
If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. #727 Signed-off-by: Kent Overstreet <[email protected]>
If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. #727 Signed-off-by: Kent Overstreet <[email protected]>
[ Upstream commit 1600514 ] If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. #727 Signed-off-by: Kent Overstreet <[email protected]>
[ Upstream commit 1600514 ] If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
[ Upstream commit 1600514 ] If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
[ Upstream commit 1600514 ] If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
[ Upstream commit 1600514 ] If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
[ Upstream commit 1600514 ] If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]>
[ Upstream commit 1600514 ] If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]>
If a file is unlinked but still open, we don't want online fsck to delete it - or fun inconsistencies will happen. koverstreet/bcachefs#727 Signed-off-by: Kent Overstreet <[email protected]>
System
I am running arch linux with a slightly customized kernel (mostly just disabling stuff i dont need) (the specific commit is 296c871)
Problem
I can boot fine but shortly after booting i get the following errors and the system goes into read-only (info from dmesg) (there are actually a lot more of the same error, I omitted them for the sake of readability):
When I run fsck -y the errors come up and it seems as tough they are fixed afterwards (they dont come up when i run it again), but when I reboot the same issue comes up again. Here is the first fsck (again, some errors are omitted):
Device configuration
I have an ssd and an hdd, with the ssd being the foreground and promote target and the hdd being the background target. I have background compression enabled. Heres the show-super output:
The text was updated successfully, but these errors were encountered: