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 -- ----------------------------------------------------------------- Daniel Senie dts at senie.com Amaranth Networks Inc. http://www.amaranth.com "George Orwell was only off by 20 years. Had he titled his book 2004 instead of 1984, he'd have been hailed as prescient. War is Peace. Freedom is Slavery. Ignorance is Strength." -dts
> # 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? http://www.wlug.org.nz/GPT
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 blocksYour 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>? yesThis 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 OSIt'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-- ------------------------------------------------------------ Peter Kjellstr?m | E-mail: cap at nsc.liu.se National Supercomputer Centre | Sweden | http://www.nsc.liu.se -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20061212/7fd4c737/attachment.sig>