1236538 – mdadm --grow --size does not work for >2TB

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.

Bug 1236538 - mdadm --grow --size does not work for >2TB

Summary: mdadm --grow --size does not work for >2TB

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	mdadm
Sub Component:
Version:	7.1
Hardware:	x86_64
OS:	Linux
Priority:	unspecified
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	XiaoNi
QA Contact:	Zhang Yi
Docs Contact:
URL:
Whiteboard:
Depends On:	1164494
Blocks:
TreeView+	depends on / blocked

Reported:	2015-06-29 11:50 UTC by XiaoNi
Modified:	2015-11-19 13:52 UTC (History)
CC List:	8 users (show)
Fixed In Version:	mdadm-3.3.2-4.el7
Doc Type:	Bug Fix
Doc Text:	Previously, on a system with a RAID1 array, after attempting to resize the array to a fix size beyond the 2 TB limit, the request was ignored. With this update, the reshape works as expected in the described situation.
Clone Of:	1164494
Environment:
Last Closed:	2015-11-19 13:52:24 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2015:2435	0	normal	SHIPPED_LIVE	mdadm bug fix update	2015-11-19 11:33:15 UTC

Comment 3 Zhang Yi 2015-07-21 02:39:19 UTC

This issue can be reproduced on mdadm-3.3.2-2.el7.x86_64
Log:
[root@storageqe-09 ~]# mdadm -D /dev/md0 
/dev/md0:
        Version : 1.2
  Creation Time : Mon Jul 20 00:45:33 2015
     Raid Level : raid1
     Array Size : 3906885632 (3725.90 GiB 4000.65 GB)
  Used Dev Size : 3906885632 (3725.90 GiB 4000.65 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Mon Jul 20 08:59:53 2015
          State : clean 
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : 0
           UUID : 91a2d730:5a9b4cca:b0e1e126:d4cd8130
         Events : 5927

    Number   Major   Minor   RaidDevice State
       0       8       97        0      active sync   /dev/sdg1
       1       8      113        1      active sync   /dev/sdh1
[root@storageqe-09 ~]# mdadm /dev/md0 --grow --size=3006885632
mdadm: component size of /dev/md0 unchanged at 3906885632K
unfreeze
[root@storageqe-09 ~]# mdadm /dev/md0 --grow --size=2147483647
mdadm: component size of /dev/md0 has been set to 2147483647K
unfreeze
[root@storageqe-09 ~]# mdadm /dev/md0 --grow --size=3006885632
mdadm: component size of /dev/md0 unchanged at 2147483647K
unfreeze


Fixed on mdadm-3.3.2-4.el7.x86_64
Log:

[root@storageqe-09 ~]# mdadm /dev/md0 --grow --size=3006885632
mdadm: component size of /dev/md0 has been set to 3006885632K
unfreeze
[root@storageqe-09 ~]# mdadm --wait /dev/md0 
[root@storageqe-09 ~]# mdadm /dev/md0 --grow --size=max
mdadm: component size of /dev/md0 has been set to 3906885632K
unfreeze
[root@storageqe-09 ~]# cat /proc/mdstat 
Personalities : [raid1] 
md0 : active raid1 sdh1[1] sdg1[0]
      3906885632 blocks super 1.2 [2/2] [UU]
      [===============>.....]  resync = 77.3% (3020777536/3906885632) finish=151.2min speed=97628K/sec
      bitmap: 8/30 pages [32KB], 65536KB chunk

unused devices: <none>
[root@storageqe-09 ~]# mdadm --wait /dev/md0 
[root@storageqe-09 ~]# cat /proc/mdstat 
Personalities : [raid1] 
md0 : active raid1 sdh1[1] sdg1[0]
      3906885632 blocks super 1.2 [2/2] [UU]
      bitmap: 0/30 pages [0KB], 65536KB chunk

unused devices: <none>


Change to VERIFIED

Comment 4 errata-xmlrpc 2015-11-19 13:52:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2435.html

Note You need to log in before you can comment on or make changes to this bug.