You are using 32 OMV 2.x? If so, it is just an old ext library. Boot systemrescuecd or gparted-live on the system to fix.
Warning here, if the 64bit flag is not present in the fs, there no other way but to reformat. If the flag is there you should be able to do as @ryecoaaron says and use another distro to expand.
Where/when did you format this array in the beginning ?
Warning here, if the 64bit flag is not present in the fs, there no other way but to reformat.
His filesystem is already over the 16tb limit of the 32bit flag. I think this is an e2fslibs version being to old issue.
You are using 32 OMV 2.x? If so, it is just an old ext library. Boot systemrescuecd or gparted-live on the system to fix.
I use the x64 install option i think.
I "solfed" my problem in that way that i complete reinstall the server.. i had some missconfiguratiosn and some design-misstages in the first install. So i installed it completly new.
But.... i'm afraid i will have this poblem agoin in some week/mounth when i install the last two 8TB HDD into this server.
Now i'm 100% sure that i use the x64 version of OMV 2.x
So is it the way for expanding the filesystem i have installed by using OVM only with a linux live CD?! You must be joking..
So is it the way for expanding the filesystem i have installed by using OVM only with a linux live CD?! You must be joking..
At some point, an old operating system designed to be super stable cannot have the latest code that can handle new software. 64 bit OMV 3.x will not have this issue. Also, xfs would never have this issue since it has always been a 64 bit filesystem. If you plan on having a filesystem this large (not typical), some research needs to be done.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!
