petit conseil

[Sandeman]

donc +1 sur le filesystem en read-only

résultat de la commande mount stp

[casa]

ik:~# mount

/dev/md1 on / type ext3 (rw,errors=remount-ro)

proc on /proc type proc (rw)

devpts on /dev/pts type devpts (rw,gid=5,mode=620)

/dev/md0 on /boot type ext2 (rw)

ik:~#

je fais ce que tu a dit plus haut ?

[Sandeman]

hum c'est bizarroide, il dit bien rw, alors qu'il voit read-only ...

si tu reboot et que tu n'as pas la main, tu es encore obligé d'appeler ton hébergeur ?

dmesg ne te dis pas quelque chose comme "filesystem errors found, remounting read-only" ?

[casa]

08 001 01 0 0 0 0 0 1 1 69

09 001 01 1 1 0 0 0 1 1 71

0a 001 01 0 0 0 0 0 1 1 79

0b 001 01 0 0 0 0 0 1 1 81

0c 001 01 0 0 0 0 0 1 1 89

0d 001 01 0 0 0 0 0 1 1 91

0e 001 01 0 0 0 0 0 1 1 99

0f 001 01 0 0 0 0 0 1 1 A1

10 001 01 1 1 0 1 0 1 1 A9

11 001 01 1 1 0 1 0 1 1 B1

12 001 01 1 1 0 1 0 1 1 B9

13 001 01 1 1 0 1 0 1 1 C1

14 001 01 1 1 0 1 0 1 1 C9

15 000 00 1 0 0 0 0 0 0 00

16 000 00 1 0 0 0 0 0 0 00

17 000 00 1 0 0 0 0 0 0 00

IRQ to pin mappings:

IRQ0 -> 0:2

IRQ1 -> 0:1

IRQ3 -> 0:3

IRQ4 -> 0:4

IRQ5 -> 0:5

IRQ6 -> 0:6

IRQ7 -> 0:7

IRQ8 -> 0:8

IRQ9 -> 0:9

IRQ10 -> 0:10

IRQ11 -> 0:11

IRQ12 -> 0:12

IRQ13 -> 0:13

IRQ14 -> 0:14

IRQ15 -> 0:15

IRQ16 -> 0:16

IRQ17 -> 0:17

IRQ18 -> 0:18

IRQ19 -> 0:19

IRQ20 -> 0:20

.................................... done.

Using local APIC timer interrupts.

calibrating APIC timer ...

..... CPU clock speed is 2394.0103 MHz.

..... host bus clock speed is 99.7504 MHz.

cpu: 0, clocks: 997504, slice: 498752

CPU0<T0:997504,T1:498752,D:0,S:498752,C:997504>

Waiting on wait_init_idle (map = 0x0)

All processors have done init_idle

PCI: PCI BIOS revision 2.10 entry at 0xf0031, last bus=1

PCI: Using configuration type 1

PCI: Probing PCI hardware

PCI: Probing PCI hardware (bus 00)

PCI: Ignoring BAR0-3 of IDE controller 00:1f.1

Transparent bridge - Intel Corp. 82801BA/CA/DB/EB PCI Bridge

PCI: Using IRQ router PIIX/ICH [8086/24d0] at 00:1f.0

PCI->APIC IRQ transform: (B0,I2,P0) -> 16

PCI->APIC IRQ transform: (B0,I29,P0) -> 16

PCI->APIC IRQ transform: (B0,I29,P1) -> 19

PCI->APIC IRQ transform: (B0,I29,P2) -> 18

PCI->APIC IRQ transform: (B0,I29,P0) -> 16

PCI->APIC IRQ transform: (B0,I31,P0) -> 18

PCI->APIC IRQ transform: (B0,I31,P0) -> 18

PCI->APIC IRQ transform: (B0,I31,P1) -> 17

PCI->APIC IRQ transform: (B1,I8,P0) -> 20

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

Starting kswapd

VFS: Disk quotas vdquot_6.5.1

Journalled Block Device driver loaded

pty: 256 Unix98 ptys configured

Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled

ttyS00 at 0x03f8 (irq = 4) is a 16550A

floppy0: no floppy controllers found

[drm] Initialized tdfx 1.0.0 20010216 on minor 0

[drm] Initialized radeon 1.7.0 20020828 on minor 1

Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4

ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx

hda: MAXTOR 6L040J2, ATA DISK drive

hdb: MAXTOR 6L040J2, ATA DISK drive

ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

hda: attached ide-disk driver.

hda: host protected area => 1

hda: 78177792 sectors (40027 MB) w/1818KiB Cache, CHS=77557/16/63

hdb: attached ide-disk driver.

hdb: host protected area => 1

hdb: 78177792 sectors (40027 MB) w/1819KiB Cache, CHS=77557/16/63

Partition check:

hda: hda1 hda2 hda3

hdb: hdb1 hdb2 hdb3

SCSI subsystem driver Revision: 1.00

kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2

md: raid0 personality registered as nr 2

md: raid1 personality registered as nr 3

md: raid5 personality registered as nr 4

raid5: measuring checksumming speed

8regs : 2765.600 MB/sec

32regs : 2062.400 MB/sec

pIII_sse : 3115.600 MB/sec

pII_mmx : 2820.000 MB/sec

p5_mmx : 2770.000 MB/sec

raid5: using function: pIII_sse (3115.600 MB/sec)

md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27

md: Autodetecting RAID arrays.

[events: 0000002e]

[events: 00000025]

[events: 0000002e]

[events: 00000025]

md: autorun ...

md: considering hdb3 ...

md: adding hdb3 ...

md: adding hda3 ...

md: created md1

md: bind<hda3,1>

md: bind<hdb3,2>

md: running: <hdb3><hda3>

md: hdb3's event counter: 00000025

md: hda3's event counter: 00000025

md: md1: raid array is not clean -- starting background reconstruction

md: RAID level 1 does not need chunksize! Continuing anyway.

md1: max total readahead window set to 124k

md1: 1 data-disks, max readahead per data-disk: 124k

raid1: device hdb3 operational as mirror 1

raid1: device hda3 operational as mirror 0

raid1: raid set md1 not clean; reconstructing mirrors

raid1: raid set md1 active with 2 out of 2 mirrors

md: updating md1 RAID superblock on device

md: hdb3 [events: 00000026]<6>(write) hdb3's sb offset: 37961664

md: hda3 [events: 00000026]<6>(write) hda3's sb offset: 37953472

md: considering hdb1 ...

md: adding hdb1 ...

md: adding hda1 ...

md: created md0

md: bind<hda1,1>

md: bind<hdb1,2>

md: running: <hdb1><hda1>

md: hdb1's event counter: 0000002e

md: hda1's event counter: 0000002e

md: md0: raid array is not clean -- starting background reconstruction

md: RAID level 1 does not need chunksize! Continuing anyway.

md0: max total readahead window set to 124k

md0: 1 data-disks, max readahead per data-disk: 124k

raid1: device hdb1 operational as mirror 1

raid1: device hda1 operational as mirror 0

md: syncing RAID array md1

md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.

md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.

md: using 124k window, over a total of 37953472 blocks.

raid1: raid set md0 not clean; reconstructing mirrors

raid1: raid set md0 active with 2 out of 2 mirrors

md: updating md0 RAID superblock on device

md: hdb1 [events: 0000002f]<6>(write) hdb1's sb offset: 102720

md: delaying resync of md0 until md1 has finished resync (they share one or more physical units)

md: hda1 [events: 0000002f]<6>(write) hda1's sb offset: 104320

md: ... autorun DONE.

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

IP: routing cache hash table of 4096 buckets, 32Kbytes

TCP: Hash tables configured (established 32768 bind 32768)

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

kjournald starting. Commit interval 5 seconds

EXT3-fs: mounted filesystem with ordered data mode.

VFS: Mounted root (ext3 filesystem) readonly.

Freeing unused kernel memory: 292k freed

Adding Swap: 1028152k swap-space (priority -1)

EXT3 FS 2.4-0.9.19, 19 August 2002 on md(9,1), internal journal

8139too Fast Ethernet driver 0.9.26

via-rhine.c:v1.10-LK1.1.19 July-12-2003 Written by Donald Becker

http://www.scyld.com/network/via-rhine.html

eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100.html

eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others

eth0: PCI device 8086:1050 (Intel Corp.), 00:0C:F1:DB:25:CD, IRQ 20.

Board assembly 000000-000, Physical connectors present: RJ45

Primary interface chip i82555 PHY #1.

General self-test: passed.

Serial sub-system self-test: passed.

Internal registers self-test: passed.

ROM checksum self-test: passed (0xed626fe2).

ICH5: IDE controller at PCI slot 00:1f.1

PCI: Enabling device 00:1f.1 (0005 -> 0007)

ICH5: chipset revision 2

ICH5: not 100% native mode: will probe irqs later

ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA

ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio

ICH5-SATA: IDE controller at PCI slot 00:1f.2

ICH5-SATA: chipset revision 2

ICH5-SATA: 100% native mode on irq 18

ide2: BM-DMA at 0xd800-0xd807, BIOS settings: hde:pio, hdf:pio

ide3: BM-DMA at 0xd808-0xd80f, BIOS settings: hdg:pio, hdh:pio

ttyS1: LSR safety check engaged!

ttyS1: LSR safety check engaged!

md: md1: sync done.

md: syncing RAID array md0

md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.

md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.

md: using 124k window, over a total of 102720 blocks.

md: md0: sync done.

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3538948: rec_len % 4 != 0 - offset=0, inode=1179403647, rec_len=257, name_len=1

Aborting journal on device md(9,1).

ext3_abort called.

EXT3-fs abort (device md(9,1)): ext3_journal_start: Detected aborted journal

Remounting filesystem read-only

Remounting filesystem read-only

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3538948: rec_len % 4 != 0 - offset=0, inode=1179403647, rec_len=257, name_len=1

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3555340: rec_len % 4 != 0 - offset=0, inode=1179403647, rec_len=257, name_len=1

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3538952: rec_len % 4 != 0 - offset=0, inode=1936614755, rec_len=15717, name_len=71

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3555342: directory entry across blocks - offset=0, inode=2777536649, rec_len=65156, name_len=255

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

ik86:~#

question con esceque je peux rebooter a distance comme unwindows

j'ai pas trouver de commande

[-rem-]

"reboot" tout betement comme commande....

j'ai un peu zappe les autres posts que vous avez echange entre temps, mais ca n'a rien fait la reconstruction du raid array ? Apparement ton sys a l'ai pas mal nicke qd meme....

[casa]

je resume

je revient ce matin

et je fait un tous petit

apt-get update

reponse :

ik86:~# apt-get update

Hit http://ftp.fr.debian.org stable/main Packages

Hit http://ftp.fr.debian.org stable/main Release

Hit http://ftp.fr.debian.org stable/contrib Packages

Hit http://ftp.fr.debian.org stable/contrib Release

Hit http://ftp.fr.debian.org stable/non-free Packages

Hit http://ftp.fr.debian.org stable/non-free Release

Hit http://security.debian.org stable/updates/main Packages

Hit http://security.debian.org stable/updates/main Release

Hit http://security.debian.org stable/updates/contrib Packages

Hit http://security.debian.org stable/updates/contrib Release

Hit http://security.debian.org stable/updates/non-free Packages

Hit http://security.debian.org stable/updates/non-free Release

W: Not using locking for read only lock file /var/lib/apt/lists/lock

W: Not using locking for read only lock file /var/lib/dpkg/lock

E: Unable to write to /var/cache/apt/

E: The package lists or status file could not be parsed or opened.

ik86:~#

n'importe quelle commande me dit

en gros cela

W: Not using locking for read only lock file /var/lib/apt/lists/lock

W: Not using locking for read only lock file /var/lib/dpkg/lock

E: Unable to write to /var/cache/apt/

E: The package lists or status file could not be parsed or opened

[Sandeman]

md: md0: sync done.

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3538948: rec_len % 4 != 0 - offset=0, inode=1179403647, rec_len=257, name_len=1

Aborting journal on device md(9,1).

ext3_abort called.

EXT3-fs abort (device md(9,1)): ext3_journal_start: Detected aborted journal

Remounting filesystem read-only

Remounting filesystem read-only

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3538948: rec_len % 4 != 0 - offset=0, inode=1179403647, rec_len=257, name_len=1

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3555340: rec_len % 4 != 0 - offset=0, inode=1179403647, rec_len=257, name_len=1

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3538952: rec_len % 4 != 0 - offset=0, inode=1936614755, rec_len=15717, name_len=71

EXT3-fs error (device md(9,1)): ext3_readdir: bad entry in directory #3555342: directory entry across blocks - offset=0, inode=2777536649, rec_len=65156, name_len=255

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

EXT3-fs error (device md(9,1)) in start_transaction: Journal has aborted

ik86:~#

Comme tu t'en doute tout ça ^ c'est pas bon signe.

je confirme donc mon diag (sorry Rémy ), fs en read-only, les inconsistences étaient dues au fait que tu as modifié des données sur ton disque pendant qu'il reconstituait le RAID, et donc qu'il y a une différence entre le journal et l'arborescence réelle du disque.

Pour rebooter, la commande est ... reboot ... (ou shutdown -r now pour les puristes).

Mais là, ce qu'il va se passer c'est qu'au redémarrage, il va s'arrêter pendant l'init 1 en disant (en gros)

fsck has found errors on device /dev/machin

you must run fsck manually

Enter root password or (Ctrl-D) for normal startup :

(et ça sera *uniquement* en console, pas en réseau ... donc si tu as personne sur place, gloups).

Sinon tu peux peut-être lancer une resync du RAID à condition de ne RIEN TOUCHE pendant les qq heures que ça va durer, mais je ne peux pas te garantir l'issue.

[casa]

la commande

pour une resynchro ? steplais

je vais tester sa ou je vias les appeleler

merci beaucoup

[tuXXX]

kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2

md: raid0 personality registered as nr 2

md: raid1 personality registered as nr 3

md: raid5 personality registered as nr 4

raid5: measuring checksumming speed

  8regs    :  2765.600 MB/sec

  32regs    :  2062.400 MB/sec

  pIII_sse  :  3115.600 MB/sec

  pII_mmx  :  2820.000 MB/sec

  p5_mmx    :  2770.000 MB/sec

raid5: using function: pIII_sse (3115.600 MB/sec)

md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27

md: Autodetecting RAID arrays.

[events: 0000002e]

[events: 00000025]

[events: 0000002e]

[events: 00000025]

md: autorun ...

md: considering hdb3 ...

md:  adding hdb3 ...

md:  adding hda3 ...

md: created md1

md: bind<hda3,1>

md: bind<hdb3,2>

md: running: <hdb3><hda3>

md: hdb3's event counter: 00000025

md: hda3's event counter: 00000025

md: md1: raid array is not clean -- starting background reconstruction

md: RAID level 1 does not need chunksize! Continuing anyway.

md1: max total readahead window set to 124k

md1: 1 data-disks, max readahead per data-disk: 124k

raid1: device hdb3 operational as mirror 1

raid1: device hda3 operational as mirror 0

raid1: raid set md1 not clean; reconstructing mirrors

raid1: raid set md1 active with 2 out of 2 mirrors

md: updating md1 RAID superblock on device

md: hdb3 [events: 00000026]<6>(write) hdb3's sb offset: 37961664

md: hda3 [events: 00000026]<6>(write) hda3's sb offset: 37953472

md: considering hdb1 ...

md:  adding hdb1 ...

md:  adding hda1 ...

md: created md0

md: bind<hda1,1>

md: bind<hdb1,2>

md: running: <hdb1><hda1>

md: hdb1's event counter: 0000002e

md: hda1's event counter: 0000002e

md: md0: raid array is not clean -- starting background reconstruction

md: RAID level 1 does not need chunksize! Continuing anyway.

md0: max total readahead window set to 124k

md0: 1 data-disks, max readahead per data-disk: 124k

raid1: device hdb1 operational as mirror 1

raid1: device hda1 operational as mirror 0

md: syncing RAID array md1

md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.

md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.

md: using 124k window, over a total of 37953472 blocks.

raid1: raid set md0 not clean; reconstructing mirrors

raid1: raid set md0 active with 2 out of 2 mirrors

md: updating md0 RAID superblock on device

md: hdb1 [events: 0000002f]<6>(write) hdb1's sb offset: 102720

md: delaying resync of md0 until md1 has finished resync (they share one or more physical units)

md: hda1 [events: 0000002f]<6>(write) hda1's sb offset: 104320

md: ... autorun DONE.

[...]

md: md1: sync done.

md: syncing RAID array md0

md: minimum _guaranteed_ reconstruction speed: 100 KB/sec/disc.

md: using maximum available idle IO bandwith (but not more than 100000 KB/sec) for reconstruction.

md: using 124k window, over a total of 102720 blocks.

md: md0: sync done.

Bon, il y a un pb avec le raid1 logiciel...

(toutes les lignes avec "md", y'a qu'à lire...)

[Sandeman]

la commande

pour une resynchro ? steplais

je vais tester sa ou je vias les appeleler

euh ...

la commande mdadm a plein de paramètres possibles et franchement je ne l'utilise jamais (pour l'instant, je touche du bois ...)

[-rem-]

W: Not using locking for read only lock file /var/lib/apt/lists/lock

W: Not using locking for read only lock file /var/lib/dpkg/lock

E: Unable to write to /var/cache/apt/

Mauvais mauvais

e confirme donc mon diag (sorry Rémy  ), fs en read-only, les inconsistences étaient dues au fait que tu as modifié des données sur ton disque pendant qu'il reconstituait le RAID, et donc qu'il y a une différence entre le journal et l'arboresce

Oui c'est vrai sandeman, je reconnais, mais comme je l'ai precise, ce n'est pas un bon controleur raid, il n'y en a ptet meme pas.... Nous on utilise ( au boulot, pas chez moi ) des controleurs hardware raid scsi qui sont completement transparent pour le systeme, ils sont assume par le bios en tant que controleur et quoi que tu installes dessus, ( unix ou linux ) tu ne vois jamais autre chose qu'un seul disque. On a meme pas de /etc/raidtab, et tu peux vraiment arracher un disque dur au hasard a chaud, meme pendant une recompil de noyau ou un truc dans le genre. Vu qu'il parlait d'un serveur, je pensais que c'etait ce genre de machine, donc, le raid est totalement invisible, ce qui fait qu'il ne peut pas etre la cause d'erreur de ce genre. Mais je pense que tu as plus d'experience que moi dans le raid software, car a part chez moi je n'en fais pas. je connais pas trop trop mal comment ca marche maintenant, mais sans plus.

Enter root password or (Ctrl-D) for normal startup :

(et ça sera *uniquement* en console, pas en réseau ... donc si tu as personne sur place, gloups).

oui, la le monsieur il a encore raison et sans un gus sur place, c'est plutot mal....

tu penses que le raid software arriverait a se reconstruire comme ca sandeman ?

[casa]

bon je vous tient au courant

en attendant

je vais chercher de howto

alternc je laisse tomber

ispman je laisser tomber

bref je sais pu

[-rem-]

ta premiere solution qui marchait a peu pres etait pas mal, moi j'aurais ecoute sandeman en essayant d'ecrire un daemon assez leger ( surtout si bcp de traffic ) qui modifie le nom sous la forme qui t'interesse, et c'est regle....

[casa]

ok

je vais faire cela

MAINTENANT j'ecoute !!!!!

vous utiliser koi vous pour vos stats de serveur de mail

nobr envoyer nbr recu virus filtrer ......

[casa]

arf les vieux demon revienne !!!

vous en penssez koi de ca ?

http://www.y0m.net/tutos/qmail-debian/

[Sandeman]

qmail

[casa]

ok j'ecoute

[-rem-]

ben serveur de mail je connais pas trop, je ne m'en occupe pas, moi je fais plutot tout ce qui est applis distribuees ( calculs etc...) et technologies Web ( non mail ), sandeman est surement bien mieux place que moi pour repondre a la question.

[tuXXX]

ok j'ecoute

Je serait etnté de dire "stfw"...

Attends pas que tout te tombe maché directement...

[Sandeman]

Sinon je peux (au nom de ma boîute) te proposer une presta de 3 jours : 1032 € / jour + frais de déplacement.

mais c'est de l'expert, là :)

[casa]

pffff

en dernier recourt !!!!!

je vias pas partir en vacances sinon

bas je vais remettre le museaux dans ispman

et je vous jure il va charger (ailaail mon raid)

[-rem-]

Sinon je peux (au nom de ma boîute) te proposer une presta de 3 jours : 1032 € / jour + frais de déplacement.

mais c'est de l'expert, là :)

Le pb c'est que ca , necessite pas un expert pour installer sandeman, enfin, je veux dire c'est pas le mec qui a mla installe le truc apparement, ca fonctionnait....C'est plutot la formation qu'il faudrait !

ps : 3 jour pour installer un serveur de mail sous debian...didiou ! lol