From: Andrew Morton <akpm@zip.com.au>
To: Adam McKenna <adam-dated-1010972538.f82778@flounder.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Filesystem creation problems with 2.4.17
Date: Tue, 08 Jan 2002 17:56:00 -0800 [thread overview]
Message-ID: <3C3BA330.729B06FE@zip.com.au> (raw)
In-Reply-To: <20020109014216.GB4511@flounder.net>
Adam McKenna wrote:
>
> I'm having some problems creating a large filesystem on linux kernels
> 2.4.17. I am using Debian Potato with Adrian Bunk's updates for
> running 2.4. The filesystem is approx. 260GB and is on an AMI MegaRAID
> RAID-5 stripe.
>
> ...
> write(3, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 32768)
> = -1 EFBIG (File too large)
> --- SIGXFSZ (File size limit exceeded) ---
> +++ killed by SIGXFSZ +++
Kernel bug. Apply this patch:
http://www.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.18pre2aa1/00_blkdev-ulimit-1
Or run mke2fs from a fresh root login (not via `su')
or fiddle with ulimit to set it unlimited.
-
next prev parent reply other threads:[~2002-01-09 2:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 1:42 Filesystem creation problems with 2.4.17 Adam McKenna
2002-01-09 1:56 ` Andrew Morton [this message]
2002-01-09 2:32 ` Bernd Eckenfels
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=3C3BA330.729B06FE@zip.com.au \
--to=akpm@zip.com.au \
--cc=adam-dated-1010972538.f82778@flounder.net \
--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