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.
+++ This bug was initially created as a clone of Bug #660661 +++
Description of problem:
While testing 707091 for RHEL 6.2, I believe I hit this bug.
Product versions:
gfs2-utils-3.0.12.1-5.el6.x86_64
Steps to reproduce:
Run gfs_fsck_stress -e grow_full
Actual Results:
SCENARIO - [grow_full]
Fill the file system then try to grow it
Creating 2G LV grow on buzz-04
Creating file system on /dev/fsck/grow with options '-p lock_dlm -j 5 -t buzzez:grow' on buzz-04
Device: /dev/fsck/grow
Blocksize: 4096
Device Size 2.00 GB (524288 blocks)
Filesystem Size: 2.00 GB (524288 blocks)
Journals: 5
Resource Groups: 8
Locking Protocol: "lock_dlm"
Lock Table: "buzzez:grow"
UUID: 59c772c6-f329-dc7b-03ec-d3e14138c558
Mounting gfs2 /dev/fsck/grow on buzz-01 with opts ''
Mounting gfs2 /dev/fsck/grow on buzz-02 with opts ''
Mounting gfs2 /dev/fsck/grow on buzz-03 with opts ''
Mounting gfs2 /dev/fsck/grow on buzz-04 with opts ''
Mounting gfs2 /dev/fsck/grow on buzz-05 with opts ''
- filling file system
- wrote 54 files
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/fsck-grow
2096912 2096912 0 100% /mnt/fsck
Extending LV grow by +100G on buzz-04
Growing /dev/fsck/grow on buzz-04
FS: Mount Point: /mnt/fsck
FS: Device: /dev/dm-3
FS: Size: 524288 (0x80000)
FS: RG size: 65533 (0xfffd)
DEV: Size: 26738688 (0x1980000)
The file system grew by 102400MB.
gfs2_grow complete.
- write more into the new space
100+0 records in
100+0 records out
1048576000 bytes (1.0 GB) copied, 1.51232 s, 693 MB/s
Unmounting /mnt/fsck on buzz-01
Unmounting /mnt/fsck on buzz-02
Unmounting /mnt/fsck on buzz-03
Unmounting /mnt/fsck on buzz-04
Unmounting /mnt/fsck on buzz-05
Starting fsck of /dev/fsck/grow on buzz-04
fsck output in /tmp/gfs_fsck_stress.2356/1.grow_full/1.fsck-buzz-04.log
fsck.gfs2 of /dev/fsck/grow on buzz-04 took 5 seconds
fsck.gfs2 returned 1
fsck.gfs2 of /dev/fsck/grow on buzz-04 fixed some errors
$ cat /tmp/gfs_fsck_stress.2356/1.grow_full/1.fsck-buzz-04.log
Validating Resource Group index.
Level 1 rgrp check: Checking if all rgrp and rindex values are good.
(level 1 passed)
Found unlinked inode at 524287 (0x7ffff)
Unlinked inode has zero size
Block 524287 (0x7ffff) seems to be free space, but is marked as inode in the bitmap.
The bitmap was fixed.
Resource group counts updated
Inode count inconsistent: is 9 should be 8
The statfs file is wrong:
Current statfs values:
blocks: 26735428 (0x197f344)
free: 25954684 (0x18c097c)
dinodes: 83 (0x53)
Calculated statfs values:
blocks: 26735428 (0x197f344)
free: 25954685 (0x18c097d)
dinodes: 82 (0x52)
The statfs file was fixed.
I am able to recreate this with linux-2.6.32-164, but not linux-2.6.32-188, and looking at the linux-2.6.32-188 code, this patch has already been added. Do you want to retest and verify this yourself, or can I just close this CURRENT_RELEASE?
Looks like it was here.
https://bugzilla.redhat.com/show_bug.cgi?id=661048
So this clearly predates the problem. The fix is definitely in linux-2.6.32-164.
Be that as it may, I'm still not able to recreate the problem on linux-2.6.32-188, although I don't have a reason for why.