Re: hung backends stuck in spinlock heavy endless loop
От | Merlin Moncure |
---|---|
Тема | Re: hung backends stuck in spinlock heavy endless loop |
Дата | |
Msg-id | CAHyXU0y8pCQ_K+JgqLGp9hbN5HAAd5tu6vDnLBKSrgk9gcUzAg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: hung backends stuck in spinlock heavy endless loop (Merlin Moncure <mmoncure@gmail.com>) |
Ответы |
Re: hung backends stuck in spinlock heavy endless loop
|
Список | pgsql-hackers |
On Thu, Jan 15, 2015 at 4:03 PM, Merlin Moncure <mmoncure@gmail.com> wrote: > On Thu, Jan 15, 2015 at 1:32 PM, Merlin Moncure <mmoncure@gmail.com> wrote: >> Since it's possible the database is a loss, do you see any value in >> bootstrappinng it again with checksums turned on? One point of note >> is that this is a brand spanking new SSD, maybe we nee to rule out >> hardware based corruption? > > hm! I bootstrapped a new database with checksums on, and lo, > > [cds2 18347 2015-01-15 15:58:29.955 CST 1779]WARNING: page > verification failed, calculated checksum 28520 but expected 28541 > [cds2 18347 2015-01-15 15:58:29.955 CST 1779]CONTEXT: SQL statement > "COPY lease_delete FROM > '/tmp/C1188732_onesiteproperty.lease_delete.csv' CSV HEADER" Running this test on another set of hardware to verify -- if this turns out to be a false alarm which it may very well be, I can only offer my apologies! I've never had a new drive fail like that, in that manner. I'll burn the other hardware in overnight and report back. merlin
В списке pgsql-hackers по дате отправления: