From: Peter Zaitsev <peter@mysql.com>
To: linux-kernel@vger.kernel.org
Subject: Disk full and writting to pre-allocated area on ReiserFS
Date: Fri, 15 Oct 2004 14:35:58 -0700 [thread overview]
Message-ID: <1097876157.6553.22.camel@sphere.site> (raw)
Hi,
I'm running SuSE 9.1 Kernel 2.6.5-7.108-default
But I would guess it applies to large variety of platforms as we have
customers reporting the same problem.
I'm using reiserfs:
/dev/md0 on /data type reiserfs (rw,noatime,notail,data=writeback)
The problem is in case of disk full condition, "Disk full" error is
being reported even if write happens to Pre-Allocated area, in my case
to Innodb recovery log files.
This is very unfortunate as in such case Innodb has no way but to
terminate database server. These logs are specially pre-allocated so
one would not run in such condition.
Question: Is there any way to avoid this problem with Reiserfs ?
--
Peter Zaitsev, Senior Support Engineer
MySQL AB, www.mysql.com
next reply other threads:[~2004-10-15 21:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 21:35 Peter Zaitsev [this message]
2004-10-16 15:22 ` Disk full and writting to pre-allocated area on ReiserFS Hans Reiser
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=1097876157.6553.22.camel@sphere.site \
--to=peter@mysql.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