Estou com o seguinte problema frequentemente em nosso servidor de backup. Vou tentar explicar a questão na esperança de que alguém possa esclarecer por que e como consertar isso
Temos um servidor DELL r200 conectado a um array de discos RAID easyRAID Q16R-S3R3. Usamos uma placa PCI LSI SAS2008 para conectar esses dois componentes (o disk-array e o head-node). No EasyRAID, temos 8 discos instalados e estão vinculados a um disco lógico.
No R200 temos a seguinte configuração de disco: Criamos o LVM no servidor R200, não no EASYRAID
pvs PV VG Fmt Attr PSize PFree /dev/sdc vg0 lvm2 a- 5.46t 1.03t
root@backupserver:/home/netsys# vgs VG #PV #LV #SN Attr VSize VFree vg0 1 9 0 wz--n- 5.46t 1.03t
root@backupserver:/home/netsys# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert lv0vm vg0 -wi-ao 1000.00g lv0vm2 vg0 -wi-a- 100.00g lv1data vg0 -wi-ao 1000.00g lv1databackup vg0 -wi-ao 1000.00g lv1dataold20120903 vg0 -wi-a- 1000.00g lv2ceres vg0 -wi-ao 200.00g lv2ceresold20121022 vg0 -wi-a- 100.00g lv3iso vg0 -wi-ao 34.00g lv4svn vg0 -wi-ao 100.00g
Todas as noites, por volta das 22h, executamos o Rsnapshot entre o lv1databackup e o lv1data (contendo os snapshots). Agora acabamos depois de executar essa configuração toda vez com os seguintes erros nos logs
May 20 22:15:20 backupserver kernel: [11777489.404269] EXT3-fs error (device dm-8): ext3_lookup: deleted inode referenced: 60891438 May 20 22:15:20 backupserver kernel: [11777489.406210] EXT3-fs error (device dm-8): ext3_lookup: deleted inode referenced: 60891429 May 20 22:15:20 backupserver kernel: [11777489.407835] EXT3-fs error (device dm-8): ext3_lookup: deleted inode referenced: 60891431 May 20 22:15:20 backupserver kernel: [11777489.409474] EXT3-fs error (device dm-8): ext3_lookup: deleted inode referenced: 60891430 May 20 22:15:21 backupserver kernel: [11777489.422835] EXT3-fs error (device dm-8): ext3_lookup: deleted inode referenced: 60891523 May 20 22:15:21 backupserver kernel: [11777489.424514] EXT3-fs error (device dm-8): ext3_lookup: deleted inode referenced: 60891533 May 20 22:15:21 backupserver kernel: [11777489.426153] EXT3-fs error (device dm-8): ext3_lookup: deleted inode referenced: 60891524
ao executar o e2fsck, esses erros são corrigidos, mas 2 ou 3 dias depois, esses erros retornam. Nós então recriamos o LVM e começamos tudo de novo. Agora este não é um sistema de backup estável.
Alguém pode esclarecer por que recebemos esses erros EXT3-fs e o que há de errado com nossa configuração?
Abaixo informações adicionais que podem ajudar
tune2fs na origem do rsnapshot
root@backupserver:/home/netsys# tune2fs -l /dev/mapper/vg0-lv1databackup tune2fs 1.42 (29-Nov-2011) Filesystem volume name: Last mounted on: Filesystem UUID: c150d0c9-cc31-41ab-85a5-3d63b79d0076 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 0 Free blocks: 143705208 Free inodes: 64168616 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width: 128 Filesystem created: Thu Sep 6 13:03:04 2012 Last mount time: Fri Jan 4 17:49:01 2013 Last write time: Fri Jan 4 17:49:01 2013 Mount count: 6 Maximum mount count: 27 Last checked: Wed Dec 12 15:03:33 2012 Check interval: 15552000 (6 months) Next check after: Mon Jun 10 16:03:33 2013 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 911d0866-e924-4069-8ce5-c945fbb6ee27 Journal backup: inode blocks
Tune2fs -l no volume do rsnapshot
root@backupserver:/home/netsys# tune2fs -l /dev/mapper/vg0-lv1data tune2fs 1.42 (29-Nov-2011) Filesystem volume name: Last mounted on: Filesystem UUID: c91740f4-17df-4518-9ef1-ba36b7820870 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file Filesystem flags: signed_directory_hash Default mount options: (none) Filesystem state: clean with errors Errors behavior: Continue Filesystem OS type: Linux Inode count: 65536000 Block count: 262144000 Reserved block count: 0 Free blocks: 127616425 Free inodes: 63661979 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 961 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 RAID stride: 128 RAID stripe width: 128 Filesystem created: Tue Sep 4 14:20:00 2012 Last mount time: Mon Apr 29 16:49:09 2013 Last write time: Tue May 21 06:52:48 2013 Mount count: 1 Maximum mount count: 23 Last checked: Mon Apr 29 10:18:08 2013 Check interval: 15552000 (6 months) Next check after: Sat Oct 26 10:18:08 2013 Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: 74faab9b-739f-47dd-ba48-059e5b06829a Journal backup: inode blocks
Uso do inode no volume rsnapshot
root@backupserver:/home/netsys# df -i /mnt/lv1data/ Filesystem Inodes IUsed IFree IUse% Mounted on /dev/mapper/vg0-lv1data 65536000 1874021 63661979 3% /mnt/lv1data
modinfo no driver para o LSI SAS2008
root@backupserver:/home/netsys# modinfo mpt2sas filename: /lib/modules/3.2.0-23-generic/kernel/drivers/scsi/mpt2sas/mpt2sas.ko version: 10.100.00.00 license: GPL description: LSI MPT Fusion SAS 2.0 Device Driver author: LSI Corporation srcversion: C1D4E89BF318C53971B5113 alias: pci:v00001000d0000007Esv*sd*bc*sc*i* alias: pci:v00001000d0000006Esv*sd*bc*sc*i* alias: pci:v00001000d00000087sv*sd*bc*sc*i* alias: pci:v00001000d00000086sv*sd*bc*sc*i* alias: pci:v00001000d00000085sv*sd*bc*sc*i* alias: pci:v00001000d00000084sv*sd*bc*sc*i* alias: pci:v00001000d00000083sv*sd*bc*sc*i* alias: pci:v00001000d00000082sv*sd*bc*sc*i* alias: pci:v00001000d00000081sv*sd*bc*sc*i* alias: pci:v00001000d00000080sv*sd*bc*sc*i* alias: pci:v00001000d00000065sv*sd*bc*sc*i* alias: pci:v00001000d00000064sv*sd*bc*sc*i* alias: pci:v00001000d00000077sv*sd*bc*sc*i* alias: pci:v00001000d00000076sv*sd*bc*sc*i* alias: pci:v00001000d00000074sv*sd*bc*sc*i* alias: pci:v00001000d00000072sv*sd*bc*sc*i* alias: pci:v00001000d00000070sv*sd*bc*sc*i* depends: scsi_transport_sas,raid_class intree: Y vermagic: 3.2.0-23-generic SMP mod_unload modversions parm: logging_level: bits for enabling additional logging info (default=0) parm: max_sectors:max sectors, range 64 to 8192 default=8192 (ushort) parm: max_lun: max lun, default=16895 (int) parm: max_queue_depth: max controller queue depth (int) parm: max_sgl_entries: max sg entries (int) parm: msix_disable: disable msix routed interrupts (default=0) (int) parm: missing_delay: device missing delay , io missing delay (array of int) parm: mpt2sas_fwfault_debug: enable detection of firmware fault and halt firmware - (default=0) parm: disable_discovery: disable discovery (int) parm: diag_buffer_enable: post diag buffers (TRACE=1/SNAPSHOT=2/EXTENDED=4/default=0) (int)
Versão do Kernel
root@backupserver:/home/netsys# uname -a Linux backupserver 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Versão
root@backupserver:/home/netsys# cat /etc/issue Ubuntu 12.04 LTS \n \l
Não usamos multipath ...
Atenciosamente
Wouter