From: Andrew Morton <akpm@zip.com.au>
To: Derek Glidden <dglidden@illusionary.com>
Cc: linux-kernel@vger.kernel.org, bugs@linux-ide.org
Subject: Re: Random "File size limit exceeded" under 2.4
Date: Wed, 05 Dec 2001 12:19:09 -0800 [thread overview]
Message-ID: <3C0E813D.F5B1F84E@zip.com.au> (raw)
In-Reply-To: <1007573331.1809.6.camel@two>
Derek Glidden wrote:
>
> I've been experiencing random and occasional encounters with "File size
> limit exceeded" errors under 2.4 kernels when trying to make
> filesystems.
I don't know if anyone has come forth to fix this yet.
Apparently it's something to do with your shell setting
rlimits, and block devices are (bogusly) honouring those
settings.
The word is that if you log in as `root' at the login
prompt, rather than using `su', the problem goes away.
next prev parent reply other threads:[~2001-12-05 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 17:28 Random "File size limit exceeded" under 2.4 Derek Glidden
2001-12-05 20:19 ` Andrew Morton [this message]
2001-12-05 22:33 ` Miquel van Smoorenburg
2001-12-15 7:40 ` Ken Brownfield
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=3C0E813D.F5B1F84E@zip.com.au \
--to=akpm@zip.com.au \
--cc=bugs@linux-ide.org \
--cc=dglidden@illusionary.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