public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Rees <dbr@greenhydrant.com>
To: linux-kernel@vger.kernel.org
Subject: mke2fs (and mkreiserfs) core dumps
Date: Wed, 13 Mar 2002 12:31:14 -0800	[thread overview]
Message-ID: <20020313123114.A11658@greenhydrant.com> (raw)

Hi,

I've got an interesting situation here where mke2fs and mkreiserfs core dump
with the message: File size limit exceeded (core dumped)

I recently upgraded the storage device in this machine from a single IDE
disk to a mirrored RAID running off a 3ware controller.

The disk was living off the primary controller as hda, I have since moved it
to hdc and the cdrom to hda.

The kernel is 2.4.18-rc4 + Trond's NFS_ALL patch.

Some info:

# fdisk -l /dev/hdc

Disk /dev/hdc: 255 heads, 63 sectors, 4982 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/hdc1             1       638   5124703+  83  Linux
/dev/hdc2           639      4982  34893180   83  Linux
# cat /proc/partitions
major minor  #blocks  name

   8     0   97684760 sda
   8     1      16033 sda1
   8     2    1052257 sda2
   8     3   40965750 sda3
   8     4   55649160 sda4
  22     0   40020624 hdc
  22     1    5124703 hdc1
  22     2   34893180 hdc2
# mke2fs /dev/hdc1
mke2fs 1.25 (20-Sep-2001)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
641280 inodes, 1281175 blocks
64058 blocks (5.00%) reserved for the super user
First data block=0
40 block groups
32768 blocks per group, 32768 fragments per group
16032 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736

File size limit exceeded (core dumped)
#

>From dmesg:

Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 21
VP_IDE: chipset revision 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: VIA vt82c686a (rev 22) IDE UDMA66 controller on pci00:04.1
    ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio
    ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio
hda: ASUS CD-S500/A, ATAPI CD/DVD-ROM drive
hdc: Maxtor 54098U8, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
hdc: 80041248 sectors (40981 MB) w/2048KiB Cache, CHS=79406/16/63, UDMA(66)
hda: ATAPI 50X CD-ROM drive, 128kB Cache, UDMA(33)


Anyone have any ideas?  Could it be a bios setting?

Thanks,
Dave

             reply	other threads:[~2002-03-13 20:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 20:31 David Rees [this message]
2002-03-13 20:55 ` mke2fs (and mkreiserfs) core dumps Andreas Dilger
2002-03-13 21:37   ` David Rees
2002-03-13 21:54     ` Andreas Dilger
2002-03-15 23:23       ` Theodore Tso
2002-03-17  7:26         ` Andreas Dilger
2002-03-17 18:37           ` Mike Fedyk
2002-03-18  3:03             ` Andreas Dilger
2002-03-18  5:10               ` Mike Fedyk
  -- strict thread matches above, loose matches on Subject: below --
2002-03-14 18:27 Thunder from the hill
2002-06-11  2:01 cnliou
2002-06-11  5:02 ` Andreas Dilger
2002-06-11 10:32 cnliou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020313123114.A11658@greenhydrant.com \
    --to=dbr@greenhydrant.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox