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.

Sign up for GitHub

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

Jump to bottom

missing subvolume read only #725

Open
zcyc opened this issue Aug 16, 2024 · 6 comments
Open

missing subvolume read only #725

zcyc opened this issue Aug 16, 2024 · 6 comments

Comments

@zcyc
Copy link

zcyc commented Aug 16, 2024 •
edited
Loading

Hi.

I am using bcachefs to mount AWS cloud disk to a server, and then accessing bcachefs in a container via NFS. When I run scripts, bcachefs goes into read-only mode.

The script performs fork, pip install, and delete, operations serially, with a concurrency of 3.

dmegs:

bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3624:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3624:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3624:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3624:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3617:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3617:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3617:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3617:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3610:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3610:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3610:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3610:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3602:1073743893: ENOENT_inode
bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 3602:1073743893: ENOENT_inode

journal:

bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): inconsistency detected - emergency read only
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_delete_dead_snapshots(): error deleting keys from dying snapshots erofs_trans_commit
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_delete_dead_snapshots(): error erofs_trans_commit
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
bcachefs kernel: bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 3601
@SunrhLeo
Copy link

same problem in read mode

@koverstreet
Copy link
Owner

Need some info about what you were doing - creating subvolumes, creating snapshots, deleting subvolumes?

@zcyc
Copy link
Author

zcyc commented Aug 21, 2024 •
edited
Loading

Need some info about what you were doing - creating subvolumes, creating snapshots, deleting subvolumes?

I execute swebench using docker, i create a snapshot before work, when the test is finished clean the environment, delete the subvolume

dmegs:

[   39.009776] RDX: 0000000000000001 RSI: 0000000000000001 RDI: ffff9f6f4305b850
[   39.013163] RBP: ffff9f6f4305b850 R08: ffffb108c1d3ba68 R09: ffffffff99e4a4c8
[   39.016542] R10: ffff9f70631cb0a0 R11: 0000000000000000 R12: ffff9f6f48303f38
[   39.019873] R13: ffff9f710ad58000 R14: ffffb108c1d3bac8 R15: 0000000000000001
[   39.023300] FS:  0000000000000000(0000) GS:ffff9f7252b00000(0000) knlGS:0000000000000000
[   39.028357] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   39.031334] CR2: 00007ffceb691fb8 CR3: 000000010f58e002 CR4: 00000000007706f0
[   39.034646] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[   39.037976] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[   39.041291] PKRU: 55555554
[   39.043488] Call Trace:
[   39.045586]  <TASK>
[   39.047596]  ? __warn+0x80/0x120
[   39.049886]  ? discard_new_inode+0x5c/0x60
[   39.052416]  ? report_bug+0x164/0x190
[   39.054836]  ? handle_bug+0x3c/0x80
[   39.057201]  ? exc_invalid_op+0x17/0x70
[   39.059691]  ? asm_exc_invalid_op+0x1a/0x20
[   39.062222]  ? discard_new_inode+0x5c/0x60
[   39.064761]  ? discard_new_inode+0x1d/0x60
[   39.067310]  bch2_inode_insert+0x16a/0x180 [bcachefs]
[   39.070147]  ? bch2_inode_update_after_write+0x79/0x180 [bcachefs]
[   39.073255]  bch2_vfs_inode_get+0x1be/0x240 [bcachefs]
[   39.076186]  bch2_fh_to_dentry+0x38/0x70 [bcachefs]
[   39.079006]  ? __pfx_nfsd_acceptable+0x10/0x10 [nfsd]
[   39.081846]  exportfs_decode_fh_raw+0x78/0x300
[   39.084520]  fh_verify+0x5a6/0x780 [nfsd]
[   39.087080]  nfsd4_proc_compound+0x34b/0x670 [nfsd]
[   39.089834]  nfsd_dispatch+0xd8/0x210 [nfsd]
[   39.092621]  svc_process_common+0x4df/0x710 [sunrpc]
[   39.095451]  ? __pfx_nfsd_dispatch+0x10/0x10 [nfsd]
[   39.098232]  svc_process+0x131/0x180 [sunrpc]
[   39.100891]  svc_recv+0x83d/0xa10 [sunrpc]
[   39.103470]  ? __pfx_nfsd+0x10/0x10 [nfsd]
[   39.106050]  nfsd+0x87/0xf0 [nfsd]
[   39.108459]  kthread+0xd2/0x100
[   39.110819]  ? __pfx_kthread+0x10/0x10
[   39.113322]  ret_from_fork+0x34/0x50
[   39.115732]  ? __pfx_kthread+0x10/0x10
[   39.118206]  ret_from_fork_asm+0x1a/0x30
[   39.120699]  </TASK>
[   39.122743] ---[ end trace 0000000000000000 ]---
[   45.639570] NFSD: Using nfsdcld client tracking operations.
[   45.642548] NFSD: starting 90-second grace period (net f0000000)
[ 4955.774880] INFO: task kworker/6:0:36089 blocked for more than 120 seconds.
[ 4955.778360]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 4955.783289] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 4955.788167] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 4955.793438] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 4955.798638] Call Trace:
[ 4955.800852]  <TASK>
[ 4955.802903]  __schedule+0x3eb/0xb40
[ 4955.805276]  schedule+0x27/0xf0
[ 4955.807578]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 4955.810653]  ? __pfx_wake_bit_function+0x10/0x10
[ 4955.813311]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 4955.818109]  process_one_work+0x17c/0x390
[ 4955.820629]  worker_thread+0x265/0x380
[ 4955.823106]  ? __pfx_worker_thread+0x10/0x10
[ 4955.825681]  kthread+0xd2/0x100
[ 4955.827985]  ? __pfx_kthread+0x10/0x10
[ 4955.830439]  ret_from_fork+0x34/0x50
[ 4955.832858]  ? __pfx_kthread+0x10/0x10
[ 4955.835305]  ret_from_fork_asm+0x1a/0x30
[ 4955.837792]  </TASK>
[ 5076.606330] INFO: task kworker/6:0:36089 blocked for more than 241 seconds.
[ 5076.609717]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5076.614602] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5076.619494] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5076.624733] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5076.629980] Call Trace:
[ 5076.632070]  <TASK>
[ 5076.634096]  __schedule+0x3eb/0xb40
[ 5076.636454]  schedule+0x27/0xf0
[ 5076.638740]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5076.641792]  ? __pfx_wake_bit_function+0x10/0x10
[ 5076.644430]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5076.649215]  process_one_work+0x17c/0x390
[ 5076.651719]  worker_thread+0x265/0x380
[ 5076.654176]  ? __pfx_worker_thread+0x10/0x10
[ 5076.656741]  kthread+0xd2/0x100
[ 5076.659032]  ? __pfx_kthread+0x10/0x10
[ 5076.661658]  ret_from_fork+0x34/0x50
[ 5076.664088]  ? __pfx_kthread+0x10/0x10
[ 5076.666548]  ret_from_fork_asm+0x1a/0x30
[ 5076.669021]  </TASK>
[ 5197.437811] INFO: task kworker/6:0:36089 blocked for more than 362 seconds.
[ 5197.441141]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5197.446031] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5197.450895] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5197.456166] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5197.461366] Call Trace:
[ 5197.463502]  <TASK>
[ 5197.465541]  __schedule+0x3eb/0xb40
[ 5197.467934]  schedule+0x27/0xf0
[ 5197.470262]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5197.473365]  ? __pfx_wake_bit_function+0x10/0x10
[ 5197.476051]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5197.480837]  process_one_work+0x17c/0x390
[ 5197.483358]  worker_thread+0x265/0x380
[ 5197.485816]  ? __pfx_worker_thread+0x10/0x10
[ 5197.488430]  kthread+0xd2/0x100
[ 5197.490711]  ? __pfx_kthread+0x10/0x10
[ 5197.493150]  ret_from_fork+0x34/0x50
[ 5197.495604]  ? __pfx_kthread+0x10/0x10
[ 5197.498087]  ret_from_fork_asm+0x1a/0x30
[ 5197.500586]  </TASK>
[ 5318.269277] INFO: task kworker/6:0:36089 blocked for more than 483 seconds.
[ 5318.272659]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5318.277592] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5318.282491] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5318.287730] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5318.292971] Call Trace:
[ 5318.295072]  <TASK>
[ 5318.297072]  __schedule+0x3eb/0xb40
[ 5318.299483]  schedule+0x27/0xf0
[ 5318.301793]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5318.304896]  ? __pfx_wake_bit_function+0x10/0x10
[ 5318.307574]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5318.312428]  process_one_work+0x17c/0x390
[ 5318.315006]  worker_thread+0x265/0x380
[ 5318.317573]  ? __pfx_worker_thread+0x10/0x10
[ 5318.320201]  kthread+0xd2/0x100
[ 5318.322566]  ? __pfx_kthread+0x10/0x10
[ 5318.325044]  ret_from_fork+0x34/0x50
[ 5318.327462]  ? __pfx_kthread+0x10/0x10
[ 5318.329891]  ret_from_fork_asm+0x1a/0x30
[ 5318.332467]  </TASK>
[ 5439.100769] INFO: task kworker/6:0:36089 blocked for more than 604 seconds.
[ 5439.104085]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5439.108936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5439.113781] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5439.119035] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5439.124318] Call Trace:
[ 5439.126425]  <TASK>
[ 5439.128445]  __schedule+0x3eb/0xb40
[ 5439.130801]  schedule+0x27/0xf0
[ 5439.133075]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5439.136111]  ? __pfx_wake_bit_function+0x10/0x10
[ 5439.138756]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5439.143508]  process_one_work+0x17c/0x390
[ 5439.145998]  worker_thread+0x265/0x380
[ 5439.148408]  ? __pfx_worker_thread+0x10/0x10
[ 5439.150967]  kthread+0xd2/0x100
[ 5439.153217]  ? __pfx_kthread+0x10/0x10
[ 5439.155632]  ret_from_fork+0x34/0x50
[ 5439.158006]  ? __pfx_kthread+0x10/0x10
[ 5439.160416]  ret_from_fork_asm+0x1a/0x30
[ 5439.162871]  </TASK>
[ 5559.932297] INFO: task kworker/6:0:36089 blocked for more than 724 seconds.
[ 5559.935609]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5559.940444] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5559.997128] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5560.002348] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5560.007549] Call Trace:
[ 5560.009674]  <TASK>
[ 5560.011656]  __schedule+0x3eb/0xb40
[ 5560.014037]  schedule+0x27/0xf0
[ 5560.016320]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5560.019382]  ? __pfx_wake_bit_function+0x10/0x10
[ 5560.022024]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5560.026779]  process_one_work+0x17c/0x390
[ 5560.029271]  worker_thread+0x265/0x380
[ 5560.031695]  ? __pfx_worker_thread+0x10/0x10
[ 5560.034282]  kthread+0xd2/0x100
[ 5560.036556]  ? __pfx_kthread+0x10/0x10
[ 5560.039034]  ret_from_fork+0x34/0x50
[ 5560.041433]  ? __pfx_kthread+0x10/0x10
[ 5560.043873]  ret_from_fork_asm+0x1a/0x30
[ 5560.046350]  </TASK>
[ 5680.763821] INFO: task kworker/6:0:36089 blocked for more than 845 seconds.
[ 5680.767145]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5680.771995] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5680.776836] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5680.782079] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5680.787271] Call Trace:
[ 5680.789382]  <TASK>
[ 5680.791401]  __schedule+0x3eb/0xb40
[ 5680.793772]  schedule+0x27/0xf0
[ 5680.796061]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5680.799119]  ? __pfx_wake_bit_function+0x10/0x10
[ 5680.801791]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5680.806535]  process_one_work+0x17c/0x390
[ 5680.809030]  worker_thread+0x265/0x380
[ 5680.811474]  ? __pfx_worker_thread+0x10/0x10
[ 5680.814056]  kthread+0xd2/0x100
[ 5680.816352]  ? __pfx_kthread+0x10/0x10
[ 5680.818785]  ret_from_fork+0x34/0x50
[ 5680.821174]  ? __pfx_kthread+0x10/0x10
[ 5680.823613]  ret_from_fork_asm+0x1a/0x30
[ 5680.826130]  </TASK>
[ 5801.595348] INFO: task kworker/6:0:36089 blocked for more than 966 seconds.
[ 5801.598652]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5801.603479] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5801.608291] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5801.613522] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5801.618726] Call Trace:
[ 5801.620837]  <TASK>
[ 5801.622853]  __schedule+0x3eb/0xb40
[ 5801.625215]  schedule+0x27/0xf0
[ 5801.627519]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5801.630621]  ? __pfx_wake_bit_function+0x10/0x10
[ 5801.633371]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5801.638270]  process_one_work+0x17c/0x390
[ 5801.640796]  worker_thread+0x265/0x380
[ 5801.643237]  ? __pfx_worker_thread+0x10/0x10
[ 5801.645856]  kthread+0xd2/0x100
[ 5801.648153]  ? __pfx_kthread+0x10/0x10
[ 5801.650597]  ret_from_fork+0x34/0x50
[ 5801.653025]  ? __pfx_kthread+0x10/0x10
[ 5801.655471]  ret_from_fork_asm+0x1a/0x30
[ 5801.657958]  </TASK>
[ 5922.426972] INFO: task kworker/6:0:36089 blocked for more than 1087 seconds.
[ 5922.430340]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 5922.435178] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 5922.440018] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 5922.445242] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 5922.450421] Call Trace:
[ 5922.452500]  <TASK>
[ 5922.454569]  __schedule+0x3eb/0xb40
[ 5922.456968]  schedule+0x27/0xf0
[ 5922.459275]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 5922.462366]  ? __pfx_wake_bit_function+0x10/0x10
[ 5922.465031]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 5922.469815]  process_one_work+0x17c/0x390
[ 5922.472342]  worker_thread+0x265/0x380
[ 5922.474770]  ? __pfx_worker_thread+0x10/0x10
[ 5922.477410]  kthread+0xd2/0x100
[ 5922.479699]  ? __pfx_kthread+0x10/0x10
[ 5922.482148]  ret_from_fork+0x34/0x50
[ 5922.484549]  ? __pfx_kthread+0x10/0x10
[ 5922.486995]  ret_from_fork_asm+0x1a/0x30
[ 5922.489501]  </TASK>
[ 6043.258413] INFO: task kworker/6:0:36089 blocked for more than 1208 seconds.
[ 6043.261754]       Tainted: G        W          6.10.4-cloud-amd64 #1 Debian 6.10.4-1
[ 6043.266555] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 6043.271413] task:kworker/6:0     state:D stack:0     pid:36089 tgid:36089 ppid:2      flags:0x00004000
[ 6043.276645] Workqueue: bcachefs_write_ref bch2_subvolume_wait_for_pagecache_and_delete [bcachefs]
[ 6043.281850] Call Trace:
[ 6043.283965]  <TASK>
[ 6043.285989]  __schedule+0x3eb/0xb40
[ 6043.288359]  schedule+0x27/0xf0
[ 6043.290644]  bch2_evict_subvolume_inodes+0x25b/0x2e0 [bcachefs]
[ 6043.293697]  ? __pfx_wake_bit_function+0x10/0x10
[ 6043.296371]  bch2_subvolume_wait_for_pagecache_and_delete+0xb4/0x270 [bcachefs]
[ 6043.301139]  process_one_work+0x17c/0x390
[ 6043.303647]  worker_thread+0x265/0x380
[ 6043.306092]  ? __pfx_worker_thread+0x10/0x10
[ 6043.308662]  kthread+0xd2/0x100
[ 6043.310949]  ? __pfx_kthread+0x10/0x10
[ 6043.313398]  ret_from_fork+0x34/0x50
[ 6043.315791]  ? __pfx_kthread+0x10/0x10
[ 6043.318226]  ret_from_fork_asm+0x1a/0x30
[ 6043.320705]  </TASK>
[ 6043.322784] Future hung task reports are suppressed, see sysctl kernel.hung_task_warnings
[ 7001.725879] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 4598:295082: ENOENT_inode
[ 7001.725897] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 4598:295082: ENOENT_inode
[ 7069.116790] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_inode_peek(): error looking up inum 4598:537467832: ENOENT_inode
[ 7329.344613] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 5358
[ 7329.344620] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 5358
[ 7329.345253] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): inconsistency detected - emergency read only at journal seq 8928290
[ 7329.360326] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): bch2_subvolume_wait_for_pagecache_and_delete(): error deleting subvolume 5378 erofs_journal_err
[ 7329.360328] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 5358
[ 7329.360562] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 5358
[ 7329.377160] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 5358
[ 7329.382326] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): missing subvolume 5358
[ 7329.388238] bcachefs (5a05af34-eced-4373-a14d-4e209a12b1d0): unshutdown complete, journal seq 8928290

@windy
Copy link

windy commented Sep 12, 2024

Hi Author, thanks for your hard work. I'd like to know if there has been any progress on this issue. I'm experiencing a similar problem. I just switched from btrfs to bcachefs, performed similar operations, created snapshots, conducted some file I/O, and deleted files. After doing this multiple times, there's a chance that this issue will occur.

@zcyc zcyc changed the title Read only and missing subvolume Read only by missing subvolume and recover error Dec 6, 2024
@koverstreet
Copy link
Owner

Change your errors= parameter to fix_simple

@zcyc
Copy link
Author

zcyc commented Dec 11, 2024 •
edited
Loading

I think that problem I encountered on 6th December is different from the one on 16th August. I opened a new issue to track that problem. All info has moved to #798

@zcyc zcyc changed the title Read only by missing subvolume and recover error Read only and missing subvolume Dec 11, 2024
@zcyc zcyc changed the title Read only and missing subvolume missing subvolume read only Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@windy @koverstreet @zcyc @SunrhLeo