Scott Marlowe wrote:
So, I wonder what went wrong? Any explanation? Soft raid no good for
PostgreSQL?
I've no such problems caused by modern linux software RAID (md). It's
no surprise pgsql didn't free up the space, as it was all likely dead
tuples at that point. Are you sure you didn't have a cartesian
product that created a larger set than you anticipated? I'd post the
query here to see if anyone has any suggestions on that.
I'm glad to hear my soft raid md0 is no problem.
As for the freeing inode messages, it sounds like something is
causeing file system corruption, and my first suspect is always memory
/ hardware issues. Have you run memtest86 on that machine to make
sure it's got good memory etc.?
I do have some weird every few days error where the soft raid blocks for
a couple of seconds and I get this kernel log output:
Jul 7 19:58:55 server kernel: [40336.000239] ata1.00: status: { DRDY }
Jul 7 19:58:55 server kernel: [40336.000244] ata1.00: cmd
61/08:a0:a7:44:21/00:00:00:00:00/40 tag 20 ncq 4096 out
Jul 7 19:58:55 server kernel: [40336.000245] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
This an experimental machine, an old(er) Dell PowerEdge 800. I haven't
had the time to look into this. Any thoughts?
Thanks!
Dirk
--
Phone: +1 (650) 215 3459
Blog: http://dirkriehle.com
http://twitter.com/dirkriehle
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
