| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Dirk Riehle <dirk(at)riehle(dot)org> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Weird disk/table space consumption problem |
| Date: | 2009-07-12 07:22:28 |
| Message-ID: | dcc563d10907120022q1ca7b22dv1eb1298aee0b74fa@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jul 11, 2009 at 7:19 PM, Dirk Riehle<dirk(at)riehle(dot)org> wrote:
> Tom Lane wrote:
>>
>> Dirk Riehle <dirk(at)riehle(dot)org> writes:
>>> During boot, fsck (must have been fsck) gave me tons of freeing up inode
>>> messages.
>>
>> And this part is a filesystem bug; it cannot possibly be Postgres'
>> fault that the filesystem got corrupted.
>
> One would think so? But the reboot should have stopped PostgreSQL properly.
Doesn't matter whether or not pgsql was shut down properly, it
shouldn't result in file system corruption. Now if the file wasn't
properly unmounted before power down, that could cause file system
corruption. With a journaling file system the file system should come
right back up corruption free.
Are you running an older distro or something maybe?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-07-12 07:23:48 | Re: Weird disk/table space consumption problem |
| Previous Message | Dennis Gearon | 2009-07-12 04:15:30 | indexes on float8 vs integer |