Re: BUG #14168: ALTER TABLE SET LOGGED failing - Mailing list pgsql-bugs

From David Gould
Subject Re: BUG #14168: ALTER TABLE SET LOGGED failing
Date
Msg-id 20160601000634.1fac664c@engels
Whole thread Raw
In response to BUG #14168: ALTER TABLE SET LOGGED failing  (ganesh.kannan@weatheranalytics.com)
Responses Re: BUG #14168: ALTER TABLE SET LOGGED failing
List pgsql-bugs
On Wed, 01 Jun 2016 04:57:41 +0000
ganesh.kannan@weatheranalytics.com wrote:

> The following bug has been logged on the website:
>
> Bug reference:      14168
>
> psql:mvTS2.sql:6: ERROR:  could not extend file
> "pg_tblspc/16404/PG_9.5_201510051/16407/61740.1": wrote only 4096 of 8192
> bytes at block 175411
> HINT:  Check free disk space.
> Time: 335539.031 ms
>
> However, there is enough free space available on the volumes to accommodate
> several of the tables, but ALTER TABLE set logged command consistently
> fails,  df -h shows this:
>
> >> df -h  | grep data5
> /dev/mapper/vg_pgdata5-lv_pgdata5  9.8T  9.5T  363G  97% /pg_land_data5

Sometimes the unix error ENOSPC covers more than disk space. For example
you could be out of inodes. What does df -i show?

-dg

--
David Gould              510 282 0869         daveg@sonic.net
If simplicity worked, the world would be overrun with insects.

pgsql-bugs by date:

Previous
From: ganesh.kannan@weatheranalytics.com
Date:
Subject: BUG #14168: ALTER TABLE SET LOGGED failing
Next
From: Michael Paquier
Date:
Subject: Re: BUG #14155: bloom index error with unlogged table