From: Christoph Lameter <cl@linux.com>
To: Tharindu Rukshan Bamunuarachchi <btharindu@gmail.com>
Cc: hughd@google.com, linux-mm@kvack.org
Subject: Re: TMPFS Maximum File Size
Date: Wed, 20 Oct 2010 09:14:22 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1010200912270.23605@router.home> (raw)
In-Reply-To: <AANLkTikn_44WcCBmWUW=8E3q3=cznZNx=dHdOcgZSKgH@mail.gmail.com>
On Wed, 20 Oct 2010, Tharindu Rukshan Bamunuarachchi wrote:
> Is there any kind of file size limitation in TMPFS ?
> Our application SEGFAULT inside write() after filling 70% of TMPFS
> mount. (re-creatable but does not happen every time).
Please show us the console output and the backtrace for the segfault.
> We are using 98GB TMPFS without swap device. i.e. SWAP is turned off.
> Applications does not take approx. 20GB memory.
Are you sure? If it would take too much memory then we should see an OOM
though. Kernel logs would be very useful to figure out what is going on.
> we have Physical RAM of 128GB Intel x86 box running SLES 11 64bit.
> We use Infiniband, export TMPFS over NFS and IBM GPFS in same box.
> (hope those won't affect)
Interesting use case.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-10-20 14:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-20 13:44 TMPFS Maximum File Size Tharindu Rukshan Bamunuarachchi
2010-10-20 14:14 ` Christoph Lameter [this message]
2010-10-20 16:57 ` Hugh Dickins
2010-10-26 13:55 ` Tharindu Rukshan Bamunuarachchi
2010-10-27 3:44 ` Hugh Dickins
2010-10-27 20:08 ` Christoph Lameter
2010-10-28 13:35 ` Tharindu Rukshan Bamunuarachchi
2010-10-28 13:49 ` Christoph Lameter
2010-10-29 2:01 ` Tharindu Rukshan Bamunuarachchi
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=alpine.DEB.2.00.1010200912270.23605@router.home \
--to=cl@linux.com \
--cc=btharindu@gmail.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).