From: Marc MERLIN <marc_lvm@merlins.org>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Can't mke2fs lv
Date: Mon Feb 11 14:25:01 2002 [thread overview]
Message-ID: <20020211202503.GA22401@merlins.org> (raw)
In-Reply-To: <20020211130701.J9826@lynx.turbolabs.com>
On Mon, Feb 11, 2002 at 01:07:01PM -0700, Andreas Dilger wrote:
> > Unfortunately, that's not it, the machine doens't have any users, and I
> > ssh'ed in as root
>
> It could still be that the ssh process inherits the ulimit from its parent.
> The real problem with this bug is that "ulimit -f" returns "unlimited", but
> in fact it is really 2GB. The user tools think 2GB is unlimited, but the
> kernel thinks 4GB is unlimited. This assumes you don't have a ulimit set
> at some value less than 2GB.
Well, I didn't set the ulimit, but sure enough, something did.
After upgrading from bash 2.04 to bash 2.05 and from ssh 2.5.x to 3.0.x, I
got:
gargamel:~# ulimit -f
2097151
I am not setting this in /etc/security/limits.conf, so something else
probably is.
Either way, after
gargamel:~# ulimit -f unlimited
it works like a charm
> I _thought_ that glibc-2.2 was not affected by this problem, but it
> could be that if you have an old shell which uses the old getrlimit
> syscall it will still break your system.
I don't know if bash 2.05 is considered old or not, but it's true that the
ulimit could be set by anything along the chain.
I haven't upgraded e2fsprogs yet, but if it tries to reset the filesize
limit to unlimited, it would definitely fix the problem I had.
Anyway, it's all working now.
Thanks a lot,
Marc
--
Microsoft is to operating systems & security ....
.... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ | Finger marc_f@merlins.org for PGP key
prev parent reply other threads:[~2002-02-11 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 11:34 [linux-lvm] Can't mke2fs lv Marc MERLIN
2002-02-11 12:11 ` Heinz J . Mauelshagen
2002-02-11 12:30 ` Marc MERLIN
2002-02-11 14:08 ` Andreas Dilger
2002-02-11 14:25 ` Marc MERLIN [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=20020211202503.GA22401@merlins.org \
--to=marc_lvm@merlins.org \
--cc=linux-lvm@sistina.com \
/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;
as well as URLs for NNTP newsgroup(s).