We have had problems with any filesystem larger than 1 TB. Although I have been assured that there are no problems with large filesystems, we can create a 1 TB filesystem, and things work fine... create it a megabyte over, and it seems to go fine, but when you start writing to the filesystem, it starts getting I/O errors. I seem to remember getting the answer that fdisk and parted cannot create LUNs larger than 1 TB, so the filesystems built on top of these LUNs have problems. I think I was told that I would have to create LUNs on the arrays smaller than 1 TB, and use LVM to create a logical volume to get the larger size.... I also think this was supposed to be fixed (at least parted, didn't hear anything about fdisk) in an upcoming release ? Do you know if this was fixed in 9.1 ? Thanks, Kevin Kevin Gassiot Advanced Systems Group Visualization Systems Support Veritas DGC 10300 Town Park Dr. Houston, Texas 77072 832-351-8978 kevin_gassiot@veritasdgc.com Andi Kleen <ak@suse.de> To 05/05/2004 01:14 Eugene Chu AM <chu@tes-mail.jpl.nasa.gov> cc suse-amd64@suse.com Subject Re: [suse-amd64] Max FS size?
I did not have the chance to swap the different types of RAIDs between the two systems, so I can not tell if the differences I saw were from the different device drivers used to talk to each system, or if they were caused by one OS not being able to properly address a disk that's greater than 1 TB. Does anyone have the definitive answer?
The 64bit OS can address more and the file systems can too. Your problems are most likely caused by the Adaptec device driver or the RAID firmware. -Andi -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com