Skip to contentSkip to conversation

LFS stopped working

DISCUSSION Andi Kleen 3 participants 3 messages Nov 21, 2001 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu.suse.lists.linux.kernel

Andi Kleen

author
#1 lore raw
Quoted 9 lines · Alex Adriaanse

= 4095
write(1, "\0", 1) = -1 EFBIG (File too large)

killed by SIGXFSZ +++ renamed from SIGXFSZ (File size limit exceeded) --- +0 -0

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/*

-Andi

#2 lore raw
In reply to a message not in the archive
Quoted 9 lines · Andi Kleen
Quoted 8 lines · Alex Adriaanse

= 4095
write(1, "\0", 1) = -1 EFBIG (File too large)

killed by SIGXFSZ +++ renamed from SIGXFSZ (File size limit exceeded) --- +0 -0

I'm doing this on a ReiserFS filesystem, but trying it on an ext2 partition yields the same results.

Quoted 7 lines
Quoted 1 line

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/

#3 lore raw

Upgrading to Debian woody (with glibc 2.2) fixed the problem. :)

Thanks,

Alex

-----Original Message-----
From: Andreas Dilger [mailto:[email protected]]
Sent: Wednesday, November 21, 2001 11:07 AM
To: Andi Kleen
Cc: Alex Adriaanse; [email protected]
Subject: Re: LFS stopped working

Quoted 7 lines · Andi Kleen
Quoted 6 lines · Alex Adriaanse

= 4095
write(1, "\0", 1) = -1 EFBIG (File too large)

killed by SIGXFSZ +++ renamed from SIGXFSZ (File size limit exceeded) --- +0 -0

I'm doing this on a ReiserFS filesystem, but trying it on an ext2

partition

Quoted 9 lines
Quoted 3 lines

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/