> > Yikes. You have corrupt files on disk. Have you had hardware problem or > OS crashes lately? Or running some funky beta-version of a filesystem > ;-) >
nah .. ext3 and no crashes > Also, what version of pg is this? Is it a large/old database, and if so > are you vacuum:ing regularly? > vacuum stopped running because of the problem ^^ >> i thought the reason could be bacula having errors... > > Nope, not related. > > > Anyway. The proper fix is to restore a backup from before the disk > corruption occured. If you can't do this, try to recreate the file > using: > dd if=/dev/zero bs=1k count=128 of=/var/lib/postgres/data/pg_clog/0000 > > This only applies if the file does not exist, of course - if it does, > and pg for some reason can't see it, you have a different problem. > > *WARNING* This may quite well lose data for you, because it will zero > out the visibility info. If it works, pg_dump yuor database right away, > re-initdb, and reload that backup. > well since postgresql only holds the bacula database i just did a reinstall and set up database from scratch, it seems to work fine now pg_dump was also not working anymore ^^ the advice to re-initdb wa a bit too late ... did it the blunt way ;-) > > You'll definitly want to do an extra round of fsck on your filesystem, > probably with badblocks checking enabled. > > //Magnus can't really do that right now, and since syslog did hold 0 messages from disk problems i don't think it's the hardware anyway Florian _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
