Kris,
It looks like you have exceeded the superblock size or maximum size
of your disk size. What block size did you select when you tried mke2fs?
I do not see any size limitations for mke2fs in the man. Perhaps one of the
higher ups could help. Also how much memory do you have in the system?
Maybe it can't allocate enough memory for caching the directory structure.
(.02)
Rgds, Andy
<snip>
Subject: Need help on linux running a single 130GB hard drive...
> his is a little out of the topic area but directly related to High-Avail. I have a
> customer that I am trying to get 130GB drive to work with a Linux redhat 5.1
> system and 5.2 system and am having two different but very nasty problems,
> can anybody help?
>
>
> >>>>
>
>
> I have two seperate things going on, they are;
>
> 1) useing Red Hat Linux release 5.1 (Manhattan) Kernel 2.0.35 on an i686,
> this is from the log loading the drivers for the qlogic board...
> --------------------------------------------------------------------------
> Dec 8 12:07:15 newman kernel: isp0: Board Revision 1040B, loaded F/W
> Revision 7.55
> Dec 8 12:07:15 newman kernel: isp0: Last F/W revision was 4.50
> Dec 8 12:07:15 newman kernel: scsi2 : Driver for a Qlogic 1XX0 SCSI
> Adapter
> Dec 8 12:07:15 newman kernel: scsi : 3 hosts.
> Dec 8 12:07:18 newman kernel: Vendor: LAND-5 Model: ICEbox DS-
> 2000 Rev: 0211
> Dec 8 12:07:18 newman kernel: Type: Direct-Access ANSI
> SCSI revision: 02
> Dec 8 12:07:18 newman kernel: Detected scsi disk sdd at scsi2, channel 0,
> id 1, lun 0
> Dec 8 12:07:21 newman kernel: SCSI device sdd: hdwr sector= 512 bytes.
> Sectors= 266746560 [130247 MB] [13
> 0.2 GB]
> Dec 8 12:07:21 newman kernel: sdd: sdd1
> Dec 8 12:10:21 newman kernel: SCSI device sdd: hdwr sector= 512 bytes.
> Sectors= 266746560 [130247 MB] [13
> 0.2 GB]
> Dec 8 12:10:21 newman kernel: sdd:
> Dec 8 12:10:23 newman kernel: SCSI device sdd: hdwr sector= 512 bytes.
> Sectors= 266746560 [130247 MB] [13
> 0.2 GB]
> Dec 8 12:10:23 newman kernel: sdd:
> Dec 8 12:12:46 newman kernel: SCSI device sdd: hdwr sector= 512 bytes.
> Sectors= 266746560 [130247 MB] [13
> 0.2 GB]
> Dec 8 12:12:46 newman kernel: sdd: sdd1
> Dec 8 12:12:48 newman kernel: SCSI device sdd: hdwr sector= 512 bytes.
> Sectors= 266746560 [130247 MB] [13
> 0.2 GB]
> Dec 8 12:12:48 newman kernel: sdd: sdd1
> -----------------------------------------------------------------------------------
> "Exerpt"
>
> Dec 8 15:04:02 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Block #253 of the i
> node table in group 0 is marked free
> Dec 8 15:04:02 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Block #254 of the i
> node table in group 0 is marked free
> Dec 8 15:04:02 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Block #255 of the i
> node table in group 0 is marked free
> Dec 8 15:04:02 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Wrong free blocks c
> ount for group 0, stored = 7411, counted = 8192
> Dec 8 15:04:02 newman kernel: is marked free
> Dec 8 15:04:02 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Block #186 of the i
> node table in group 1 is marked free
>
> **** THIS goes on fro hundreds of lines *****
>
> Dec 8 15:24:29 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Block #253 of the i
> node table in group 12218 is marked free
> Dec 8 15:24:29 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Block #254 of the i
> node table in group 12218 is marked free
> Dec 8 15:24:30 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Block #255 of the i
> node table in group 12218 is marked free
> Dec 8 15:24:30 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Wrong free blocks c
> ount for group 12218, stored = 7424, counted = 8192
> Dec 8 15:27:00 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_blocks_bitmap: Wrong free blocks
>
> ***** THEN this *****
>
> count in super block, stored = 120867776, counted = 130251981
> Dec 8 15:27:00 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_inodes_bitmap: Wrong free inodes c
> ount in group 0, stored = 2037, counted = 2048
> Dec 8 15:36:16 newman kernel: EXT2-fs error (device 08:31):
> ext2_check_inodes_bitmap: Wrong free inodes c
> ount in super block, stored = 33343477, counted = 33343488
>
> *** THEN **** This is in the middle of doing a FSCK as seen below in the
> process outline...
>
> Dec 8 19:12:30 newman PAM_pwdb[1392]: (su) session opened for user
> root by kland(uid=0)
> Dec 8 19:16:11 newman kernel: scsi2 channel 0 : resetting for second half
> of retries.
> Dec 8 19:16:11 newman kernel: SCSI bus is being reset for host 2 channel
> 0.
> Dec 8 19:16:19 newman kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
> return code = 26030000
> Dec 8 19:16:19 newman kernel: scsidisk I/O error: dev 08:31, sector
> 221889536, absolute sector 221889599
> Dec 8 19:16:19 newman kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
> return code = 26030000
> Dec 8 19:16:19 newman kernel: scsidisk I/O error: dev 08:31, sector
> 221905920, absolute sector 221905983
> Dec 8 19:16:19 newman kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
> return code = 26030000
> Dec 8 19:16:19 newman kernel: scsidisk I/O error: dev 08:31, sector
> 221922304, absolute sector 221922367
> Dec 8 19:16:27 newman kernel: scsi2 channel 0 : resetting for second half
> of retries.
> Dec 8 19:16:27 newman kernel: SCSI bus is being reset for host 2 channel
> 0.
> Dec 8 19:16:33 newman kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
> return code = 26030000
> Dec 8 19:16:33 newman kernel: scsidisk I/O error: dev 08:31, sector
> 221971456, absolute sector 221971519
> Dec 8 19:16:33 newman kernel: SCSI disk error : host 2 channel 0 id 1 lun 0
> return code = 26030000
> Dec 8 19:16:33 newman kernel: scsidisk I/O error: dev 08:31, sector
> 221987840, absolute sector 221987903
> Dec 8 19:18:37 newman PAM_pwdb[1392]: (su) session closed for user
> root
> ------------------------------------------------------------------------------------
>
> ******** Add'l info *******
>
> [root@newman log]# df
> Filesystem 1024-blocks Used Available Capacity Mounted on
> /dev/sda1 101075 25515 70341 27% /
> /dev/sda9 995115 2526 941183 0% /home
> /dev/sda8 995115 16 943693 0% /tmp
> /dev/sda7 1981000 694721 1183867 37% /usr
> /dev/sda6 1981000 110408 1768180 6% /var
> /dev/sda11 132185 17 125342 0% /var/named
> /dev/sda10 132185 60 125299 0% /var/spool/mail1
> /dev/sda5 2152074 13 2040813 0% /var/spool/mqueue
> /dev/sdb1 7932792 943518 6578012 13% /alt
> /dev/sdc1 8566007 44 8121768 0% /var/spool/mail
> /dev/sdd1 120867789 13 114199197 0% /big
>
> [root@newman log]# ps
> PID TTY STAT TIME COMMAND
> 444 1 S 0:00 (mingetty)
> 445 2 S 0:00 /sbin/mingetty tty2
> 446 3 S 0:00 /sbin/mingetty tty3
> 447 4 S 0:00 /sbin/mingetty tty4
> 448 5 S 0:00 /sbin/mingetty tty5
> 449 6 S 0:00 /sbin/mingetty tty6
> 1173 p1 S 0:00 su -
> 1174 p1 S 0:00 -bash
> 1226 a0 S 0:00 su
> 1227 a0 S 0:00 bash
> 1262 p1 S 0:00 fsck /dev/sdd1
> 1263 p1 D 8:38 fsck.ext2 /dev/sdd1
> 1278 p2 S 0:00 su -
> 1279 p2 S 0:00 -bash
> 1329 a0 S 0:00 man mkfs
> 1330 a0 S 0:00 sh -c (cd /usr/man ; (echo -e ".pl 1100i"; cat
> /usr/man/man8/mkfs.8) | /usr/bin/gtbl |
> 1331 a0 S 0:00 sh -c (cd /usr/man ; (echo -e ".pl 1100i"; cat
> /usr/man/man8/mkfs.8) | /usr/bin/gtbl |
> 1336 a0 S 0:00 /usr/bin/less -is
> 1495 p3 S 0:00 su -
> 1496 p3 S 0:00 -bash
> 1511 p3 R 0:00 ps
>
> <<<<
>
> The machine stayed locked running FSCK here is what the log fie said
> before the machine got rebooted, sigh....
> ------------------
> Your file system creation and subsequent fsck operation did not
> yield a working disk. Here is a log of an attempt to run fsck
> on the disk array as I found it:
>
> Script started on Thu Dec 10 02:16:26 1998
>
> [root@newman notepad]# /sbin/fsck /dev/sdd
> Parallelizing fsck version 1.10 (24-Apr-97)
> e2fsck 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
> Couldn't find ext2 superblock, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/sdd
>
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
> e2fsck -b 8193 <device>
>
> [root@newman notepad]# /sbin/fsck -b 8193 /dev/sdd
> Parallelizing fsck version 1.10 (24-Apr-97)
> e2fsck 1.10, 24-Apr-97 for EXT2 FS 0.5b, 95/08/09
> fsck.ext2: Bad magic number in super-block while trying to open /dev/sdd
>
> The superblock could not be read or does not describe a correct ext2
> filesystem. If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
> e2fsck -b 8193 <device>
>
> Command exited with non-zero status 8
>
> >>>
>
>
>
>----------------------------------------------------------------------------------------
>
>
> 2) Subject: Redhat 5.2 Linux Install Failure Info
>
> boot:
> Loading initrd.img.............
> Loading vmlinuz................
> uncompressing Linux..., done.
> Now booting the kernel
> Memory: sized by int13 0e801h
> Console: 16 point font, 400 scans
> Console: colour VGA+ 80 x 25, 1 virtual console (max63)
> pcibios_init : BIOS32 Service Directory structure at
> 0x000fdb50
> pcibios_init : BIOS32 Service Directory entry at 0xfd
> pcibios_init : PCI BIOS revision 2.10 entry at 0xfdb81
> Probing PCI hardware.
> Calibrating delay loop.. ok - 450.56 BogoMIPs
> initrd overwritten (0x00e00000 < 0x01014e78) - disabling it
> Memory : 1032740k/1048576k available (708k kernel code,
> 384k reserved, 14744k data)
> Bad pmd in pte_alloc : 008000e7
> Kernel panic: Failed to allocate buffer hash table
>
> In swapper task - not syncing
>
>
> ------------------------------------------------------------------------------
>
>
> Thanks again! Kris
>
>
>
>
> - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the
> body of a message to [EMAIL PROTECTED]
***************************************************************************************
Andrew B. Cramer
<[EMAIL PROTECTED]> <http://www.cramer-ts.com>
The Linux Resource Exchange <http://www.linuxrx.com>
Member - HTML Writers Guild - Netware Users International
If you don't have time to do it right, when are you going to find time to do it over?
The use of SPAM should come with a death sentence.
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
