[OT] raiserfs su suse
Ciao a tutti, in azienda abbiamo un server suse su cui è stato
installato un db oracle. Questa mattina il server l'ho trovato bloccato.
L'ho riavviato ed oracle non ne vuole sapere di partire. Mentre dei
tecnici poco più esperti di me di oracle stanno provando a vedere quale
possa essere il problema, ho dato un'occhiata ai log di questa notte ed
ho trovato questo:
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: warning: is_tree_node:
> node level 0 does not match to the expected one 1
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: md0: warning: vs-5150:
> search_by_key: invalid format found in block 49087588. Fsck?
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: md0: warning: vs-13050:
> reiserfs_update_sd: i/o failure occurred trying to update [135852
> 289654 0x0 SD] stat data
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: warning: is_tree_node:
> node level 0 does not match to the expected one 1
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: md0: warning: vs-5150:
> search_by_key: invalid format found in block 49087588. Fsck?
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: md0: warning: vs-13050:
> reiserfs_update_sd: i/o failure occurred trying to update [135852
> 289654 0x0 SD] stat data
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: warning: is_tree_node:
> node level 0 does not match to the expected one 1
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: md0: warning: vs-5150:
> search_by_key: invalid format found in block 49087588. Fsck?
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: warning: is_tree_node:
> node level 0 does not match to the expected one 1
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: md0: warning: vs-5150:
> search_by_key: invalid format found in block 49087588. Fsck?
> Sep 13 04:00:58 serverlab2 kernel: ReiserFS: md0: warning: vs-5657:
> reiserfs_do_truncate: i/o failure occurred trying to truncate [135852
> 289654 0xfffffffffffffff DIRECT]
> Sep 13 04:01:06 serverlab2 kernel: general protection fault: 0000 [1] SMP
> Sep 13 04:01:06 serverlab2 kernel: last sysfs file:
> /devices/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0/irq
> Sep 13 04:01:06 serverlab2 kernel: CPU 3
> Sep 13 04:01:06 serverlab2 kernel: Modules linked in: raw nfs lockd
> nfs_acl sunrpc ipv6 binfmt_misc apparmor usbhid loop dm_mod ide_cd
> ehci_hcd uhci_hcd shpchp pci_hotplug usbcore hw_random bnx2 cdrom
> floppy reiserfs linear raid5 xor raid0 generic edd raid1 processor sg
> ata_piix libata piix sd_mod scsi_mod ide_disk ide_core
> Sep 13 04:01:06 serverlab2 kernel: Pid: 26539, comm: emagent Not
> tainted 2.6.16.60-0.37_f594963d-smp #1
> Sep 13 04:01:06 serverlab2 kernel: RIP: 0010:[<ffffffff80195308>]
> <ffffffff80195308>{__link_path_walk+2649}
> Sep 13 04:01:06 serverlab2 kernel: RSP: 0018:ffff8100a4ac5c98 EFLAGS:
> 00210202
> Sep 13 04:01:06 serverlab2 kernel: RAX: 524f204554454c45 RBX:
> ffff8101783cec30 RCX: 0000000000000000
> Sep 13 04:01:06 serverlab2 kernel: RDX: ffff8100a4ac5cb8 RSI:
> ffff81018c1a0220 RDI: ffff8100a4ac5cb8
> Sep 13 04:01:06 serverlab2 kernel: RBP: ffff8100a4ac5ea8 R08:
> 0000000000000000 R09: 0000000000000000
> Sep 13 04:01:06 serverlab2 kernel: R10: 0000000000009003 R11:
> ffffffff8823ca5b R12: ffff8100a4ac5cb8
> Sep 13 04:01:06 serverlab2 kernel: R13: 0000000000000000 R14:
> ffff810096f1802f R15: 00000000ffffff9c
> Sep 13 04:01:06 serverlab2 kernel: FS: 0000000000000000(0000)
> GS:ffff8101a9befe40(0063) knlGS:00000000f4dffba0
> Sep 13 04:01:06 serverlab2 kernel: CS: 0010 DS: 002b ES: 002b CR0:
> 0000000080050033
> Sep 13 04:01:06 serverlab2 kernel: CR2: 000000000822f6cc CR3:
> 00000001554ad000 CR4: 00000000000006a0
> Sep 13 04:01:06 serverlab2 kernel: Process emagent (pid: 26539,
> threadinfo ffff8100a4ac4000, task ffff8100cbaf3040)
> Sep 13 04:01:07 serverlab2 kernel: Stack: 4943534137535509
> 0000010100000049 0000000da4b6f43e ffff810096f18022
> Sep 13 04:01:07 serverlab2 kernel: ffff8101a946d6c0
> ffff81018c1a0220 0000000000000049 ffff8100a4ac5ea8
> Sep 13 04:01:07 serverlab2 kernel: ffff8100a4ac5ea8
> ffff8101a946d6c0
> Sep 13 04:01:07 serverlab2 kernel: Call Trace:
> <ffffffff8019589e>{link_path_walk+95}
> <ffffffff80195d18>{do_path_lookup+641}
> Sep 13 04:01:07 serverlab2 kernel:
> <ffffffff8019678a>{__path_lookup_intent_open+88}
> <ffffffff80196964>{open_namei+117}
> Sep 13 04:01:07 serverlab2 kernel:
> <ffffffff80184a3f>{do_filp_open+28} <ffffffff80184aa0>{do_sys_open+69}
> Sep 13 04:01:07 serverlab2 kernel:
> <ffffffff801226d4>{sysenter_do_call+27}
> Sep 13 04:01:07 serverlab2 kernel:
> Sep 13 04:01:07 serverlab2 kernel: Code: 48 83 78 50 00 0f 84 ca 03 00
> 00 65 48 8b 04 25 00 00 00 00
> Sep 13 04:01:07 serverlab2 kernel: RIP
> <ffffffff80195308>{__link_path_walk+2649} RSP <ffff8100a4ac5c98>
> Sep 13 04:01:48 serverlab2 apcupsd[3454]: Communications with UPS lost.
> Sep 13 04:05:01 serverlab2 /usr/sbin/cron[26770]: (root) CMD (
> /root/bin/loadwarn)
> Sep 13 04:11:41 serverlab2 syslog-ng[2535]: STATS: dropped 0
> Sep 13 04:11:49 serverlab2 apcupsd[3454]: Communications with UPS lost.
> Sep 13 04:21:49 serverlab2 apcupsd[3454]: Communications with UPS lost.
> Sep 13 04:31:51 serverlab2 apcupsd[3454]: Communications with UPS lost.
Dai log sembra che ci sia stato un errore nel filesystem che ha mandato
il kernel in fault che ha mandato in crash emagent (enterprise
management agent di oracle). Di raiserfs non ho alcuna esperienza, di
oracle pochissima e di suse ancor meno. Guardando in internet però
sembra che sia necessario eseguire raiserfsck: credete sia rischioso?
Avete qualche consiglio?
Grazie
Piviul
Reply to: