From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f44.google.com (mail-wr1-f44.google.com [209.85.221.44]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 21ECF2AE72 for ; Tue, 29 Apr 2025 05:32:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.44 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1745904759; cv=none; b=dbbp3pIaYaGmllpMhNtLVjKOyKaoJc7CSngA5qH5fnchOPRIAfOpX1ISUMMMDgNroNgFuZWFYUqoDDfdtFVXZqbmMuvUD8YVQi7pVGQ3t6mhJpFf7Vr9olJky+69VlfT2SIIjgm/G+/9KSg09quQoxBqIhRDgew9CVQm9QfsxG4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1745904759; c=relaxed/simple; bh=gsnmZ9EjdzQp/dlw+a9bSAOuHyntfmlGQh8sOiwDOuA=; h=Message-ID:Date:MIME-Version:Subject:To:References:From: In-Reply-To:Content-Type; b=MDpvuPtoCQ7s7QjT99ZkL3eE6IAsyQvOl+C8UvBx48ebNmTNfz+4GVFJvM985H0Sh/dSDvCzuXyspyqJVeRBiJatTLC8WeiJGZxWKuWdo+6WnKGGmILqlijf2Wb4uuo/gbJFbwJ6a52ys25UXElp7oeG4enNl/wXqqkfzqvLSA8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=suse.com; spf=pass smtp.mailfrom=suse.com; dkim=pass (2048-bit key) header.d=suse.com header.i=@suse.com header.b=AmnNV55Q; arc=none smtp.client-ip=209.85.221.44 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=suse.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=suse.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=suse.com header.i=@suse.com header.b="AmnNV55Q" Received: by mail-wr1-f44.google.com with SMTP id ffacd0b85a97d-39c0dfad22aso4238981f8f.2 for ; Mon, 28 Apr 2025 22:32:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=google; t=1745904755; x=1746509555; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:autocrypt:from :content-language:references:to:subject:user-agent:mime-version:date :message-id:from:to:cc:subject:date:message-id:reply-to; bh=pBIZq3zezEz0lNvhqbJsDoZ6E+a3TOUn7eUnwBRBWME=; b=AmnNV55QdDXAhp0ebBQfArrde7tgvxuRGN38b5nmDYa8jqSbvImQ5GHinBvQl4LgGS m7O5l0zhGmMNlYyBqDAmlJyqEHJFioobdBQfByM6XqFJluSWA5M4FxHSsbMR0rzDMor/ i2dCBtVSdQj/Tr6khvdkXd5NfE4iTC4Oc8rXPGHsF0QDbAUQckc7pgarsDmW5ZW89ADJ of3T83ARrk/DYVUDe/qizBqMK2ays9QgMiHQlSLtsjmoGCkjFLog3mFyfB6ZjQrkLNBO CRVtHqEx9CwYRz09t5xwSOZbDUrHhjiZxDKH+1Boa2fVgbkrrBt+utsG5IYMRU8dIJwD Dy4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1745904755; x=1746509555; h=content-transfer-encoding:in-reply-to:autocrypt:from :content-language:references:to:subject:user-agent:mime-version:date :message-id:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pBIZq3zezEz0lNvhqbJsDoZ6E+a3TOUn7eUnwBRBWME=; b=nbciYkuLI7njkcSP6H9pmRvTiljc+2/GW6X7gtDU7SPF5JcF9djj7voZuTVkS2lYST Osw0BRXhGJFgFAalcxgGpZWiypx15bgeEKkFz9MRF8ws0la0YVSRtrdsHHS29GfeNMAG UoLfqEqakObd8zH3OhPNMxVOGqMpsidrkK+oJm8PmniaswfA2pNQXFpeMtqlrwGKw/5j hpzV9jZSlsjb4BEjBK2nzMz3ti3/z5GqaHoHdREi9fYylmM/z5QKjR3QoTCjA5aJgAqw q59JnACDdy52Gcf+r7qSbr/bDsEImpt1ehfZEns4XwQVm3EITT8Qzzk2rF9dLk0MNMCl I3Lg== X-Forwarded-Encrypted: i=1; AJvYcCVfC9/oZW7/+p5WSf9s8D/kfj4KJrfcWrjUFaPR0SHa2DxFYUJ/y5pw3l8jPW3ypStZGRvO6QYzpHKniA==@vger.kernel.org X-Gm-Message-State: AOJu0YxymO26I5LSlRoKGYC72zQzO+Xvh9FbGwxl696ikIi5tzvio3+5 /xiUGn723hzaz3B6gxHhqj7hn1orJXh5yhnPkKHoinkcsvINonNyFid7+NGJi9Dj7/D6R4PVzID ijx8= X-Gm-Gg: ASbGncuHiGGrC92ssfKoGJHUXLlsV92WLWigItblyIzvaiykXOgTTEM/lLQU45lgn3Q /JXCL15OOmDu38ZJy2xrbUv6DGZSp3wjhGk26YEfoRaBtb+Z1m9urgX53sIYpOLvLNYaxNebOxQ bAVVFaXV/YMIc3/CN2ZHjtBIvznHwGSmXhBg2Wq+lpOBDXZ1/x7OnZhfIjCbkIkArt7rxA0BEYA RhJXEdN0aqbUJghLyZ2JOetDf60EnldhNVCf+GA0idCWkZahbuhRpwABED7KC0E35LkBSpn///z zIbLrhWZyR4h39P7cBKt7rU8ZPTIlYq2EkzbFIPP02w9rFkAqmCD8tskJoECGMuTQ60k X-Google-Smtp-Source: AGHT+IHUHaKCOY9EnzUjy9uWC4NkrHx0ym0nO5Zfsmeg+AJorI6Gx36uHc68zukNeZmV7l7xVBg8EQ== X-Received: by 2002:a5d:64ee:0:b0:39c:142d:c0a with SMTP id ffacd0b85a97d-3a08a35180bmr1118664f8f.19.1745904754986; Mon, 28 Apr 2025 22:32:34 -0700 (PDT) Received: from ?IPV6:2403:580d:fda1::299? (2403-580d-fda1--299.ip6.aussiebb.net. [2403:580d:fda1::299]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-73e2549f570sm9062233b3a.0.2025.04.28.22.32.33 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 28 Apr 2025 22:32:34 -0700 (PDT) Message-ID: <1be5f421-a36e-4a27-8c4b-73140f94a217@suse.com> Date: Tue, 29 Apr 2025 15:02:30 +0930 Precedence: bulk X-Mailing-List: linux-btrfs@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Fwd: HTML message rejected: btrfs checksum error To: Przemek Klosowski , linux-btrfs@vger.kernel.org References: <1745893230-14268-mlmmj-729fb3af@vger.kernel.org> Content-Language: en-US From: Qu Wenruo Autocrypt: addr=wqu@suse.com; keydata= xsBNBFnVga8BCACyhFP3ExcTIuB73jDIBA/vSoYcTyysFQzPvez64TUSCv1SgXEByR7fju3o 8RfaWuHCnkkea5luuTZMqfgTXrun2dqNVYDNOV6RIVrc4YuG20yhC1epnV55fJCThqij0MRL 1NxPKXIlEdHvN0Kov3CtWA+R1iNN0RCeVun7rmOrrjBK573aWC5sgP7YsBOLK79H3tmUtz6b 9Imuj0ZyEsa76Xg9PX9Hn2myKj1hfWGS+5og9Va4hrwQC8ipjXik6NKR5GDV+hOZkktU81G5 gkQtGB9jOAYRs86QG/b7PtIlbd3+pppT0gaS+wvwMs8cuNG+Pu6KO1oC4jgdseFLu7NpABEB AAHNGFF1IFdlbnJ1byA8d3F1QHN1c2UuY29tPsLAlAQTAQgAPgIbAwULCQgHAgYVCAkKCwIE FgIDAQIeAQIXgBYhBC3fcuWlpVuonapC4cI9kfOhJf6oBQJnEXVgBQkQ/lqxAAoJEMI9kfOh Jf6o+jIH/2KhFmyOw4XWAYbnnijuYqb/obGae8HhcJO2KIGcxbsinK+KQFTSZnkFxnbsQ+VY fvtWBHGt8WfHcNmfjdejmy9si2jyy8smQV2jiB60a8iqQXGmsrkuR+AM2V360oEbMF3gVvim 2VSX2IiW9KERuhifjseNV1HLk0SHw5NnXiWh1THTqtvFFY+CwnLN2GqiMaSLF6gATW05/sEd V17MdI1z4+WSk7D57FlLjp50F3ow2WJtXwG8yG8d6S40dytZpH9iFuk12Sbg7lrtQxPPOIEU rpmZLfCNJJoZj603613w/M8EiZw6MohzikTWcFc55RLYJPBWQ+9puZtx1DopW2jOwE0EWdWB rwEIAKpT62HgSzL9zwGe+WIUCMB+nOEjXAfvoUPUwk+YCEDcOdfkkM5FyBoJs8TCEuPXGXBO Cl5P5B8OYYnkHkGWutAVlUTV8KESOIm/KJIA7jJA+Ss9VhMjtePfgWexw+P8itFRSRrrwyUf E+0WcAevblUi45LjWWZgpg3A80tHP0iToOZ5MbdYk7YFBE29cDSleskfV80ZKxFv6koQocq0 vXzTfHvXNDELAuH7Ms/WJcdUzmPyBf3Oq6mKBBH8J6XZc9LjjNZwNbyvsHSrV5bgmu/THX2n g/3be+iqf6OggCiy3I1NSMJ5KtR0q2H2Nx2Vqb1fYPOID8McMV9Ll6rh8S8AEQEAAcLAfAQY AQgAJgIbDBYhBC3fcuWlpVuonapC4cI9kfOhJf6oBQJnEXWBBQkQ/lrSAAoJEMI9kfOhJf6o cakH+QHwDszsoYvmrNq36MFGgvAHRjdlrHRBa4A1V1kzd4kOUokongcrOOgHY9yfglcvZqlJ qfa4l+1oxs1BvCi29psteQTtw+memmcGruKi+YHD7793zNCMtAtYidDmQ2pWaLfqSaryjlzR /3tBWMyvIeWZKURnZbBzWRREB7iWxEbZ014B3gICqZPDRwwitHpH8Om3eZr7ygZck6bBa4MU o1XgbZcspyCGqu1xF/bMAY2iCDcq6ULKQceuKkbeQ8qxvt9hVxJC2W3lHq8dlK1pkHPDg9wO JoAXek8MF37R8gpLoGWl41FIUb3hFiu3zhDDvslYM4BmzI18QgQTQnotJH8= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 在 2025/4/29 11:55, Przemek Klosowski 写道: > I have a RAID1 btrfs root/home on Fedora 42 that developed what > appears to be a single data checksum error. RAM tests fine, but it's a > DELL system that had memory problems early on (years ago), that were > fixed by Dell BIOS memory tests (which changed the mem controller > settings). > > The errors seem to have started right after a scrub (see btrfs > messages from journal below) > > btrfs check --readonly --force --check-data-csum -p /dev/nvme0n1p2 > > shows a cascade of errors (which seem to be increasing in number) > .. > [4/7] checking fs roots (0:00:04 elapsed, 60923 > items checked) > mirror 1 bytenr 299511672832 csum 0x125beb3c expected csum > 0xc8374bb569 items checked) > mirror 1 bytenr 299511676928 csum 0x4c6adf72 expected csum 0xd82f54b8 > mirror 2 bytenr 299511672832 csum 0x125beb3c expected csum 0xc8374bb5 > mirror 2 bytenr 299511676928 csum 0x4c6adf72 expected csum 0xd82f54b8 > mirror 1 bytenr 306513821696 csum 0x8941f998 expected csum > 0xa5fe1bfd94 items checked) > mirror 1 bytenr 306513825792 csum 0x8941f998 expected csum 0x77c755d4 > .. and many more > > I can recover the file with only 1 4kB block zeroed out. > > Is there a way to read the bad sector? I thought that > mount -o ro,degraded,rescue=ignoredatacsums/dev/sda5 /mnt > would read data ignoring the bad checksum? as it is, it replicates the > I/O error that is raised when reading the original file. It turns out to be a bug in the implementation, we expect to ignore bad data csum error and return the data directly, but it's not implemented if the csum tree is still valid... I'll send out a patch for that, but that will also mean with rescue=idatacsums mount option, the data will only be the first one btrfs read out. It'll be fine for your case, as both mirrors have the same csum. > > Do you think that deleting the file with the bad checksum will solve > this? Yes. > or should I move to rebuilding and restoring from backups? No need, "btrfs check --check-data-csum" is the most comprehensive check we have and it only reports error of data checksum so far (better than scrub because of the comprehensive metadata checks). Although you will need to find out all involved files, scrub is doing a good job resolving the path, but the output may be ratelimited. I'd recommend to craft a small script, parsing all involved unique bytenr into `btrfs ins logical` to get a full path to the affected files. Thanks, Qu > > > Apr 26 22:41:04 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > started on devid 1 > Apr 26 22:41:04 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > started on devid 2 > Apr 26 22:41:36 fedora kernel: BTRFS error (device nvme0n1p2): unable > to fixup (regular) error at logical 452965761024 on dev /dev/nvme0n1p2 > physical 74303995904 > Apr 26 22:41:36 fedora kernel: BTRFS warning (device nvme0n1p2): > checksum error at logical 452965761024 on dev /dev/nvme0n1p2, physical > 74303995904, root 257, inode 35328, offset 26034176, length 4096, > links 1 (path: usr/lib/sysimage/rpm/rpmdb.sqlite-wal) > Apr 26 22:42:52 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > finished on devid 1 with status: 0 > Apr 26 22:45:46 fedora kernel: BTRFS error (device nvme0n1p2): unable > to fixup (regular) error at logical 452965761024 on dev /dev/sda5 > physical 147297468416 > Apr 26 22:45:46 fedora kernel: BTRFS warning (device nvme0n1p2): > checksum error at logical 452965761024 on dev /dev/sda5, physical > 147297468416, root 257, inode 35328, offset 26034176, length 4096, > links 1 (path: usr/lib/sysimage/rpm/rpmdb.sqlite-wal) > Apr 26 22:48:45 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > finished on devid 2 with status: 0 > Apr 26 22:53:23 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > started on devid 2 > Apr 26 22:53:23 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > started on devid 1 > Apr 26 22:53:52 fedora kernel: BTRFS error (device nvme0n1p2): unable > to fixup (regular) error at logical 452965761024 on dev /dev/nvme0n1p2 > physical 74303995904 > Apr 26 22:53:52 fedora kernel: BTRFS warning (device nvme0n1p2): > checksum error at logical 452965761024 on dev /dev/nvme0n1p2, physical > 74303995904, root 257, inode 35328, offset 26034176, length 4096, > links 1 (path: usr/lib/sysimage/rpm/rpmdb.sqlite-wal) > Apr 26 22:55:07 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > finished on devid 1 with status: 0 > Apr 26 22:58:04 fedora kernel: BTRFS error (device nvme0n1p2): unable > to fixup (regular) error at logical 452965761024 on dev /dev/sda5 > physical 147297468416 > Apr 26 22:58:04 fedora kernel: BTRFS warning (device nvme0n1p2): > checksum error at logical 452965761024 on dev /dev/sda5, physical > 147297468416, root 257, inode 35328, offset 26034176, length 4096, > links 1 (path: usr/lib/sysimage/rpm/rpmdb.sqlite-wal) > Apr 26 23:01:01 fedora kernel: BTRFS info (device nvme0n1p2): scrub: > finished on devid 2 with status: 0 > Apr 27 07:35:32 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:32 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 > Apr 27 07:35:32 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:32 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 > Apr 27 07:35:32 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:32 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 > Apr 27 07:35:32 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:32 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 > Apr 27 07:35:33 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:33 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 > Apr 27 07:35:33 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:33 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 3, gen 0 > Apr 27 07:35:33 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:33 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 > Apr 27 07:35:33 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:33 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 4, gen 0 > Apr 27 07:35:33 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:33 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 > Apr 27 07:35:33 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:33 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 > Apr 27 07:35:55 fedora kernel: btrfs_print_data_csum_error: 2 > callbacks suppressed > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:55 fedora kernel: btrfs_dev_stat_inc_and_print: 2 > callbacks suppressed > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x127b77ee expected csum > 0xcf4a5572 mirror 2 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/sda5 errs: wr 0, rd 0, flush 0, corrupt 11, gen 0 > Apr 27 07:35:55 fedora kernel: BTRFS warning (device nvme0n1p2): csum > failed root 257 ino 35328 off 26079232 csum 0x862b6025 expected csum > 0xcf4a5572 mirror 1 > Apr 27 07:35:55 fedora kernel: BTRFS error (device nvme0n1p2): bdev > /dev/nvme0n1p2 errs: wr 0, rd 0, flush 0, corrupt 11, gen 0 >