Skip site navigation (1) Skip section navigation (2)

BUG #6022: Postgre84+RHEL6+Veritas file system?

From: "Manoranjan Reddy" <mano(at)manosoftlive(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6022: Postgre84+RHEL6+Veritas file system?
Date: 2011-05-11 11:22:01
Message-ID: 201105111122.p4BBM1Ip059915@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      6022
Logged by:          Manoranjan Reddy
Email address:      mano(at)manosoftlive(dot)com
PostgreSQL version: 8.4
Operating system:   RHEL6
Description:        Postgre84+RHEL6+Veritas file system?
Details: 

Do this config work well?
PostGreSQL 8.4 + Veritas File System + RHEL 6.0 ?

This combination is giving problems for me.
Can anyone comment on this?
Following is the procedure i followed and errors etc...
Expert advice is greatly appreciated.
===============================================
#Started the PostGreSQL, started successfully
postgres{5} pg_ctl -D /usr/local/postgres/data/ start
server starting

#Output of ps command
postgres{6} !ps
ps -ef | grep post
postgres 18203 1 0 19:09 ? 00:00:00 postgres: logger process
postgres 18205 1 99 19:09 ? 01:39:26 postgres: writer process
postgres 19381 1 0 19:11 ? 00:00:00 postgres: logger process
postgres 19383 1 0 19:11 ? 00:00:00 postgres: writer process
root 21392 21352 0 20:47 pts/2 00:00:00 su postgres
postgres 21393 21392 0 20:47 pts/2 00:00:00 bash
postgres 21781 1 18 20:49 pts/2 00:00:00 /usr/bin/postgres -D
/usr/local/postgres/data
postgres 21782 21781 0 20:49 ? 00:00:00 postgres: logger process
postgres 21784 21781 0 20:49 ? 00:00:00 postgres: writer process
postgres 21785 21781 0 20:49 ? 00:00:00 postgres: wal writer process
postgres 21786 21781 0 20:49 ? 00:00:00 postgres: autovacuum launcher
process
postgres 21787 21781 0 20:49 ? 00:00:00 postgres: stats collector process
postgres 21788 21393 4 20:49 pts/2 00:00:00 ps -ef
postgres 21789 21393 0 20:49 pts/2 00:00:00 grep post

#Checking status of PostGreSQL
postgres{23} pg_ctl status -D /usr/local/postgres/data/
pg_ctl: server is running (PID: 21781)
/usr/bin/postgres "-D" "/usr/local/postgres/data"

#Stopping PostGreSQL, it didnt go through
postgres{24} pg_ctl stop -D /usr/local/postgres/data/
waiting for server to shut
down.............................................. ................. failed
pg_ctl: server does not shut down

#Checking status of PostGreSQL, Status shows it as running
postgres{25} pg_ctl status -D /usr/local/postgres/data/
pg_ctl: server is running (PID: 21781)
/usr/bin/postgres "-D" "/usr/local/postgres/data"

# Killed the process 21781, output of ps -ef
postgres{57} ps -ef | grep postgres
postgres 18205 1 99 19:09 ? 01:46:29 postgres: writer process
postgres 19383 1 0 19:11 ? 00:00:00 postgres: writer process
root 21392 21352 0 20:47 pts/2 00:00:00 su postgres
postgres 21393 21392 0 20:47 pts/2 00:00:00 bash
postgres 21784 1 0 20:49 ? 00:00:00 postgres: writer process
postgres 24398 21393 0 20:56 pts/2 00:00:00 ps -ef
postgres 24399 21393 0 20:56 pts/2 00:00:00 grep postgres

#output of ipcs, open ipcs.
postgres{58} ipcs | grep postgres
0x00000000 1507334 postgres 600 29278208 1 dest
0x00000000 1540104 postgres 600 29278208 1 dest
0x0052e2c1 1572873 postgres 600 29278208 1
0x0052e2c1 9535490 postgres 600 17
0x0052e2c2 9568259 postgres 600 17
0x0052e2c3 9601028 postgres 600 17
0x0052e2c4 9633797 postgres 600 17
0x0052e2c5 9666566 postgres 600 17
0x0052e2c6 9699335 postgres 600 17
0x0052e2c7 9732104 postgres 600 17
================

Consequences of this :
1)Because of unclosed writers i'm unable to umount filesystem(even with
force flag)
root 23674 23636 0 20:54 ? 00:00:00 /opt/VRTS/bin/vxumount -o force
/usr/local/postgres/data [veritas file system umount is stuck]
2) These writer processes cant be killed, even with kill -9
3) File system is hung.
4) I had to reboot machine

Responses

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2011-05-11 14:25:39
Subject: Re: Changed behaviour of \'
Previous:From: 李紅兵Date: 2011-05-11 11:11:21
Subject: Re: BUG #5994: Can't excute DBI->connect to oracle by client site

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group