Databases
StackOverflow2013
Postsdbo
POPostgreSQL 9: could not fsync file "base/16386": Invalid argument
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPostgreSQL 9: could not fsync file "base/16386": Invalid argument
    primarykey
    data
    text
    <p>I'm trying to test a small PostgreSQL setup, so I cobbled together a quick local install. However, when I'm trying to create my personal db with createdb, it chokes on errors like this (notably, it starts with base/16384 the first time, and increments each time I run it). Anyone know what's going on here, or if there's some trivial config I missed that would cause this? Thanks, and this is somewhat time-critical, so please respond if you do know anything. Thanks! </p> <p>UPDATES:<br> I'm running this on a CentOS 5 server, apologies that I don't have too many further details (it's a shared account on that server). uname -a has the following output: </p> <p>Linux {OMITTED} 2.6.18-194.11.4.el5 #1 SMP Tue Sep 21 05:04:09 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux </p> <p>I installed PostgreSQL from source from: </p> <p><a href="http://wwwmaster.postgresql.org/download/mirrors-ftp/source/v9.0.1/postgresql-9.0.1.tar.bz2" rel="nofollow">http://wwwmaster.postgresql.org/download/mirrors-ftp/source/v9.0.1/postgresql-9.0.1.tar.bz2</a> </p> <p>built in my home directory and installed to prefix=$HOME/local/pgsql. </p> <h2>Here's a terminal readout for me attempting to create my user's db on a fresh data setup:</h2> <p>[htung@{OMITTED}:~]$ killall postgres<br> LOG: autovacuum launcher shutting down<br> LOG: received smart shutdown request<br> LOG: shutting down<br> LOG: database system is shut down<br> [htung@{OMITTED}:~]$ rm -r tmp<br> mk[1]+ Done ../local/pgsql/bin/postgres -D $HOME/tmp (wd: ~/tmp)<br> (wd now: ~)<br> [htung@{OMITTED}:~]$ mkdir tmp<br> [htung@{OMITTED}:~]$ local/pgsql/bin/initdb -D $HOME/tmp<br> The files belonging to this database system will be owned by user "htung".<br> This user must also own the server process. </p> <p>The database cluster will be initialized with locale en_US.UTF-8.<br> The default database encoding has accordingly been set to UTF8.<br> The default text search configuration will be set to "english". </p> <p>fixing permissions on existing directory /afs/{OMITTED}/htung/tmp ... ok<br> creating subdirectories ... ok<br> selecting default max_connections ... 100<br> selecting default shared_buffers ... 32MB<br> creating configuration files ... ok<br> creating template1 database in /afs/{OMITTED}/htung/tmp/base/1 ... ok<br> initializing pg_authid ... ok<br> initializing dependencies ... ok<br> creating system views ... ok<br> loading system objects' descriptions ... ok<br> creating conversions ... ok<br> creating dictionaries ... ok<br> setting privileges on built-in objects ... ok<br> creating information schema ... ok<br> loading PL/pgSQL server-side language ... ok<br> vacuuming database template1 ... ok<br> copying template1 to template0 ... ok<br> copying template1 to postgres ... ok </p> <p>WARNING: enabling "trust" authentication for local connections<br> You can change this by editing pg_hba.conf or using the -A option the<br> next time you run initdb. </p> <p>Success. You can now start the database server using: </p> <pre><code>local/pgsql/bin/postgres -D /afs/{OMITTED}/htung/tmp </code></pre> <p>or<br> local/pgsql/bin/pg_ctl -D /afs/{OMITTED}/htung/tmp -l logfile start </p> <p>[htung@{OMITTED}:~]$ local/pgsql/bin/postgres -D $HOME/tmp<br> LOG: database system was shut down at 2010-11-15 13:47:25 PST<br> LOG: autovacuum launcher started<br> LOG: database system is ready to accept connections </p> <p>[1]+ Stopped local/pgsql/bin/postgres -D $HOME/tmp<br> [htung@{OMITTED}:~]$ bg<br> [1]+ local/pgsql/bin/postgres -D $HOME/tmp &amp;<br> [htung@{OMITTED}:~]$ local/pgsql/bin/createdb<br> ERROR: could not fsync file "base/16384": Invalid argument<br> STATEMENT: CREATE DATABASE htung; </p> <p>createdb: database creation failed: ERROR: could not fsync file "base/16384": Invalid argument<br> [htung@{OMITTED}:~]$ </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USuser508633
    1. USuser508633
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COWhat OS are you on? How did you install it, with an installer or via source? Also copy in your entire session text that results in that error.
      singulars
      1. POPostgreSQL 9: could not fsync file "base/16386": Invalid argument
      1. USKuberchaun
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload