search for: 2.2tb

I have an Infortrend RAID box I'd like to see as one big 6TB partition, but I only can get 2.2TB partitions to work. I was trying to do this with an Adaptec controller but apparently they are only (any of them) 48 bits wide. Does anybody have a working system for SCSI/Centos over 2.2TB? Milt Mallory Topix.com 650-461-8316 Always consider the issues of progressive enhancement and

We recently bought a 32-bit Xeon system with a 12-port 3Ware RAID card and a dozen 500GB drives. We wanted to create 4TB drive arrays; however, we soon discovered that there is about a 2.2TB drive array size limit on 32-bit hardware. Does that sound correct? Would replacing the 32-bit mobo/cpu with a 64-bit mobo/cpu allow us to use drive arrays larger than 2.2TB? Thanks.

I really hope someone has a clue on this one.... :) I've got a 2.2TB array mounted on a 3ware 9500 controller. I installed it last week ensuring that LBA was enabled and using gpt with parted to get the full size available on one array. I also think I chose reiserfs for the array. We then moved ALOT of data to the array. Problem now is that after a reboot LBA doesn't seem to be in

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I installed centos4 on a raid system with 7 400GB Hitachi SATA disks in RAID 5 on the 3Ware card. I set up a 2.2TB EXT3 Partition /opt. After the install I rebooted and the system went straight into maintenance mode....! The system reported a problem with /opt, but I was able to mount it manually and init 4 with no problems. However a reboot dropped

From: Mark Jarvis <mark.jarvis at pvmail.maricopa.edu> > HUH? FAT32 problem??? No, it's a geometry issue on legacy BIOS/DOS Disk Labels (Partition Table Format) aka "Basic Disc" in NT5+ (2000+) when both NT and Linux share the disk for booting. Microsoft never standardized how geometry should be handled after NT4.0 Service Pack 4 (SP4) other than using legacy LBA32 --

I tried this on the IRC channel and got not response... I have a 2.2TB filesystem. The filesystem itself is a stornext (Quantum) filesystem, which in the /etc/fstab is type cvfs. When a client mounts the samba share, it only reports ~4GB (3.9 or 3.7 GB) total space. We have a third party app, which will/can not be updated which checks the disk space available and fails if it's not enough.