From: Andreas Dilger <adilger@turbolabs.com>
To: Jean-Luc Coulon <jean-luc.coulon@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.16-pre1 : e2fsck, File size limit exceeded (core dumped)
Date: Sun, 25 Nov 2001 15:17:56 -0700 [thread overview]
Message-ID: <20011125151756.C712@lynx.no> (raw)
In-Reply-To: <3C00EEA0.F43E95AA@wanadoo.fr>
In-Reply-To: <3C00EEA0.F43E95AA@wanadoo.fr>; from jean-luc.coulon@wanadoo.fr on Sun, Nov 25, 2001 at 02:14:08PM +0100
On Nov 25, 2001 14:14 +0100, Jean-Luc Coulon wrote:
> I've two partitions. /dev/hda1 where I can boot 2.2.20 or 2.4.16-pre1,
> /dev/hda3 with only 2.4.16-pre1.
>
> Now, if I boot 2.4.16-pre1, I have the following :
>
> e2fsck 1.25 (20-Sep-2001)
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> /dev/hda3: 79176/250368 files (1.5% non-contiguous), 277317/500023
> blocks
> File size limit exceeded (core dumped)
This is a kernel bug. It can be avoided by running as a user with no
filesystem limits. Note that _any_ call to "ulimit" is currently
broken, especially "ulimit -f unlimited", which will actually impose
a 2GB file limit on the block device. Remove any "ulimit" statements
from the system startup or root .bash* scripts, and you should be OK.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
prev parent reply other threads:[~2001-11-25 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-25 13:14 2.4.16-pre1 : e2fsck, File size limit exceeded (core dumped) Jean-Luc Coulon
2001-11-25 22:17 ` Andreas Dilger [this message]
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=20011125151756.C712@lynx.no \
--to=adilger@turbolabs.com \
--cc=jean-luc.coulon@wanadoo.fr \
--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