martinjuhasz Posted November 4, 2022 Share Posted November 4, 2022 Hello, i'm getting this message whenever i start my array: pool BTRFS too many profiles (You can ignore this warning when a pool balance operation is in progress) There is no balancing operation taking place. i also did a full balance without any changes, reboot, nothing helped. btrfs fi df /mnt/cache Data, single: total=124.01GiB, used=38.28GiB Data, RAID1: total=289.00GiB, used=142.08GiB System, RAID1: total=32.00MiB, used=80.00KiB System, DUP: total=8.00MiB, used=0.00B Metadata, RAID1: total=1.00GiB, used=302.75MiB Metadata, DUP: total=1.00GiB, used=155.50MiB GlobalReserve, single: total=270.20MiB, used=0.00B WARNING: Multiple block group profiles detected, see 'man btrfs(5)'. WARNING: Data: single, raid1 WARNING: Metadata: raid1, dup WARNING: System: raid1, dup I'm a bit lost on what to do? Anyone might help me out? Quote Link to comment
trurl Posted November 4, 2022 Share Posted November 4, 2022 attach diagnostics to your NEXT post in this thread Quote Link to comment
martinjuhasz Posted November 4, 2022 Author Share Posted November 4, 2022 sure winston-diagnostics-20221104-1347.zip Quote Link to comment
JorgeB Posted November 4, 2022 Share Posted November 4, 2022 Balance aborted because it found some data corruption, run a scrub then look for the affected files in the syslog, delete/restore from backups those and run another balance. Quote Link to comment
martinjuhasz Posted November 4, 2022 Author Share Posted November 4, 2022 ok. with scrub you mean i should run btrfs scrub start /mnt/cache ? will do if this is correct. Quote Link to comment
JorgeB Posted November 4, 2022 Share Posted November 4, 2022 You can do it using the GUI, click on cache and scroll down. Quote Link to comment
martinjuhasz Posted November 4, 2022 Author Share Posted November 4, 2022 ok, one more question if you might ask. doing it in the ui, should i Repair corrupted blocks or not? i guess so? Is not checking like a dry run? Quote Link to comment
JorgeB Posted November 4, 2022 Share Posted November 4, 2022 You can enable repair but at least some blocks will not be repairable. Quote Link to comment
martinjuhasz Posted November 4, 2022 Author Share Posted November 4, 2022 (edited) Ok, it finished, these are the syslog outputs Nov 4 17:12:12 Winston ool www[15451]: /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' '' Nov 4 17:12:12 Winston kernel: BTRFS info (device dm-3): scrub: started on devid 1 Nov 4 17:12:12 Winston kernel: BTRFS info (device dm-3): scrub: started on devid 2 Nov 4 17:12:52 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 5, gen 0 Nov 4 17:12:52 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 81550143488 on dev /dev/mapper/sdf1 Nov 4 17:13:34 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 6, gen 0 Nov 4 17:13:34 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 122435252224 on dev /dev/mapper/sdf1 Nov 4 17:13:35 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 7, gen 0 Nov 4 17:13:35 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 123201454080 on dev /dev/mapper/sdf1 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 8, gen 0 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 179388588032 on dev /dev/mapper/sdf1 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 9, gen 0 Nov 4 17:13:56 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 179478081536 on dev /dev/mapper/sdf1 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 10, gen 0 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 180374007808 on dev /dev/mapper/sdf1 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 11, gen 0 Nov 4 17:13:57 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 185834225664 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 12, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 186957123584 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 13, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 186955014144 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 14, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187113508864 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 15, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187287994368 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 16, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187306131456 on dev /dev/mapper/sdf1 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 17, gen 0 Nov 4 17:13:58 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 187558371328 on dev /dev/mapper/sdf1 Nov 4 17:14:01 Winston kernel: scrub_handle_errored_block: 52 callbacks suppressed Nov 4 17:14:01 Winston kernel: btrfs_dev_stat_print_on_error: 52 callbacks suppressed Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 70, gen 0 Nov 4 17:14:01 Winston kernel: scrub_handle_errored_block: 52 callbacks suppressed Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 191955169280 on dev /dev/mapper/sdf1 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 71, gen 0 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 191962398720 on dev /dev/mapper/sdf1 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 72, gen 0 Nov 4 17:14:01 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 192054423552 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 73, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194658598912 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 74, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194773180416 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 75, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194779500544 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 76, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194793492480 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 77, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194779983872 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 78, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194928234496 on dev /dev/mapper/sdf1 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 79, gen 0 Nov 4 17:14:02 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 194943197184 on dev /dev/mapper/sdf1 Nov 4 17:16:46 Winston kernel: scrub_handle_errored_block: 1 callbacks suppressed Nov 4 17:16:46 Winston kernel: btrfs_dev_stat_print_on_error: 1 callbacks suppressed Nov 4 17:16:46 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 81, gen 0 Nov 4 17:16:46 Winston kernel: BTRFS error (device dm-3): fixed up error at logical 801075355648 on dev /dev/mapper/sdf1 Nov 4 17:17:54 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdg1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Nov 4 17:17:54 Winston kernel: scrub_handle_errored_block: 1 callbacks suppressed Nov 4 17:17:54 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 953985130496 on dev /dev/mapper/sdg1 Nov 4 17:18:01 Winston kernel: BTRFS info (device dm-3): scrub: finished on devid 2 with status: 0 Nov 4 17:18:12 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 82, gen 0 Nov 4 17:18:12 Winston kernel: BTRFS error (device dm-3): unable to fixup (regular) error at logical 953985130496 on dev /dev/mapper/sdf1 Nov 4 17:18:30 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 83, gen 0 Nov 4 17:18:30 Winston kernel: BTRFS error (device dm-3): fixed up error at logical 846948855808 on dev /dev/mapper/sdf1 Nov 4 17:19:06 Winston kernel: BTRFS error (device dm-3): bdev /dev/mapper/sdf1 errs: wr 0, rd 0, flush 0, corrupt 84, gen 0 Nov 4 17:19:06 Winston kernel: BTRFS error (device dm-3): fixed up error at logical 861991755776 on dev /dev/mapper/sdf1 Nov 4 17:20:33 Winston emhttpd: spinning down /dev/sdc Nov 4 17:20:42 Winston kernel: BTRFS info (device dm-3): scrub: finished on devid 1 with status: 0 Nov 4 17:21:52 Winston emhttpd: spinning down /dev/sde Nov 4 17:24:41 Winston emhttpd: spinning down /dev/sdd not sure what that means? not any files listet here i tried resolving "logical" with inspect, but this doesnt result in any output, f.e.: btrfs inspect-internal logical-resolve 81550143488 /mnt/cache Edited November 4, 2022 by martinjuhasz Quote Link to comment
JorgeB Posted November 4, 2022 Share Posted November 4, 2022 That suggests the problem is with metadata, in that case best to backup everything you can and re-format the pool. Quote Link to comment
martinjuhasz Posted November 4, 2022 Author Share Posted November 4, 2022 oh damn, okay. i might switch back to zfs then. really wanted to avoid doing "manual" local backup with rsync. would you mind elaborating what indicates that its metadata? Quote Link to comment
JorgeB Posted November 4, 2022 Share Posted November 4, 2022 Mainly not indicating a file path, this is how it looks when it's data: Oct 6 09:30:20 Test kernel: BTRFS warning (device md1): checksum error at logical 8981135360 on dev /dev/md1, sector 18000032, root 5, inode 266, offset 739328000, length 4096, links 1 (path: ISOS/Windows.10.ISO) Oct 6 09:30:20 Test kernel: BTRFS error (device md1): bdev /dev/md1 errs: wr 0, rd 0, flush 0, corrupt 330, gen 0 Quote Link to comment
martinjuhasz Posted November 6, 2022 Author Share Posted November 6, 2022 ok. so i moved files, formatted newly to btrfs encrypted, moved files again. Seems to be normal currently. i ran scrub and balance after moving files back and no errors so far. anything i can do besides that to verify its ok now? might happen over time again right? Quote Link to comment
JorgeB Posted November 6, 2022 Share Posted November 6, 2022 See here for better pool monitoring so are notified immediately if there are similar issues. Quote Link to comment
martinjuhasz Posted November 6, 2022 Author Share Posted November 6, 2022 ok. thank you so much for your time and help 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.