User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.7) Gecko/2009030503 Fedora/3.0.7-1.fc10 Firefox/3.0.7 User has extended a clustered logical volume and is attempting to grow the gfs2 filesystem that resides on it to take up that new space. This volume is using 4k blocksize The sosreport confirms that the space is showing up properly. I reviewed the steps customer performed and they look correct. However upon attempting to grow the GFS2 filesytem they get an error: $ gfs2_grow /edh_gfs2_test1 Error: The device has grown by less than one Resource Group (RG). The device grew by 0MB. One RG is 255MB for this file system. gfs2_grow complete. It looks like they have updated to gfs2-utils-0.1.53-1.el5_3.1-x86_64 which resolves that gfs2_grow issue in these bzs. https://bugzilla.redhat.com/show_bug.cgi?id=483527 https://bugzilla.redhat.com/show_bug.cgi?id=469773 $ grep gfs installed-rpms gfs-utils-0.1.18-1.el5-x86_64 kmod-gfs-0.1.31-3.el5-x86_64 gfs2-utils-0.1.53-1.el5_3.1-x86_64 ------------------------- HARDWARE INFO: ------------------------- Storage is located on 3PAR DATA (RAID-5 device) /dev/sdd :VMware :Virtual disk :1.0 : : 19922944 [root@ohedf068 tmp]# 138 IOLUN04 50002AC016430379 OHEGNE4_COMM 23000005E600B5D0 2:4:3 port IOLUN04 Base --- 5699 RW started 0 0 20480 CISCO MDS9509 SAN SWITCH with the following software: Software BIOS: version 1.1.0 loader: version 1.2(2) kickstart: version 3.2(2c) system: version 3.2(2c) Reproducible: Always Steps to Reproduce: STEPS TO REPRODUCE: For me this only works on non-4k blocksize, but 4k for customer: 1) mkfs.gfs2 -b 2048 ... on a logical volume 2) mount device 3) lvextend the logical volume (customer and I were both adding 2Gb) 4) gfs2_grow device Actual Results: Error thrown: Error: The device has grown by less than one Resource Group (RG). The device grew by 0MB. One RG is 255MB for this file system. gfs2_grow complete. Expected Results: The gfs2 fs is grown to the correct size.
Created attachment 336528 [details] gfs meta data
With the latest gfs2-utils package, I've been able to successfully grow the customer's file system from 5GB to 10GB using the customer's metadata. All evidence points to this problem being a duplicate of bug #469773 (which is in Modified state, so the fix hasn't been shipped yet, but should make the next release). Unless I see evidence to the contrary in the next day or so, I'm planning to close this one as a duplicate of bug #469773.
I may have recreated the problem by starting with a 2GB file system, and extending by another 2G. I got these messages: Error: The device has grown by less than one Resource Group (RG). The device grew by 0MB. One RG is 255MB for this file system. I'll figure out why it did that today.
Sorry, a typing mistake caused a false-positive. Please disregard comment #4. When done correctly, with the latest gfs2 code that includes the fix for bug #469733, I had no problem extending and gfs2_growing a GFS2 file system from 2GB to 4GB.
I guess there are no objections, so I'm closing this as a duplicate of bug #469773. If anyone finds evidence to the contrary, feel free to reopen this bug record. *** This bug has been marked as a duplicate of bug 469773 ***