postgresql启动时遇到一个post_create错误?

shang12

症状：
启动postgresql的时候是失败的.
系统提示的是这个错误,kernel:post_create:setxattr failed,rc=28(dev=hda3 ino=634205)

环境:
虚拟机装了redhat as4
linux kernel 2.6.9-42.EL
postgresql8.14
resin3.0
jdk1.5

LOG:
这个是postgresql-2008-04-02_100233.log
LOG:  database system was shut down at 2008-04-02 10:02:31 EDT
LOG:  checkpoint record is at 0/33A70C
LOG:  redo record is at 0/33A70C; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 565; next OID: 10794
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system is ready
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
ERROR:  database "jasinda" does not exist
ERROR:  database "jasindadetail" does not exist
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
LOG:  received fast shutdown request
LOG:  shutting down
LOG:  database system is shut down
LOG:  logger shutting down

postgresql-2008-04-02_100242.log
LOG:  database system was shut down at 2008-04-02 10:02:40 EDT
LOG:  checkpoint record is at 0/33BACC
LOG:  redo record is at 0/33BACC; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 576; next OID: 16387
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system is ready
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
ERROR:  role "jasinda" already exists
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"
LOG:  received fast shutdown request
LOG:  shutting down
LOG:  database system is shut down
LOG:  logger shutting down
这2个是发生错误以前的最后2个LOG.在/var/log/message里面也看不到其他任何的信息.就只是看到
service postgresql failed.

措施:
1.用top,和ps -aux查看是否有postmaster的进程
2.去/var/lib/pgsql/data/里面也没有发现postmaster.pid的文件..

变化:
最近这一段时间都没做什么操作.在4月3号还是可以照常访问的,但是有一次非法重起了.就造成了这种错误.