public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Johannes Thumshirn <Johannes.Thumshirn@wdc.com>
Cc: "dsterba@suse.cz" <dsterba@suse.cz>,
	Sven Oehme <oehmes@gmail.com>,
	Naohiro Aota <Naohiro.Aota@wdc.com>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	"linux-btrfs @ vger . kernel . org" <linux-btrfs@vger.kernel.org>
Subject: Re: Host managed SMR drive issue
Date: Mon, 11 Oct 2021 15:06:37 +0200	[thread overview]
Message-ID: <20211011130637.GG9286@twin.jikos.cz> (raw)
In-Reply-To: <PH0PR04MB7416D33F5C5D2C3954F65C4E9BB59@PH0PR04MB7416.namprd04.prod.outlook.com>

On Mon, Oct 11, 2021 at 10:28:38AM +0000, Johannes Thumshirn wrote:
> On 11/10/2021 12:23, David Sterba wrote:
> > On Mon, Oct 11, 2021 at 06:32:35AM +0000, Johannes Thumshirn wrote:
> >> [ +Cc linux-btrfs ]
> >>
> >> On 07/10/2021 14:18, Sven Oehme wrote:
> >>> Thu Oct  7 06:09:30 2021] ------------[ cut here ]------------
> >>>
> >>> [Thu Oct  7 06:09:30 2021] BTRFS: Transaction aborted (error -22)
> >>>
> >>> [Thu Oct  7 06:09:30 2021] WARNING: CPU: 8 PID: 73260 at fs/btrfs/ctree.c:491 
> >>> __btrfs_cow_block+0x3d8/0x5a0 [btrfs]
> >>>
> >>> [Thu Oct  7 06:09:30 2021] Modules linked in: vhost_vsock 
> >>> vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock xt_conntrack 
> >>> nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack 
> >>> nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user nft_counter rpcsec_gss_krb5 nfsv4 nfs 
> >>> fscache netfs xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge stp 
> >>> llc cuse overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc 
> >>> scsi_dh_alua intel_rapl_msr intel_rapl_common amd64_edac edac_mce_amd kvm_amd 
> >>> kvm rapl efi_pstore ipmi_ssif joydev input_leds ftdi_sio usbserial ccp k10temp 
> >>> acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler mac_hid sch_fq_codel nfsd 
> >>> auth_rpcgss nfs_acl lockd grace msr sunrpc ip_tables x_tables autofs4 btrfs 
> >>> blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy 
> >>> async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear 
> >>> ses enclosure hid_lenovo hid_generic usbhid hid ast drm_vram_helper 
> >>> drm_ttm_helper ttm crct10dif_pclmul drm_kms_helper
> >>>
> >>> [Thu Oct  7 06:09:30 2021]  crc32_pclmul syscopyarea ghash_clmulni_intel 
> >>> sysfillrect sysimgblt aesni_intel fb_sys_fops crypto_simd cec cryptd rc_core 
> >>> nvme mpt3sas ahci drm ixgbe raid_class libahci igb smartpqi nvme_core xhci_pci 
> >>> xfrm_algo scsi_transport_sas xhci_pci_renesas i2c_piix4 dca i2c_algo_bit mdio
> >>>
> >>> [Thu Oct  7 06:09:30 2021] CPU: 8 PID: 73260 Comm: kworker/u98:0 Not tainted 
> >>> 5.13.0-rc6-fix2 #3
> >>
> >> Hi sorry for the late reply, I've been to a conference.
> >>
> >> This is already fixed in current btrfs misc-next, but not sure if the fix is 
> >> already in Linus' tree.
> > 
> > Which fix is that please?
> > 
> 
> The series from 
> c4153d4049f2 ("btrfs: introduce btrfs_is_data_reloc_root")
> to 
> 98e467cfa9c2 ("btrfs: zoned: let the for_treelog test in the allocator stand out")
> 
> As far as I can see they're only in btrfs-misc-next as of now.
> 
> But I think the series is a bit too big in terms of code change to go into
> 5.15 this late in the cycle.

The changes are more or less contained under the zoned mode (allocator
or if (zoned)), but the whole patchset size is larger than I'd consider
appropriate for rc5 time. I'll read the report again and give it another
thought.

  reply	other threads:[~2021-10-11 13:07 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-24 18:25 Host managed SMR drive issue Sven Oehme
2021-09-26 23:19 ` Damien Le Moal
2021-09-27 17:28   ` Sven Oehme
2021-09-27 22:36     ` Sven Oehme
2021-09-27 22:38     ` Sven Oehme
2021-09-27 22:48       ` Damien Le Moal
2021-09-27 22:56         ` Sven Oehme
2021-09-27 23:01           ` Damien Le Moal
2021-09-27 23:17             ` Sven Oehme
2021-09-27 23:31               ` Damien Le Moal
2021-09-27 23:34                 ` Sven Oehme
2021-09-27 23:36                   ` Sven Oehme
2021-09-27 23:38                     ` Damien Le Moal
2021-09-27 23:51                       ` Sven Oehme
2021-09-28  7:10                     ` Naohiro Aota
2021-09-28 11:49                       ` Sven Oehme
2021-09-30  9:55                         ` Johannes Thumshirn
     [not found]                           ` <CALssuR1wcChWwLt1wVoxhf=ufWdKtBHa7FXn-m9mkJcpPGbfOg@mail.gmail.com>
     [not found]                             ` <PH0PR04MB7416408BFBD494211A4D86B69BAA9@PH0PR04MB7416.namprd04.prod.outlook.com>
     [not found]                               ` <CALssuR1JZqaBLf_aCMRLm683cww66wc_p+hgCpCENMiQkVoSRg@mail.gmail.com>
     [not found]                                 ` <20211006154828.bqiwik2b6jaqxcck@naota-xeon>
     [not found]                                   ` <CALssuR3UeNmx0PnwUT8ZR0bOd9iAGjvgmv9u8yfHDnfpChKb2w@mail.gmail.com>
     [not found]                                     ` <20211007032239.iwrtygcavadvvb62@naota-xeon>
     [not found]                                       ` <CH0PR14MB50764AC8659E9378C65D6DE8F4B19@CH0PR14MB5076.namprd14.prod.outlook.com>
2021-10-11  6:32                                         ` Johannes Thumshirn
2021-10-11 10:23                                           ` David Sterba
2021-10-11 10:28                                             ` Johannes Thumshirn
2021-10-11 13:06                                               ` David Sterba [this message]
2021-09-28  6:36                   ` Johannes Thumshirn
2021-09-29 10:29                     ` Johannes Thumshirn

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=20211011130637.GG9286@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=Naohiro.Aota@wdc.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=oehmes@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox