From: "Curt Hartung" <curt@northarc.com>
To: <linux-kernel@vger.kernel.org>
Subject: Raw devices broken in 2.6.1?
Date: Thu, 29 Jan 2004 17:44:01 -0500 [thread overview]
Message-ID: <01c501c3e6b9$67225f70$0700000a@irrosa> (raw)
New to the list, checked the FAQ and nothing on this. I'm using raw devices
for a large database application (highwinds-software) and under 2.4 it runs
fine, but under 2.6 I get: Program terminated with signal 25, File size
limit exceeded. (SIGXFSZ) As soon as it tries to grow the raw device pase 2G
(might be 4G, I'll go back and check)
ulimit reports: file size (blocks) unlimited
but running the process as root and setrlimit RLIMIT_FSIZE to RLIM_INFINITY
just to be sure yields the same result.
I can easily provide a short test program to trigger it, the call I'm using
is pwrite64(...);
-Curt
next reply other threads:[~2004-01-29 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-29 22:44 Curt Hartung [this message]
2004-01-30 0:38 ` Raw devices broken in 2.6.1? Andrew Morton
2004-01-30 1:30 ` Raw devices broken in 2.6.1? AND- 2.6.1 I/O degraded? Curt Hartung
2004-01-30 4:56 ` Andrew Morton
2004-01-30 6:34 ` Curt
2004-01-30 6:46 ` Andrew Morton
2004-01-30 7:13 ` Nick Piggin
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='01c501c3e6b9$67225f70$0700000a@irrosa' \
--to=curt@northarc.com \
--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