Re: database corruption

Поиск
Список
Период
Сортировка
От Albe Laurenz *EXTERN*
Тема Re: database corruption
Дата
Msg-id D960CB61B694CF459DCFB4B0128514C202FF6555@exadv11.host.magwien.gv.at
обсуждение исходный текст
Ответ на Re: database corruption  ("Jeff Brenton" <jbrenton@sandvine.com>)
Список pgsql-general
This thread is a top posting mess. I'll try to rearrange:

Jeff Brenton wrote:
>>>>> REINDEX INDEX testrun_log_pkey;
>>>>>
>>>>> ERROR:  could not write block 1832079 of temporary file: No space left
>>>>> on device
>>>>> HINT:  Perhaps out of disk space?
>>>>>
>>>>> There is currently 14GB free on the disk that postgres is installed on.
>>>>> Does anyone know what I can do to get the db up and running again?
[...]
>>>>> /dev/amrd2s1d    663G    596G     14G    98%    /db
>>>>
>>>> I guess the first question is, does the db have permissions(access) to
>>>> all that space?
>>>
>>> There are no filesystem level content size restrictions that I am aware
>>> of on this system.  The user pgsql should have full access to the
>>> filesystems indicated except for the root filesystem.
>>
>> Inodes?
>
> There are 9 miilion inodes free on /db.  All other partitions have at
> least 1/2 million free.

Assuming that this is ext3 on Linux, it could be space reserved for root.

What do you get if you run the following as root:

dumpe2fs /dev/amrd2s1d | grep 'Reserved block count'

Yours,
Laurenz Albe

В списке pgsql-general по дате отправления:

Предыдущее
От: Craig Ringer
Дата:
Сообщение: Re: database corruption
Следующее
От: Ivan Sergio Borgonovo
Дата:
Сообщение: Re: database corruption