I'm getting the following error when I try to resize my ext4 filesystem after growing a four-disk RAID 6 array (5.41TiB after parity) to eight disks (16.4TiB after parity):
Zitat"Failed to grow the filesystem '/dev/md0': resize2fs 1.42.5 (29-Jul-2012) resize2fs: New size too large to be expressed in 32 bits"
with the following stack trace:
ZitatAlles anzeigenError #6000:
exception 'OMVException' with message 'Failed to grow the filesystem '/dev/md0': resize2fs 1.42.5 (29-Jul-2012)
resize2fs: New size too large to be expressed in 32 bits
' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:699
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->resize(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('resize', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'resize', Array, Array, 1)
#4 {main}
This appears to be an issue where the ext4 filesystem was created as a 32-bit filesystem and I'm trying to expand it beyond what can be addressed with a 32-bit filesystem. I'm not the first to have come across this issue, which appeared to have been fixed back in OMV 1.8. After doing some additional reading, it seems that while ext4 itself has supported volumes larger than 16TiB for some time, the e2fsprogs tools didn't until version 1.42. I have version 1.42.5 of the tools, however. (And for what it's worth, switching to the backported 3.16 kernel didn't help.)
Some information about my system:
I've got a very recent install of 64-bit OpenMediaVault 2.1.19 running on ESXi 6.0. I'm passing through an LSI SAS 9207-8i, which is connected to eight 3TB disks. I created the filesystem after completely updating OMV, so all of the versions and settings have been thus:
Zitatroot@omv:~# uname -a
Linux omv 3.2.0-4-amd64 #1 SMP Debian 3.2.68-1+deb7u6 x86_64 GNU/Linux
Zitatroot@omv:~# apt-cache show e2fsprogs
Package: e2fsprogs
Version: 1.42.5-1.1+deb7u1
[...]
ZitatAlles anzeigenroot@omv:~# cat /etc/mke2fs.conf
[...]
ext4 = {
features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
auto_64-bit_support = 1
inode_size = 256
}
[...]
Ultimately, my question is this: is there any hope of migrating my existing, 32-bit filesystem to a 64-bit filesystem (ext4 or XFS or whatever) or am I going to need to rebuild the filesystem from scratch and re-copy the 5TiB of data back over? While the latter is a possibility, it's one I'm loathe to do because of the hardware limitations in my system make it extremely difficult—it's the primary reason I started with four disks and expanded to eight in the first place.
Any help would be greatly appreciated.