Gfilui

I have a production multi-pathed iSCSI SAN (Dell MD3200i) with 40Tib of storage. We recently purchased an additional shelf expanding it to 80Tib. This storage is presented to an Ubuntu 14.04.5 LTS server as part of a multipath configuration on /dev/mapper/mpath0-part1.

# multipath -ll
mpath0 (3644a842000016bfd000002a654bf22ad) dm-2 DELL ,MD32xxi
size=**80T** features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 rdac' wp=rw
|-+- policy='round-robin 0' prio=6 status=active
| |- 3:0:0:1 sdg 8:96 active ready running
| |- 4:0:0:1 sdi 8:128 active ready running
| |- 5:0:0:1 sdd 8:48 active ready running
| `- 8:0:0:1 sdb 8:16 active ready running
`-+- policy='round-robin 0' prio=1 status=enabled
 |- 10:0:0:1 sdc 8:32 active ghost running
 |- 6:0:0:1 sdh 8:112 active ghost running
 |- 7:0:0:1 sdf 8:80 active ghost running
 `- 9:0:0:1 sde 8:64 active ghost running

Listing the block devices shows the disk and partitions have been expanded to the SAN volume size. With the disk being (md-2) or /dev/md-2 and the partition being (md-3) or /dev/md-3. Both can see the 80Tib of storage.

# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 160G 0 disk
├─sda1 8:1 0 243M 0 part 
/boot
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 159.8G 0 part
 ├─pathology--linux--fileserver--vg-root (dm-0) 252:0 0 151.7G 0 lvm /
 └─pathology--linux--fileserver--vg-swap_1 (dm-1) 252:1 0 8G 0 lvm [SWAP]
sdb 8:16 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sdc 8:32 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sdd 8:48 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sde 8:64 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sdf 8:80 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sdg 8:96 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sdh 8:112 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sdi 8:128 0 80T 0 disk
└─mpath0 (dm-2) 252:2 0 80T 0 mpath
 └─mpath0-part1 (dm-3) 252:3 0 80T 0 part
sr0 11:0 1 1024M 0 rom

When mounted, the disk only shows 40Tib.

# df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.9G 12K 7.9G 1% /dev
tmpfs 1.6G 1.4M 1.6G 1% /run
/dev/dm-0 150G 7.0G 135G 5% /
none 4.0K 0 4.0K 0% /sys/fs/cgroup
none 5.0M 0 5.0M 0% /run/lock
none 7.9G 152K 7.9G 1% /run/shm
none 100M 40K 100M 1% /run/user
/dev/sda1 236M 105M 119M 47% /boot
/dev/mapper/mpath0-part1 37T 35T 299G 100% /Pathology_Lab

The command e2fsck -f /dev/mapper/mpath0-part1 successfully runs without error, however the command resize2fs -p /dev/mapper/mpath0-part1 just hangs and nothing shows in the logs.

I realize this could take a long time however nothing is indicating that it is expanding or even running except for the processor consumption.

I am seeing bad superblock errors on /dev/sdb -- /dev/sdi and when I looked up these errors it appears I "may" have to rebuild this disk from scratch; any pointing in the right direction is appreciated.