Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
After converting btrfs to raid5 or raid6 profile, btrfs scrub returns non-zero return value, but the output of scrub indicates no errors, dmesg shows no errors either.
Not sure it's a kernel issue or a btrfs-progs issue, take it as btrfs-progs though.
[root@ibm-p750e-02-lp1 profile-conversion]# mkfs -t btrfs -m raid0 -d raid0 -f -K /dev/loop{0..3}
WARNING! - Btrfs v3.12 IS EXPERIMENTAL
WARNING! - see http://btrfs.wiki.kernel.org before using
Turning ON incompat feature 'extref': increased hardlink limit per file to 65536
adding device /dev/loop1 id 2
adding device /dev/loop2 id 3
adding device /dev/loop3 id 4
fs created label (null) on /dev/loop0
nodesize 65536 leafsize 65536 sectorsize 65536 size 4.00GiB
Btrfs v3.12
[root@ibm-p750e-02-lp1 profile-conversion]# mount /dev/loop0 /mnt/btrfs
[root@ibm-p750e-02-lp1 profile-conversion]# btrfs fi balance start -mconvert=raid5 -dconvert=raid5 /mnt/btrfs
Done, had to relocate 6 out of 6 chunks
[root@ibm-p750e-02-lp1 profile-conversion]# umount /mnt/btrfs
[root@ibm-p750e-02-lp1 profile-conversion]# mount /dev/loop0 /mnt/btrfs
[root@ibm-p750e-02-lp1 profile-conversion]# btrfs scrub start -B /mnt/btrfs
scrub done for 12e251f9-bc07-4fbd-a25a-a50679bc3545
scrub started at Sun Jan 12 22:25:24 2014 and finished after 0 seconds
total bytes scrubbed: 7.50MiB with 0 errors
[root@ibm-p750e-02-lp1 profile-conversion]# echo $?
3
Version-Release number of selected component (if applicable):
btrfs-progs-3.12-1.el7
kernel-3.10.0-64.el7
How reproducible:
always
Steps to Reproduce:
1. mkfs -t btrfs -m raid0 -d raid0 -f -K /dev/loop{0..3}
2. mount /dev/loop0 /mnt/btrfs
3. btrfs fi balance start -mconvert=raid5 -dconvert=raid6 /mnt/btrfs
4. btrfs scrub start -B /mnt/btrfs
Actual results:
btrfs scrub returns 3, but no error messages in stderr nor in dmesg
Expected results:
btrfs scrub returns 0 or show some error messages if there're really some errors
Additional info:
(In reply to Wang Shilong from comment #2)
> Created attachment 877550[details]
> Bug fix for your problem
This patch can be applied to btrfs-next, and it should can fix your problem, i'd like you can test it before i send this patch out to list.
Thanks for reporting.
Fixed in v3.16 with:
965cd86 btrfs-progs: adjust the return values for scrub
Closing this and others with NEXTRELEASE since it's part of a rebase, but if you prefer we can re-open, get all the acks, and add it to the errata. I'm not sure if that's worth it, but if you want to, please let me know.
Thanks,
-Eric
Description of problem: After converting btrfs to raid5 or raid6 profile, btrfs scrub returns non-zero return value, but the output of scrub indicates no errors, dmesg shows no errors either. Not sure it's a kernel issue or a btrfs-progs issue, take it as btrfs-progs though. [root@ibm-p750e-02-lp1 profile-conversion]# mkfs -t btrfs -m raid0 -d raid0 -f -K /dev/loop{0..3} WARNING! - Btrfs v3.12 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using Turning ON incompat feature 'extref': increased hardlink limit per file to 65536 adding device /dev/loop1 id 2 adding device /dev/loop2 id 3 adding device /dev/loop3 id 4 fs created label (null) on /dev/loop0 nodesize 65536 leafsize 65536 sectorsize 65536 size 4.00GiB Btrfs v3.12 [root@ibm-p750e-02-lp1 profile-conversion]# mount /dev/loop0 /mnt/btrfs [root@ibm-p750e-02-lp1 profile-conversion]# btrfs fi balance start -mconvert=raid5 -dconvert=raid5 /mnt/btrfs Done, had to relocate 6 out of 6 chunks [root@ibm-p750e-02-lp1 profile-conversion]# umount /mnt/btrfs [root@ibm-p750e-02-lp1 profile-conversion]# mount /dev/loop0 /mnt/btrfs [root@ibm-p750e-02-lp1 profile-conversion]# btrfs scrub start -B /mnt/btrfs scrub done for 12e251f9-bc07-4fbd-a25a-a50679bc3545 scrub started at Sun Jan 12 22:25:24 2014 and finished after 0 seconds total bytes scrubbed: 7.50MiB with 0 errors [root@ibm-p750e-02-lp1 profile-conversion]# echo $? 3 Version-Release number of selected component (if applicable): btrfs-progs-3.12-1.el7 kernel-3.10.0-64.el7 How reproducible: always Steps to Reproduce: 1. mkfs -t btrfs -m raid0 -d raid0 -f -K /dev/loop{0..3} 2. mount /dev/loop0 /mnt/btrfs 3. btrfs fi balance start -mconvert=raid5 -dconvert=raid6 /mnt/btrfs 4. btrfs scrub start -B /mnt/btrfs Actual results: btrfs scrub returns 3, but no error messages in stderr nor in dmesg Expected results: btrfs scrub returns 0 or show some error messages if there're really some errors Additional info: