Precisa de quaisquer dicas sobre o sistema de arquivos do host Linux que vai para o modo somente leitura

Question

Eu tenho um guest Linux do CentOS 5.x rodando em um servidor XEN (Citrix), e de vez em quando misteriosamente ele entra no modo somente leitura.

Eu verifiquei o sistema de arquivos em busca de erros, nada suspeito apareceu ...: (

O log do sistema diz algo como:

Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735103
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735191
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735279
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735359
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735447
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735535
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735103
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 309735103
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 307662855
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 315316647
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 315316655
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 315316663
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 315316671
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 315316735
Mar  5 10:57:16 testsrv last message repeated 38 times
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 307662855
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 262717023
Mar  5 10:57:16 testsrv last message repeated 2 times
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 258482255
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 141041743
Mar  5 10:57:16 testsrv kernel: EXT3-fs error (device xvdb1): ext3_find_entry: reading directory #17629185 offset 0
Mar  5 10:57:16 testsrv kernel: Aborting journal on device xvdb1.
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 16519
Mar  5 10:57:16 testsrv kernel: Buffer I/O error on device xvdb1, logical block 2057
Mar  5 10:57:16 testsrv kernel: lost page write due to I/O error on xvdb1
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 63
Mar  5 10:57:16 testsrv kernel: Buffer I/O error on device xvdb1, logical block 0
Mar  5 10:57:16 testsrv kernel: lost page write due to I/O error on xvdb1
Mar  5 10:57:16 testsrv kernel: end_request: I/O error, dev xvdb, sector 59692223
Mar  5 10:57:16 testsrv last message repeated 33 times
Mar  5 10:57:16 testsrv kernel: ext3_abort called.
Mar  5 10:57:16 testsrv kernel: EXT3-fs error (device xvdb1): ext3_journal_start_sb: Detected aborted journal
Mar  5 10:57:16 testsrv kernel: Remounting filesystem read-only

    

Answer 1

@DejanLekic: tune2fs etc só verifica o sistema de arquivos em busca de erros. As mensagens de erro do kernel que você observou são sobre falhas de hardware, que é uma camada abaixo do sistema de arquivos. Sistemas de arquivos e sistemas operacionais modernos estão levando muito a sério falhas de hardware; ext * remonta a si mesmo como somente leitura para evitar qualquer acesso de gravação causando mais danos, o XFS se encerra completamente e assim por diante.

Então você tem algum tipo de problema de hardware. Controlador RAID ruim, disco rígido morto, SAN não confiável, outra coisa.