Control: tag -1 upstream Russell Coker <[email protected]> writes:
> Package: btrfs-progs > Version: 6.14-1 > Severity: normal > > I'm doing a test of BTRFS kernel functionality by running a script that > repeatedly corrupts one disk in a BTRFS RAID-5 and fixing it with a scrub. > The > command "btrfs scrub start -B /mnt" gives the following output, it corrected > 23186 errors (which seems a likely number given the situation) and then gives > a > WARNING message saying "1 corrected" which has no correlation to what > happened. > > I think the WARNING should say 23186 corrected. > > Starting scrub on devid 1 > Starting scrub on devid 2 > Starting scrub on devid 3 > Starting scrub on devid 4 > scrub done for 4bda2da0-54a2-4992-83d7-15b9667f65ab > Scrub started: Thu Jun 26 02:07:02 2025 > Status: finished > Duration: 0:00:04 > Total to scrub: 1.26GiB > Rate: 323.51MiB/s > Error summary: csum=23186 > Corrected: 23186 > Uncorrectable: 0 > Unverified: 0 > WARNING: errors detected during scrubbing, 1 corrected Raid56 is still has nontrivial data loss cases, and does not meet Debian standards for quality, reliability, nor stability. Please forward your data and reproducer to upstream. https://btrfs.readthedocs.io/en/stable/Status.html#block-group-profiles Best, Nicholas
signature.asc
Description: PGP signature
