Terry, Did you CMS format this disk before using it with Linux? If so, that's your problem. Do a manual dasdfmt, using -b 4096, followed by mke2fs -b 4096, and you'll probably be fine.
Mark Post -----Original Message----- From: Terrance Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 4:15 PM To: [EMAIL PROTECTED] Subject: Re: Maximum DASD size I actually formatted this volume twice using YaST, maybe there is a better way. Or should I change the blocksize or something? I'll attempt to do it manuallu using dasdfmt Regards Terry -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED]]On Behalf Of Post, Mark K Sent: Tuesday, March 12, 2002 4:02 PM To: [EMAIL PROTECTED] Subject: Re: Maximum DASD size Terry, During the Redbook residency, I did a test with creating a large LVM set using 3 3390-9 volumes. I did have a couple of quirky things happen, but nothing consistent, and nothing that looks like your problem. When you did your dasdfmt command, how long did it take to complete? (It should have taken a _long_ time, about 45 minutes or so.) Mark Post -----Original Message----- From: Terrance Smith [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 1:55 PM To: [EMAIL PROTECTED] Subject: Maximun DASD size I have a Suse 2.2.16 and 2.4.7 Linux systems that I need to assign several Gigabytes to for oracle databases, I have 3390 mod 9s and the 2.4.7 seems to allow this but my 2.2.16 system gives the following errors during initialization fsck /dev/dasdf1 , Parallelizing fsck version 1.19a (13-Jul-2000) , e2fsck 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09 , /dev/dasdf1 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes , Pass 1: Checking inodes, blocks, and sizes , Inode 635233 has imagic flag set. Clear<y>?, yes , Inode 635234 is in use, but has dtime set. Fix<y>? yes , Inode 635235 is in use, but has dtime set. Fix<y>? yes , Inode 635235 has imagic flag set. Clear<y>? yes , Inode 635236 is in use, but has dtime set. Fix<y>?,y, Inode 635236 has imagic flag set. Clear<y>? yes , Inode 635237 is in use, but has dtime set. Fix<y>?,y, Inode 635237 has imagic flag set. Clear<y>? yes , Inode 635238 is in use, but has dtime set. Fix<y>?,yes , Special (device/socket/fifo) inode 635238 has non-zero size. Fix<y>? yes Inode 635239 is in use, but has dtime set. Fix<y>?,y, Inode 635239 has imagic flag set. Clear<y>? yes , . . Inode 635315 has imagic flag set. Clear<y>? yes , , Inode 635316 is in use, but has dtime set. Fix<y>? this seems to go on forever, and I've attempted to format this volume several times. So, is there a maximum volume size for 2.2.16 and what about 2.4.7 and what is the fastest and most reliable way to append these together; LVM or RAID and is this version related? Regards Terry
