https://bugzilla.novell.com/show_bug.cgi?id=656464 https://bugzilla.novell.com/show_bug.cgi?id=656464#c0 Summary: 2.6.37rc3 - disk corruption? Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: jnelson-suse@jamponi.net QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 I'm on openSUSE 11.3 with KOTD:HEAD and home:jobermeyr (for drm), KDE, etc... Since booting 2.6.37rc3 today, I've had a *bunch* of postgresql errors which typically indicate storage issues. I have been running postgresql for almost three years on this machine without *one* instance of this class of error, or any storage-related error for that matter. One such error (the most frequent): XX002: index "FOO_pkey" contains unexpected zero page at block 35536 Another: right sibling's left-link doesn't match: block 2855 links to 38398 instead of expected 36370 in index "FOO_pkey" The primary key index FOO_pkey is not /always/ the place where the error crops up. but there are other errors, all similar -- finding zeros where there shouldn't be or other forms of corruption. the filesystem is ext4 mounted noatime. barriers are enabled and appear to work. the next layer is an LVM logical volume. the next layer is an LVM volume group constructed of a dm-crypt'd partition. Thus, it goes: /dev/sdaX -> dm-crypt -> LVM stack -> ext4 The block number of the error, and the specific error change. The *type* of error does not. It is not 100% reproducible during a particular test, but it has happened at least a half-dozen times today alone. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.