All of lore.kernel.org
 help / color / mirror / Atom feed
From: Asif Youssuff <yoasif@gmail.com>
To: Qu Wenruo <wqu@suse.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Filesystem goes readonly soon after mount, cannot free space or rebalance
Date: Mon, 21 Jun 2021 20:55:09 -0400	[thread overview]
Message-ID: <CAHw5_hmUda4hO7=sNQNWtSxyyzm7i9MU50nsQkrZRw7fsAW3NA@mail.gmail.com> (raw)
In-Reply-To: <CAHw5_hkUhV8OvrdZOWTnQU_ksh3z94+ivskyw_h069HwYhvNXg@mail.gmail.com>

To be clear, it was the last snapshot on an infrequently updated
subvolume, likely with no changes since the prior snapshot to the one
deleted.

On Mon, Jun 21, 2021 at 8:50 PM Asif Youssuff <yoasif@gmail.com> wrote:
>
> I tried removing a single snapshot from a subvolume with rarely
> updated data (likely no changes at all to that subvolume between
> snapshots), and I was unable to successfully sync the filesystem
> before it went readonly.
>
> On Mon, Jun 21, 2021 at 8:26 PM Qu Wenruo <wqu@suse.com> wrote:
> >
> >
> >
> > On 2021/6/22 上午8:12, Asif Youssuff wrote:
> > > On Mon, Jun 21, 2021 at 7:36 PM Qu Wenruo <quwenruo.btrfs@gmx.com> wrote:
> > >
> > >>> I have tried removing snapshots, but the disk continues to go ro -
> > >>> after remount, the subvolumes are still there. Is there a way to force
> > >>> a sync of the subvolume removal before the fs goes ro?
> > >>
> > >> Maybe you can try "btrfs fi sync" before remount?
> > >
> > > Tried deleting a bunch of snapshots and immediately did a btrfs fi
> > > sync - still forced ro pretty quickly:
> >
> > So that's the worst case, metadata already exhausted.
> >
> > Have you tried to just delete one small subvolume and then fi sync?
> >
> > It's possible that too many pending subvolume deletion can cause too
> > much metadata space usage.
> >
> > Thus if you do it one by one, there may be a chance to commit successfully.
> >
> > Thanks,
> > Qu
> > >
> > > [ 1810.858326] ------------[ cut here ]------------
> > > [ 1810.858334] BTRFS: Transaction aborted (error -28)
> > > [ 1810.858384] BTRFS: error (device sdf) in __btrfs_free_extent:3216:
> > > errno=-28 No space left
> > > [ 1810.858493] BTRFS info (device sdf): forced readonly
> > > [ 1810.858405] WARNING: CPU: 5 PID: 10137 at
> > > fs/btrfs/extent-tree.c:3216 __btrfs_free_extent+0x7be/0x920 [btrfs]
> > > [ 1810.858500] BTRFS: error (device sdf) in
> > > btrfs_run_delayed_refs:2163: errno=-28 No space left
> > > [ 1810.858635] Modules linked in: veth xt_nat nf_conntrack_netlink
> > > nfnetlink xfrm_user xfrm_algo xt_addrtype br_netfilter xt_CHECKSUM
> > > iptable_mangle xt_MASQUERADE iptable_nat nf_nat xt_conntrack
> > > nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ipt_REJECT nf_reject_ipv4
> > > xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter
> > > ip6_tables iptable_filter bpfilter ppdev parport_pc parport
> > > vmw_vsock_vmci_transport vsock vmw_vmci overlay bluetooth ecdh_generic
> > > ecc msr binfmt_misc input_leds joydev ipmi_ssif dm_crypt
> > > intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp
> > > coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul
> > > ghash_clmulni_intel aesni_intel crypto_simd cryptd rapl intel_cstate
> > > intel_pch_thermal lpc_ich mei_me mei acpi_ipmi ipmi_si ipmi_devintf
> > > ipmi_msghandler ie31200_edac mac_hid acpi_pad sch_fq_codel ib_iser
> > > rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi
> > > scsi_transport_iscsi ip_tables x_tables autofs4 btrfs blake2b_generic
> > > raid10 raid456
> > > [ 1810.858782]  async_raid6_recov async_memcpy async_pq async_xor
> > > async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear
> > > hid_generic usbhid hid uas usb_storage ast drm_vram_helper
> > > drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect sysimgblt
> > > fb_sys_fops cec mpt3sas rc_core raid_class drm igb ahci xhci_pci dca
> > > e1000e libahci i2c_algo_bit scsi_transport_sas xhci_pci_renesas video
> > > [ 1810.858857] CPU: 5 PID: 10137 Comm: btrfs-transacti Tainted: G
> > >    W         5.12.12-051212-generic #202106180931
> > > [ 1810.858865] Hardware name: Supermicro X10SLM-F/X10SLM-F, BIOS 3.0 04/24/2015
> > > [ 1810.858868] RIP: 0010:__btrfs_free_extent+0x7be/0x920 [btrfs]
> > > [ 1810.858973] Code: 8b 40 50 f0 48 0f ba a8 48 0a 00 00 03 72 1d 8b
> > > 45 84 83 f8 fb 74 32 83 f8 e2 74 2d 89 c6 48 c7 c7 98 0c 75 c0 e8 15
> > > e1 f6 f7 <0f> 0b 8b 4d 84 48 8b 7d 90 ba 90 0c 00 00 48 c7 c6 c0 52 74
> > > c0 e8
> > > [ 1810.858980] RSP: 0018:ffffab4702a43c00 EFLAGS: 00010286
> > > [ 1810.858986] RAX: 0000000000000000 RBX: 0000000000000030 RCX: ffff95e57fd585c8
> > > [ 1810.858991] RDX: 00000000ffffffd8 RSI: 0000000000000027 RDI: ffff95e57fd585c0
> > > [ 1810.858995] RBP: ffffab4702a43ca8 R08: 0000000000000000 R09: ffffab4702a439e0
> > > [ 1810.858998] R10: ffffab4702a439d8 R11: ffffffffb99542e8 R12: 000157fe74a6e000
> > > [ 1810.859002] R13: 0000000000000515 R14: ffff95de8a0941c0 R15: ffff95dfaa212200
> > > [ 1810.859007] FS:  0000000000000000(0000) GS:ffff95e57fd40000(0000)
> > > knlGS:0000000000000000
> > > [ 1810.859012] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> > > [ 1810.859016] CR2: 00007fd6fc652718 CR3: 0000000278610004 CR4: 00000000001706e0
> > > [ 1810.859022] Call Trace:
> > > [ 1810.859031]  run_delayed_data_ref+0x96/0x160 [btrfs]
> > > [ 1810.859130]  btrfs_run_delayed_refs_for_head+0x184/0x480 [btrfs]
> > > [ 1810.859225]  __btrfs_run_delayed_refs+0x8c/0x1d0 [btrfs]
> > > [ 1810.859320]  btrfs_run_delayed_refs+0x73/0x200 [btrfs]
> > > [ 1810.859474]  btrfs_commit_transaction+0x68/0xa20 [btrfs]
> > > [ 1810.859633]  ? start_transaction+0xd5/0x590 [btrfs]
> > > [ 1810.859783]  ? __next_timer_interrupt+0xd0/0x110
> > > [ 1810.859800]  transaction_kthread+0x138/0x1b0 [btrfs]
> > > [ 1810.859905]  kthread+0x12f/0x150
> > > [ 1810.859916]  ? btrfs_cleanup_transaction.isra.0+0x290/0x290 [btrfs]
> > > [ 1810.860020]  ? __kthread_bind_mask+0x70/0x70
> > > [ 1810.860031]  ret_from_fork+0x22/0x30
> > > [ 1810.860045] ---[ end trace 64a07c4b91899089 ]---
> > > [ 1810.860052] BTRFS: error (device sdf) in __btrfs_free_extent:3216:
> > > errno=-28 No space left
> > > [ 1810.860172] BTRFS: error (device sdf) in
> > > btrfs_run_delayed_refs:2163: errno=-28 No space left
> > >
> > >
> > >
> >
>
>
> --
> Thanks,
> Asif



-- 
Thanks,
Asif

  reply	other threads:[~2021-06-22  0:55 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19  5:16 Filesystem goes readonly soon after mount, cannot free space or rebalance Asif Youssuff
2021-06-19 18:47 ` Chris Murphy
2021-06-20  9:11   ` Asif Youssuff
     [not found]   ` <ab0e8705-e18f-90eb-c42b-318c04a2101c@gmail.com>
2021-06-20 16:24     ` Chris Murphy
2021-06-20 16:49       ` Chris Murphy
2021-06-21  2:04       ` Asif Youssuff
2021-06-21  3:27         ` Chris Murphy
2021-06-21  6:53           ` Asif Youssuff
2021-06-21  7:42 ` Qu Wenruo
2021-06-21 23:14   ` Asif Youssuff
2021-06-21 23:36     ` Qu Wenruo
2021-06-22  0:12       ` Asif Youssuff
2021-06-22  0:25         ` Qu Wenruo
2021-06-22  0:50           ` Asif Youssuff
2021-06-22  0:55             ` Asif Youssuff [this message]
2021-06-22  3:15               ` Qu Wenruo
2021-06-22  4:54                 ` Asif Youssuff
2021-06-22  5:03                   ` Qu Wenruo
2021-06-22  6:37                     ` Asif Youssuff
2021-06-22 21:33                       ` Chris Murphy
2021-06-23  9:32                         ` Asif Youssuff
2021-06-23  9:37                           ` Qu Wenruo
2021-06-23  9:53                             ` Forza
2021-06-23 16:24                             ` Asif Youssuff
2021-06-23 16:29                               ` Martin Raiber
2021-07-27 21:58                               ` Asif Youssuff
2021-06-23  5:32 ` Zygo Blaxell
2021-06-23  6:08   ` Paul Jones
2021-06-23  9:22   ` Asif Youssuff

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHw5_hmUda4hO7=sNQNWtSxyyzm7i9MU50nsQkrZRw7fsAW3NA@mail.gmail.com' \
    --to=yoasif@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=quwenruo.btrfs@gmx.com \
    --cc=wqu@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.