Newsgroup: it.comp.os.linux.sys
Titolo: Disastroso comportamento di raid-1 e EXT3-fs

Confido nel vostro aiuto per cercare di capire cosa è successo al nostro
server venerdì scorso, affinchè non si ripeta mai più che siano persi i dati
di 4 ore di lavoro apparentemente andate a buon fine.
Eccovi i fatti:
venerdì sera, dopo aver lavorato in 3 su diversi progetti (php e vb) senza
che nessun problema fosse apparentemente presente, cerco di arrestare il
server. Non riesco ad ottenere nessuno spegnimento ne con i classici
Crtl-Alt-Del ne tantomento con shutdown da riga di comando (user root). Sono
quindi costretto a spegnere brutalmente il server.
Oggi scopriamo il problema, dopo che sabato mattina il sistema è stato
riacceso per alcune ore da uno di noi, che però non ha notato nulla di
strano poichè i dati necessari erano sul suo PC. Comincio a guardare i vari
log e nel syslog trovo, tra le altre cose, queste righe. Mi rendo conto che
è lungo, ma ho assolutamente bisogno di capire cosa diavolo è successo
venerdì e sabato per causare un incidente tanto serio da provocare la
perdita di mezza giornata di lavoro (legge di murphy: il backup è stato
fatto nella pausa pranzo!). I file risultano presenti ma alla versione delle
ore 12.15-12.45 (a seconda dell'ultimo salvataggio).
Grazie 1000 per l'eventuale aiuto.
Fabio
May 10 11:01:00 CROND[5612]: (root) CMD (run-parts /etc/cron.hourly)
May 10 11:09:49 kernel: UDP: short packet: 137/58
May 10 11:54:48 kernel: UDP: short packet: 137/58
May 10 12:01:00 CROND[6865]: (root) CMD (run-parts /etc/cron.hourly)
May 10 12:39:49 kernel: UDP: short packet: 137/58
May 10 13:01:00 CROND[8124]: (root) CMD (run-parts /etc/cron.hourly)
May 10 13:01:00 CROND[8126]: (root) CMD
(/home/comune/backup/cron/mysql.backup)
May 10 13:01:00 CROND[8128]: (root) CMD
(/home/comune/backup/cron/cvs.backup)
May 10 13:01:00 CROND[8129]: (root) CMD
(/home/comune/backup/cron/fax.backup)
May 10 13:01:00 CROND[8134]: (root) CMD (/home/comune/backup/cron/sw.backup)
May 10 13:01:00 CROND[8135]: (root) CMD
(/home/comune/backup/cron/prjs.backup)
May 10 13:01:00 CROND[8139]: (root) CMD
(/home/comune/backup/cron/mans.backup)
May 10 13:01:00 CROND[8142]: (root) CMD
(/home/comune/backup/cron/docs.backup)
May 10 13:01:01 smbd[3157]: [2002/05/10 13:01:01, 0]
rpc_server/srv_netlog.c:api_net_sam_logon(208)
May 10 13:01:01 smbd[3157]: api_net_sam_logon: Failed to marshall
NET_R_SAM_LOGON.
May 10 13:01:01 smbd[3157]: [2002/05/10 13:01:01, 0]
rpc_server/srv_pipe.c:api_rpcTNP(1215)
May 10 13:01:01 smbd[3157]: api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
May 10 13:01:02 mount.smbfs[8155]: [2002/05/10 13:01:02, 0]
client/smbmount.c:send_fs_socket(381)
May 10 13:01:02 mount.smbfs[8155]: mount.smbfs: entering daemon mode for
service \\pc_enrico\backup, pid=8155
May 10 13:01:07 mount.smbfs[8164]: [2002/05/10 13:01:07, 0]
client/smbmount.c:send_fs_socket(381)
May 10 13:01:07 mount.smbfs[8164]: mount.smbfs: entering daemon mode for
service \\pc_enrico\backup, pid=8164
May 10 13:02:52 mount.smbfs[8201]: [2002/05/10 13:02:52, 0]
client/smbmount.c:send_fs_socket(381)
May 10 13:02:52 mount.smbfs[8201]: mount.smbfs: entering daemon mode for
service \\pc_enrico\backup, pid=8201
May 10 13:03:25 mount.smbfs[8217]: [2002/05/10 13:03:25, 0]
client/smbmount.c:send_fs_socket(381)
May 10 13:03:25 mount.smbfs[8217]: mount.smbfs: entering daemon mode for
service \\pc_enrico\backup, pid=8217
May 10 13:03:37 mount.smbfs[8224]: [2002/05/10 13:03:37, 0]
client/smbmount.c:send_fs_socket(381)
May 10 13:03:37 mount.smbfs[8224]: mount.smbfs: entering daemon mode for
service \\pc_enrico\backup, pid=8224
May 10 13:39:39 smbd[2833]: [2002/05/10 13:39:39, 0]
rpc_server/srv_netlog.c:api_net_sam_logon(208)
May 10 13:39:39 smbd[2833]: api_net_sam_logon: Failed to marshall
NET_R_SAM_LOGON.
May 10 13:39:39 smbd[2833]: [2002/05/10 13:39:39, 0]
rpc_server/srv_pipe.c:api_rpcTNP(1215)
May 10 13:39:39 smbd[2833]: api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
May 10 13:39:39 smbd[2181]: [2002/05/10 13:39:39, 0]
rpc_server/srv_netlog.c:api_net_sam_logon(208)
May 10 13:39:39 smbd[2181]: api_net_sam_logon: Failed to marshall
NET_R_SAM_LOGON.
May 10 13:39:39 smbd[2181]: [2002/05/10 13:39:39, 0]
rpc_server/srv_pipe.c:api_rpcTNP(1215)
May 10 13:39:39 smbd[2181]: api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
May 10 13:39:39 smbd[3157]: [2002/05/10 13:39:39, 0]
rpc_server/srv_netlog.c:api_net_sam_logon(208)
May 10 13:39:39 smbd[3157]: api_net_sam_logon: Failed to marshall
NET_R_SAM_LOGON.
May 10 13:39:39 smbd[3157]: [2002/05/10 13:39:39, 0]
rpc_server/srv_pipe.c:api_rpcTNP(1215)
May 10 13:39:39 smbd[3157]: api_rpcTNP: api_netlog_rpc: NET_SAMLOGON failed.
May 11 09:33:11 kernel: md: bind<ide/host0/bus0/target0/lun0/part9,2>
May 11 09:33:11 kernel: md: running:
<ide/host0/bus0/target0/lun0/part9><ide/host0/bus1/target0/lun0/part9>
May 11 09:33:11 kernel: md: now!
May 11 09:33:11 kernel: md: ide/host0/bus0/target0/lun0/part9's event
counter: 00000132
May 11 09:33:11 kernel: md: ide/host0/bus1/target0/lun0/part9's event
counter: 00000132
May 11 09:33:11 kernel: md: md1: raid array is not clean -- starting
background reconstruction
May 11 09:33:11 kernel: RAID level 65536 does not need chunksize! Continuing
anyway.
May 11 09:33:11 kernel: md1: max total readahead window set to 124k
May 11 09:33:11 kernel: md1: 1 data-disks, max readahead per data-disk: 124k
May 11 09:33:11 kernel: raid1: device ide/host0/bus0/target0/lun0/part9
operational as mirror 0
May 11 09:33:11 kernel: raid1: device ide/host0/bus1/target0/lun0/part9
operational as mirror 1
May 11 09:33:11 kernel: raid1: raid set md1 not clean; reconstructing
mirrors
May 11 09:33:11 kernel: raid1: raid set md1 active with 2 out of 2 mirrors
May 11 09:33:11 kernel: md: updating md1 RAID superblock on device
May 11 09:33:11 kernel: md: ide/host0/bus0/target0/lun0/part9 [events:
00000133](write) ide/host0/bus0/target0/lun0/part9's sb offset: 361344
May 11 09:33:11 kernel: md: delaying resync of md1 until md0 has finished
resync (they share one or more physical units)
May 11 09:33:11 kernel: md: ide/host0/bus1/target0/lun0/part9 [events:
00000133](write) ide/host0/bus1/target0/lun0/part9's sb offset: 361344
May 11 09:33:11 kernel: md: ... autorun DONE.
May 11 09:33:11 kernel: EXT3-fs: INFO: recovery required on readonly
filesystem.
May 11 09:33:11 kernel: EXT3-fs: write access will be enabled during
recovery.
May 11 09:33:11 kernel: kjournald starting. Commit interval 5 seconds
May 11 09:33:11 kernel: EXT3-fs: md(9,0): orphan cleanup on readonly fs
May 11 09:33:11 kernel: ext3_orphan_cleanup: deleting unreferenced inode
49576
May 11 09:33:11 kernel: EXT3-fs: md(9,0): 1 orphan inode deleted
May 11 09:33:11 kernel: EXT3-fs: recovery complete.
May 11 09:33:11 kernel: EXT3-fs: mounted filesystem with ordered data mode.
May 11 09:33:11 kernel: Freeing unused kernel memory: 712k freed
May 11 09:33:11 kernel: Real Time Clock Driver v1.10d
May 11 09:33:11 kernel: Adding Swap: 706820k swap-space (priority -1)
May 11 09:33:11 kernel: Adding Swap: 706820k swap-space (priority -2)
May 11 09:33:11 kernel: EXT3 FS 2.4-0.9.6, 11 Aug 2001 on md(9,0), internal
journal
May 11 09:33:11 kernel: kjournald starting. Commit interval 5 seconds
May 11 09:33:11 kernel: EXT3 FS 2.4-0.9.6, 11 Aug 2001 on md(9,1), internal
journal
May 11 09:33:11 kernel: EXT3-fs: recovery complete.
May 11 09:33:11 kernel: EXT3-fs: mounted filesystem with ordered data mode.
May 11 09:33:11 kernel: kjournald starting. Commit interval 5 seconds
May 11 09:33:11 kernel: EXT3 FS 2.4-0.9.6, 11 Aug 2001 on md(9,4), internal
journal
May 11 09:33:11 kernel: EXT3-fs: recovery complete.
May 11 09:33:11 kernel: EXT3-fs: mounted filesystem with ordered data mode.
May 11 09:33:11 kernel: SUPERMOUNT error (device 0/9):
supermount_read_super: no dev=<filesystem> option
May 11 09:33:11 kernel: kjournald starting. Commit interval 5 seconds
May 11 09:33:11 kernel: EXT3 FS 2.4-0.9.6, 11 Aug 2001 on md(9,2), internal
journal
May 11 09:33:11 kernel: EXT3-fs: recovery complete.
May 11 09:33:11 kernel: EXT3-fs: mounted filesystem with ordered data mode.
May 11 09:33:11 kernel: kjournald starting. Commit interval 5 seconds
May 11 09:33:11 kernel: EXT3 FS 2.4-0.9.6, 11 Aug 2001 on md(9,3), internal
journal
May 11 09:33:11 kernel: EXT3-fs: recovery complete.
May 11 09:33:11 kernel: EXT3-fs: mounted filesystem with ordered data mode.

puoi postare anche il dmesg ?