All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Worley <chrisw@lnxi.com>
To: reiserfs-list@namesys.com
Subject: Re: 2GB limit won't go away
Date: Sun, 9 Jun 2002 18:52:25 +0000 (UTC)	[thread overview]
Message-ID: <1023754048.4654.1821.camel@xserver> (raw)
In-Reply-To: <200206091608.g59G8ISI021286@turing-police.cc.vt.edu>

I'm using glibc-2.2.4-21; would that be the problem?

My ulimits:

#  ulimit -a
core file size (blocks)     0
data seg size (kbytes)      unlimited
file size (blocks)          unlimited
max locked memory (kbytes)  unlimited
max memory size (kbytes)    unlimited
open files                  1024
pipe size (512 bytes)       8
stack size (kbytes)         unlimited
cpu time (seconds)          unlimited
max user processes          8192
virtual memory (kbytes)     unlimited

Thanks,

Chris

On Sun, 2002-06-09 at 10:08, Valdis.Kletnieks@vt.edu wrote:
> On Mon, 10 Jun 2002 05:28:53 MDT, Chris Worley <chrisw@lnxi.com>  said:
> 
> > But,  I can't create a file greater than 2GB.
> 
> Two quick guesses:
> 
> 1) Old/busticated/crufty libc that doesn't have large-file support
> 1a) other userspace tools that don't have it (dd, cat, etc)
> 
> 2) a 'ulimit -f' value for max filesize.
> -- 
> 				Valdis Kletnieks
> 				Computer Systems Senior Engineer
> 				Virginia Tech
> 



  reply	other threads:[~2002-06-09 18:52 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-09  6:13 2GB limit won't go away Chris Worley
     [not found] ` <3D033CC6.70707@neuronet.pitt.edu>
2002-06-09 15:13   ` Chris Worley
2002-06-09 16:08 ` Valdis.Kletnieks
2002-06-09 18:52   ` Chris Worley [this message]
2002-06-09 18:35 ` Andreas Dilger
2002-06-09 18:55   ` Chris Worley
2002-06-09 19:16     ` Oleg Drokin
2002-06-10  2:11       ` Chris Worley
2002-06-10  4:58         ` Oleg Drokin
2002-06-10  5:42           ` Andreas Dilger
2002-06-10 14:00             ` Chris Worley
2002-06-10 14:05           ` Chris Worley
2002-06-10 14:09             ` Chris Worley
2002-06-10 16:08               ` Andreas Dilger
2002-06-10 15:47             ` Oleg Drokin

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=1023754048.4654.1821.camel@xserver \
    --to=chrisw@lnxi.com \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.