public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@turbolabs.com>
To: Andi Kleen <ak@suse.de>
Cc: Alex Adriaanse <alex_a@caltech.edu>, linux-kernel@vger.kernel.org
Subject: Re: LFS stopped working
Date: Wed, 21 Nov 2001 12:07:18 -0700	[thread overview]
Message-ID: <20011121120718.R1308@lynx.no> (raw)
In-Reply-To: <JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu.suse.lists.linux.kernel> <p737kss7eia.fsf@amdsim2.suse.de>
In-Reply-To: <p737kss7eia.fsf@amdsim2.suse.de>; from ak@suse.de on Thu, Nov 15, 2001 at 07:08:13AM +0100

On Nov 15, 2001  07:08 +0100, Andi Kleen wrote:
> "Alex Adriaanse" <alex_a@caltech.edu> writes:
> > = 4095
> > write(1, "\0", 1)                       = -1 EFBIG (File too large)
> > --- SIGXFSZ (File size limit exceeded) ---
> > +++ killed by SIGXFSZ +++
> > 
> > I'm doing this on a ReiserFS filesystem, but trying it on an ext2 partition
> > yields the same results.
> > 
> > Any suggestions?
> 
> ulimit -f unlimited.
> 
> SIGXFSZ means you exceeded your quota. Somehow you managed to set your 
> file size quotas to 2GB. Set them to unlimited instead. It could be caused
> by same PAM module; e.g. pam_limits, check /etc/security/*

The problem is that the old getrlimit() syscall returns a max of 0x7fffffff
for the limit, while the kernel uses 0xffffffff for unlimited, so if you
do "setrlimit(getrlimit())" you may actually be going from a real unlimited
ulimit, to a "bogus" unlimited limit that the kernel will deny you on.

I think the fix is to simply ignore file limits when writing to block
devices.

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/


  reply	other threads:[~2001-11-21 19:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu.suse.lists.linux.kernel>
2001-11-15  6:08 ` LFS stopped working Andi Kleen
2001-11-21 19:07   ` Andreas Dilger [this message]
2001-11-21 20:06     ` Alex Adriaanse
2001-11-14 22:05 Alex Adriaanse
2001-11-15  2:58 ` Ben Collins
2001-11-15  6:29   ` Alex Adriaanse
2001-11-15  9:38 ` Andreas Jaeger
2001-11-15 10:03   ` Alex Adriaanse
2001-11-15 10:42     ` Andreas Jaeger
2001-11-15 11:57       ` Alex Adriaanse

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=20011121120718.R1308@lynx.no \
    --to=adilger@turbolabs.com \
    --cc=ak@suse.de \
    --cc=alex_a@caltech.edu \
    --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