libc-2.11.2.so segfault on OpenSuSE puts filesystem server into readonly mode

Reignfire · 07-31-2013, 03:10 AM

Hi,

I'm having some problems which put my server into readonly mode. I pretty sure it's software related, cause i recently replaced the disks by new ones.

Some information about the server:

OS: OpenSuSE 11.3
kernel: 2.6.34.10-0.2-desktop
disks: 2 x 1TB (raid 1)

When i try to remove something i get: Read-only file system
When i try to run something like zypper i get: bash: /usr/bin/zypper: Input/output error

If i restart the server it works fine until i get following segfaults and then it starts acting weird. The libc-2.11.2.so library seems to be the problem.

dmesg output:

Code:

[ 1710.220109] packagekitd[15769]: segfault at d8 ip 00007fad78a6ce8f sp 00007fad7285d8b0 error 6 in libc-2.11.2.so[7fad789b5000+157000]
[ 2112.986321] usb 1-7.1.1: USB disconnect, address 5
[ 2113.754325] usb 1-7.1.2: USB disconnect, address 4
[13948.696131] lmstat[5860]: segfault at 37353140 ip 00000000f764f463 sp 00000000ffff547c error 4 in libc-2.11.2.so[f75d9000+164000]
[21940.498648] fluentlm-helper[21950]: segfault at 0 ip 00000000f760c033 sp 00000000ff83fe28 error 4 in libc-2.11.2.so[f75dc000+164000]
[21955.232748] liblic90.so[21951]: segfault at 1 ip 0000000000000001 sp 00007fff4f610ba8 error 14 in liblic90.so[7f0dec355000+7000]
[22931.603944] fluentlm-helper[24719]: segfault at 0 ip 00000000f763d033 sp 00000000ff821d88 error 4 in libc-2.11.2.so[f760d000+164000]
[24311.797090] fluentlm-helper[27195]: segfault at 0 ip 00000000f758b033 sp 00000000ff97d628 error 4 in libc-2.11.2.so[f755b000+164000]
[28154.929289] warning: `mono' uses deprecated v2 capabilities in a way that may be insecure.
[41848.753078] lmstat[16655]: segfault at 37353140 ip 00000000f7625463 sp 00000000ffc880ec error 4 in libc-2.11.2.so[f75af000+164000]
[46348.724119] lmstat[19948]: segfault at 37353140 ip 00000000f7634463 sp 00000000ffd74cfc error 4 in libc-2.11.2.so[f75be000+164000]
[46554.113081] Buffer I/O error on device dm-2, logical block 4195040
[46554.113085] lost page write due to I/O error on dm-2
[46554.113101] Buffer I/O error on device dm-2, logical block 4195230
[46554.113103] lost page write due to I/O error on dm-2
[46554.113106] Buffer I/O error on device dm-2, logical block 0
[46554.113107] lost page write due to I/O error on dm-2
[46554.113111] Buffer I/O error on device dm-2, logical block 2
[46554.113112] lost page write due to I/O error on dm-2
[46554.113125] Buffer I/O error on device dm-2, logical block 4718596
[46554.113127] lost page write due to I/O error on dm-2
[46559.692101] Buffer I/O error on device dm-2, logical block 795664
[46559.692103] lost page write due to I/O error on dm-2
[46559.692158] Buffer I/O error on device dm-2, logical block 788425
[46559.692160] lost page write due to I/O error on dm-2
[46559.692171] JBD2: Detected IO errors while flushing file data on dm-2-8
[46559.700052] Aborting journal on device dm-2-8.
[46559.700067] EXT4-fs error (device dm-2) in ext4_reserve_inode_write: Journal has aborted
[46559.700070] Buffer I/O error on device dm-2, logical block 2655233
[46559.700072] lost page write due to I/O error on dm-2
[46559.700075] EXT4-fs (dm-2): previous I/O error to superblock detected
[46559.700079] JBD2: I/O error detected when updating journal superblock for dm-2-8.
[46559.708030] Buffer I/O error on device dm-2, logical block 0
[46559.708031] lost page write due to I/O error on dm-2
[46559.708051] EXT4-fs error (device dm-2) in ext4_dirty_inode: Journal has aborted
[46559.708053] EXT4-fs (dm-2): previous I/O error to superblock detected
[46559.708069] Buffer I/O error on device dm-2, logical block 0
[46559.708071] lost page write due to I/O error on dm-2
[46559.708082] EXT4-fs error (device dm-2): ext4_journal_start_sb: Detected aborted journal
[46559.708084] EXT4-fs (dm-2): Remounting filesystem read-only
[47237.178047] Buffer I/O error on device dm-0, logical block 196144380
[47237.178051] lost page write due to I/O error on dm-0
[47237.178056] Buffer I/O error on device dm-0, logical block 196144381
[47237.178058] lost page write due to I/O error on dm-0
[47237.178061] Buffer I/O error on device dm-0, logical block 196144382
[47237.178063] lost page write due to I/O error on dm-0
[47242.695200] JBD2: Detected IO errors while flushing file data on dm-0-8
[47242.695258] Aborting journal on device dm-0-8.
[47242.695271] Buffer I/O error on device dm-0, logical block 104890368
[47242.695272] lost page write due to I/O error on dm-0
[47242.695278] JBD2: I/O error detected when updating journal superblock for dm-0-8.
[47266.931827] EXT4-fs error (device dm-0): ext4_journal_start_sb: Detected aborted journal
[47266.931831] EXT4-fs (dm-0): Remounting filesystem read-only
[48136.658563] type=1503 audit(1375227001.352:293): operation="change_hat" info="unconfined" error=                                        -1 pid=20789

How can i fix this?

Kind regards

John VV · 07-31-2013, 09:10 PM

11.3 ?
well 11.4 is also past the lifespan
and so is 12.1

might be time to upgrade to 12.3

are you trying to use "evergreen 11.4 repo"

i do not think it is compatible with 11.3

besides replacing hard drives what else have you done
-- there have been NO updates to 11.3 for 18 months , since Jan 20 2012
so you have not installed updates .

Quote:

warning: `mono' uses deprecated v2 capabilities in a way that may be insecure.

you are getting a mono warning , and the very old version in 11 did not work ( to but it mildly ) well .

How did you replace drives ?
that there might put the OS into READ ONLY mode to protect it from a faulty set up raid or lvm,
and you are getting lvm partition errors .
How did you make the back up that you copied on to the new drives ?
and how did you move it over to the new drives ?