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
Cc: Andreas Dilger <adilger@clusterfs.com>
Subject: Re: mke2fs (and mkreiserfs) core dumps
Date: Wed, 13 Mar 2002 13:37:48 -0800	[thread overview]
Message-ID: <20020313133748.A12472@greenhydrant.com> (raw)
In-Reply-To: <20020313123114.A11658@greenhydrant.com> <20020313205537.GC429@turbolinux.com>
In-Reply-To: <20020313205537.GC429@turbolinux.com>; from adilger@clusterfs.com on Wed, Mar 13, 2002 at 01:55:37PM -0700

On Wed, Mar 13, 2002 at 01:55:37PM -0700, Andreas Dilger wrote:
> On Mar 13, 2002  12:31 -0800, David Rees wrote:
> > I've got an interesting situation here where mke2fs and mkreiserfs core dump
> > with the message: File size limit exceeded (core dumped)
> 
> This is a ulimit bug caused by the kernel and libc 2.1.  If you log into
> the system as root at the console (no su) it should work.
> 
> > The kernel is 2.4.18-rc4 + Trond's NFS_ALL patch.
> 
> I thought that the fix for this was in the 2.4.18 kernel, but I guess
> not.

Thanks for the info.  This explains why I didn't have any problems
partitioning the 3ware's RAID, I was logged into the console.

Is there anyway I can avoid logging into the console?  It can be a PITA if
the machine happens to be far away.

Thanks,
Dave

  reply	other threads:[~2002-03-13 21:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-13 20:31 mke2fs (and mkreiserfs) core dumps David Rees
2002-03-13 20:55 ` Andreas Dilger
2002-03-13 21:37   ` David Rees [this message]
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=20020313133748.A12472@greenhydrant.com \
    --to=dbr@greenhydrant.com \
    --cc=adilger@clusterfs.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