From: Erik Jones <erik@myemma.com>
To: Jeff Frost <jeff@frostconsultingllc.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: General Postgresql List <pgsql-sql@postgresql.org>
Subject: Re: Disk is full, what's cool to get rid of?
Date: Thu, 27 Jul 2006 15:00:03 -0500
Message-ID: <44C91B43.3080901@myemma.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0607271236090.11632@discord.home.frostconsultingllc.com>
References: <44C8E7EB.3040608@myemma.com>
<Pine.LNX.4.64.0607270931280.11632@discord.home.frostconsultingllc.com>
<1154025714.31664.95.camel@state.g2switchworks.com>
<44C91390.7030206@myemma.com>
<Pine.LNX.4.64.0607271236090.11632@discord.home.frostconsultingllc.com>
Awesome. Makes sense as 5% is exactly the amount of space that appeared
after running it. Thanks!
Jeff Frost wrote:
> Depends what the default is on your system. The default is 5% with
> the version of mke2fs that I have here, so you would just:
>
> tune2fs -m 5 <devicename>
>
> to put it back.
>
> On Thu, 27 Jul 2006, Erik Jones wrote:
>
>> Awesome. Do I need to reset that to any magic # after the vacuum?
>> I'm not all that up on filesystem maintenance/tweaking...
>>
>> Scott Marlowe wrote:
>>> I can't tell you the number of times that little trick has saved my
>>> life.
>>>
>>> On Thu, 2006-07-27 at 11:32, Jeff Frost wrote:
>>>
>>>> You can probably just "tune2fs -m 0 <device name>" to give yourself
>>>> enough space to get out of the jam before you go deleting things.
>>>> Then you might want to vacuum full afterwards.
>>>>
>>>> On Thu, 27 Jul 2006, Erik Jones wrote:
>>>>
>>>>
>>>>> Hello, quick question. I've run into an issue with the disk that
>>>>> my development box is on filling up and preventing pretty much any
>>>>> writing (inserts, updates, deletes, etc...) from happening. Other
>>>>> than some piddly text logs the db is pretty much the only thing on
>>>>> the box. So, my question is: what can I do to free space and run
>>>>> a full vacuum? (I was not the one who set up this box and there
>>>>> has been virtually no administration or maintenance on it that I
>>>>> know of...) How about the WAL files in pg_xlog? How critical are
>>>>> they when no data on the system is critical in and of itself? Any
>>>>> suggestions would be greatly appreciated...
>>>>>
>>>>>
>>>>>
>>>
>>> ---------------------------(end of
>>> broadcast)---------------------------
>>> TIP 6: explain analyze is your friend
>>>
>>
>>
>>
>
--
erik jones <erik@myemma.com>
software development
emma(r)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: erik@myemma.com, jeff@frostconsultingllc.com, smarlowe@g2switchworks.com
Subject: Re: Disk is full, what's cool to get rid of?
In-Reply-To: <44C91B43.3080901@myemma.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox