public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alex Adriaanse" <alex_a@caltech.edu>
To: <linux-kernel@vger.kernel.org>
Subject: LFS stopped working
Date: Wed, 14 Nov 2001 14:05:21 -0800	[thread overview]
Message-ID: <JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu> (raw)

Hey,

I've been running 2.4.14 for a few days now.  I needed LFS support, so I
recompiled glibc 2.1.3 with the new 2.4 headers, and after that I could
create large files (e.g. using dd if=/dev/zero of=test bs=1M count=0
seek=3000) just fine.

However, as of yesterday, I couldn't create files bigger than 2GB anymore.
I did not change kernels, nor did I mess with libc or anything else (I did
some Debian package upgrades/installations/recompiles, but I don't think
they should affect this) - I'm not quite sure what happened.  Now commands
such as the dd command I mentioned above will die with the message "File
size limit exceeded", leaving a 2GB file behind.  Rebooting didn't solve
anything.  My ulimits seem to be fine (file size = unlimited).

The last few lines of the strace on the dd command above shows the
following:
open("/dev/zero", O_RDONLY|0x8000)      = 0
close(1)                                = 0
open("test", O_RDWR|O_CREAT|0x8000, 0666) = 1
ftruncate64(0x1, 0xbb800000, 0, 0, 0x1) = 0
--- SIGXFSZ (File size limit exceeded) ---
+++ killed by SIGXFSZ +++

Also, cat'ing two 2GB files together into one big 4GB file (cat file1 file2
> file3) just dies after creating a 2GB file, whereas it used to work fine
(if I remember correctly).  Doing an strace on it ends with the following
lines:
write(1, "\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"..., 4096)
= 4096
read(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"..., 4096) =
4096
write(1, "\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"..., 4096)
= 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?

Thanks,

Alex


             reply	other threads:[~2001-11-14 22:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-14 22:05 Alex Adriaanse [this message]
2001-11-15  2:58 ` LFS stopped working 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
     [not found] <JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu.suse.lists.linux.kernel>
2001-11-15  6:08 ` Andi Kleen
2001-11-21 19:07   ` Andreas Dilger
2001-11-21 20:06     ` 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=JIEIIHMANOCFHDAAHBHOOEOLCMAA.alex_a@caltech.edu \
    --to=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