I installed 4.4 on a machine that's got two RAID volumes, one of which is a bit over 2.1 terabytes. The installer had no problem. However, fsck does. Commenting out the volume in /etc/fstab, the machine will boot. The machine will mount the volume and use it. Everything seems fine except fsck, which seems, well, fscked.
When trying to run fsck, it says:
# fsck /dev/sdb1 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004) The filesystem size (according to the superblock) is 549346683 blocks The physical size of the device is 12475771 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? yes
Is there some way to build single volumes larger than 2TB? It should not be a problem with a 64 bit OS (Windows managed to do it on this hardware before I switched it over to Linux). Is there some tuning I need? Any pointers to documents or other useful references would be appreciated. Thanks for any/all help.
Dan
# fsck /dev/sdb1 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004) The filesystem size (according to the superblock) is 549346683 blocks The physical size of the device is 12475771 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? yes
Is there some way to build single volumes larger than 2TB? It should not be a problem with a 64 bit OS (Windows managed to do it on this hardware before I switched it over to Linux). Is there some tuning I need? Any pointers to documents or other useful references would be appreciated. Thanks for any/all help.
Are you using a GPT partition for that 2.x TB filesystem?
At 12:52 AM 12/12/2006, Feizhou wrote:
# fsck /dev/sdb1 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004) The filesystem size (according to the superblock) is 549346683 blocks The physical size of the device is 12475771 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? yes Is there some way to build single volumes larger than 2TB? It should not be a problem with a 64 bit OS (Windows managed to do it on this hardware before I switched it over to Linux). Is there some tuning I need? Any pointers to documents or other useful references would be appreciated. Thanks for any/all help.
Are you using a GPT partition for that 2.x TB filesystem?
I wasn't. I had let the installer set up the partition using LVM. Then I tried without LVM. No matter what I did, it went boom.
I used parted to create a gpt partition, and was able to build a clean file system that fsck doesn't get upset about.
Thanks VERY much for this info. It solved my problem.
Both anaconda and the LVM GUI created partitions that were unusable. Nice set of bugs.
On Tuesday 12 December 2006 14:43, Daniel Senie wrote:
Are you using a GPT partition for that 2.x TB filesystem?
I wasn't. I had let the installer set up the partition using LVM. Then I tried without LVM. No matter what I did, it went boom.
I used parted to create a gpt partition, and was able to build a clean file system that fsck doesn't get upset about.
Thanks VERY much for this info. It solved my problem.
Both anaconda and the LVM GUI created partitions that were unusable. Nice set of bugs.
This wasn't on the bootable drive I take it, or you wouldn't be able to boot after switching to the GPT partition table (and you would probably find it hard to switch to GPT while preserving the data anyway). If you don't really need multiple partitions on the device, you can also do away with any partitioning scheme and just create an LVM instance on the device itself.
There's a bit more info about this in the thread "Large disk support" started by me on 2006-11-28, as went through some related problems.
On Tuesday 12 December 2006 03:01, Daniel Senie wrote:
The filesystem size (according to the superblock) is 549346683 blocks The physical size of the device is 12475771 blocks
Your partitioning is messed up, most likely you have a >2TiB partition on a dos partition table (which simply won't work). You have two options for devices larger than 2TiB, 1) use gtp as the partition table type (create with parted) 2) create a lvm pv directly on the device and skip the partition table all together.
Also, why the installer happily creates these filesystems like this is beyond me...
Either the superblock or the partition table is likely to be corrupt! Abort<y>? yes
This fs is most likely lost.
Is there some way to build single volumes larger than 2TB? It should not be a problem with a 64 bit OS
It's not even a problem on 32-bit Centos, just has to be done "the right way".
/Peter
(Windows managed to do it on this hardware before I switched it over to Linux). Is there some tuning I need? Any pointers to documents or other useful references would be appreciated. Thanks for any/all help.
Dan
-
Daniel Senie -
Feizhou -
Kevan Benson -
Peter Kjellstrom