Setup:
12x 1TB drives in a RAID6 (MDADM)
crypt-setup running ontop of MDADM
LVM running on the crypted drives
EXT4 on the LVM
Background:
I added a new drive to the RAID (increasing from 11 to 12 drives), and 'bubbled' up through the layers (MDADM, etc…) to reizing the ext4 partition. This machine is used as a centralized repository for photography and as a backup server (for both Windows and Mac machines) so bringing it down to add the drive and wait for the resizing and everything wasn't really an option. So I started the resize operation several days ago. HTOP is reporting the resize2fs operation as running for 81h now. DMESG and syslog are both clear, and the drives are still accessable. The resize command reports it's started an online resize of the partition, so the process IS running, and it is burning through 100% of one of my cores.
Question: Is it normal for the operation to take this long or has something gone horribly wrong? Where would I start looking for signs of trouble?
Best Answer
If you ran
resize2fswith the-poption, it would print out regular progress reports. However, since you didn't, there doesn't seem to be any way to get that information while it's running.This related question seems to indicate that it is fairly normal for
resize2fsto run for a very long time.