> i guess my thinking is more along the lines of implementing
> a lustre interface
I'm sure that I'm vastly over-simplifying this, but I was thinking something
along the lines of:
1. Assemble the data being written, calculate its length
2. Check for any free pages in the database file, and use
mysql@lists.mysql.com
> Subject: Re: Database Quotas
>
> > if MYSQL attempts to insert more bytes than what is available
> > on disk you will get 28 ENOSPC No space left on device
> > http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
>
>
I ran out of space on a large, busy production database just a few weeks
ago. All tables are InnoDB and I experienced zero data loss.
It was actually running out of space for almost 2 weeks after a review of
the log file. As temp files were deleted transactions were able to continue
until all but
> if MYSQL attempts to insert more bytes than what is available
> on disk you will get 28 ENOSPC No space left on device
> http://dev.mysql.com/doc/refman/5.0/en/operating-system-error-codes.html
Does it figured that out before it tries to write a record? So, if I have 2KB
left on the device an
nt facilement être sujets à la manipulation, nous ne
pouvons accepter aucune responsabilité pour le contenu fourni.
> Date: Thu, 20 May 2010 18:09:42 -0700
> From: t...@soe.ucsc.edu
> To: noel.but...@ausics.net
> CC: mysql@lists.mysql.com
> Subject: Re: Database Quotas
>
> >
> First, generally speaking, putting a quota on an entire database means
> you are probably doing it wrong. In a perfect world, it seems to be
> that building a database which can maintain a size without constant
> mothering would be best, this doesn't always happen for one reason
> or another, but
Tim Gustafson wrote:
Hi,
I'm not sure if this is already an open issue or not - a Google search resulted
in various discussions but I didn't find any open support/feature request.
It would be really handy if during the "create database" statement, one could
specify something like:
CREATE DAT
On May 20, 2010 09:55:41 pm Tim Gustafson wrote:
> > Use postgres, you can assign tablespaces to a partition
> > of the size you want. When it gets full, writes are
> > refused. I'm not sure how nicely that is handled ( in
> > terms of error output ) but the advantage is that Pg is
> > ACID compli
> Use postgres, you can assign tablespaces to a partition
> of the size you want. When it gets full, writes are
> refused. I'm not sure how nicely that is handled ( in
> terms of error output ) but the advantage is that Pg is
> ACID compliant, so you won't lose data.
Wow, that's the first time I'
On May 20, 2010 08:32:56 pm Noel Butler wrote:
> On Thu, 2010-05-20 at 16:27 -0700, Tim Gustafson wrote:
> > Hi,
> >
> > I'm not sure if this is already an open issue or not - a Google search
> > resulted in various discussions but I didn't find any open
> > support/feature request.
> >
> > It w
> Ummm, you're going to have the same problem either way when
> the limit is reached, be it a MySQL quota or system quota,
> if its full, its full.
Yes, but mySQL could return a more friendly "you're out of space" message and
not corrupt the data files if a given statement would cause the databas
On Thu, 2010-05-20 at 16:27 -0700, Tim Gustafson wrote:
> Hi,
>
> I'm not sure if this is already an open issue or not - a Google search
> resulted in various discussions but I didn't find any open support/feature
> request.
>
> It would be really handy if during the "create database" statemen
Hi,
I'm not sure if this is already an open issue or not - a Google search resulted
in various discussions but I didn't find any open support/feature request.
It would be really handy if during the "create database" statement, one could
specify something like:
CREATE DATABASE foo QUOTA=10G;
t
Another way I was thinking about by now is to periodically calculate the
database's size and, if over quota, revoke the user's INSERT, UPDATE rights
and so on.
It's not real-time, too, but maybe a little more friendly since I don't know
how MySQL behaves when running against fs quota writing to a f
25, 2003 3:11 AM
Subject: Re: Database quotas?
> On Wed, Sep 24, 2003 at 03:18:07PM +1000, [EMAIL PROTECTED] wrote:
> > Yeah but when they make a nwe table, it will be owned by root.root wont
it?
>
> First, don't run MySQL as root.
>
> Second, yes. It will be owned by wh
On Wed, Sep 24, 2003 at 03:18:07PM +1000, [EMAIL PROTECTED] wrote:
> Yeah but when they make a nwe table, it will be owned by root.root wont it?
First, don't run MySQL as root.
Second, yes. It will be owned by whoever creates it. But a periodic cron
job to chorwn them appropriately would be a r
Yeah but when they make a nwe table, it will be owned by root.root wont it?
> On Wed, Sep 24, 2003 at 01:38:43PM +1000, [EMAIL PROTECTED] wrote:
>> Hey guys,
>>
>> is it possible to bind some databases to a userid so u can do disk
>> quotas on them, or limit how big a db can be?
>
> chown the file
On Wed, Sep 24, 2003 at 01:38:43PM +1000, [EMAIL PROTECTED] wrote:
> Hey guys,
>
> is it possible to bind some databases to a userid so u can do disk quotas
> on them, or limit how big a db can be?
chown the files. Just make sure they're group-wrtiable so that MySQL can
write to 'em.
--
Jeremy
Hey guys,
is it possible to bind some databases to a userid so u can do disk quotas
on them, or limit how big a db can be?
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
19 matches
Mail list logo
