[FUG-BR] Servidor travando

[Marcelo Beckmann]

Silmar Oliveira escreveu:
>> On 9/27/07, Marcio Antunes <mantunes.listas em gmail.com> wrote:
>>> Faço jus a palavras do amigo Welington..
>>>
>>> use  amd64 ele é compativel com EM64T
>> Exatamente ! E existem alguns drivers que não funcionam bem com PAE.
> 
> Pow... vacilei legal...
> Acredito que não, mas não custa perguntar :) Existe alguma forma de
> mudar para amd64 através de alguma atualização?
> 
> Outra coisa, quando dou um fsck -y, ele me retorna isso:
> 
> 25 files, 8 used, 506479 free (39 frags, 63305 blocks, 0.0% fragmentation)
> ** /dev/aacd0s1e (NO WRITE)
> ** Last Mounted on /usr
> ** Phase 1 - Check Blocks and Sizes
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> UNREF FILE I=1275070  OWNER=root MODE=100444
> SIZE=133233 MTIME=Sep 20 11:23 2007
> CLEAR? no
> 
> ** Phase 5 - Check Cyl groups
> FREE BLK COUNT(S) WRONG IN SUPERBLK
> SALVAGE? no
> 
> 202855 files, 4345764 used, 731315 free (37467 frags, 86731 blocks,
> 0.7% fragmentation)
> ** /dev/aacd0s1f (NO WRITE)
> ** Last Mounted on /var
> ** Phase 1 - Check Blocks and Sizes
> INCORRECT BLOCK COUNT I=967210 (4 should be 0)
> CORRECT? no
> 
> ** Phase 2 - Check Pathnames
> ** Phase 3 - Check Connectivity
> ** Phase 4 - Check Reference Counts
> LINK COUNT FILE I=894982  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 11:00 2007  COUNT 2 SHOULD BE 1
> ADJUST? no
> 
> LINK COUNT FILE I=895001  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 10:33 2007  COUNT 2 SHOULD BE 1
> ADJUST? no
> 
> UNREF FILE  I=895002  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 09:55 2007
> RECONNECT? no
> 
> 
> CLEAR? no
> 
> LINK COUNT FILE I=895036  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 10:44 2007  COUNT 2 SHOULD BE 1
> ADJUST? no
> 
> LINK COUNT FILE I=895039  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 10:55 2007  COUNT 2 SHOULD BE 1
> ADJUST? no
> 
> LINK COUNT FILE I=895041  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 10:00 2007  COUNT 2 SHOULD BE 1
> ADJUST? no
> 
> LINK COUNT FILE I=895173  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 10:22 2007  COUNT 2 SHOULD BE 1
> ADJUST? no
> 
> LINK COUNT FILE I=895174  OWNER=operator MODE=100400
> SIZE=2048 MTIME=Sep 28 10:11 2007  COUNT 2 SHOULD BE 1
> ADJUST? no
> 
> UNREF FILE  I=967210  OWNER=mysql MODE=100660
> SIZE=0 MTIME=Sep 28 11:10 2007
> RECONNECT? no
> 
> 
> CLEAR? no
> 
> UNREF FILE I=1601569  OWNER=mysql MODE=100600
> SIZE=0 MTIME=Sep 27 23:59 2007
> CLEAR? no
> 
> UNREF FILE I=1601571  OWNER=mysql MODE=100600
> SIZE=541 MTIME=Sep 28 01:02 2007
> CLEAR? no
> 
> UNREF FILE I=1601659  OWNER=mysql MODE=100600
> SIZE=0 MTIME=Sep 27 23:59 2007
> CLEAR? no
> 
> UNREF FILE I=1601676  OWNER=mysql MODE=100600
> SIZE=0 MTIME=Sep 27 23:59 2007
> CLEAR? no
> 
> UNREF FILE I=1601881  OWNER=mysql MODE=100600
> SIZE=0 MTIME=Sep 27 23:59 2007
> CLEAR? no
> 
> UNREF FILE I=2355215  OWNER=root MODE=140666
> SIZE=0 MTIME=Sep 27 23:59 2007
> CLEAR? no
> 
> ** Phase 5 - Check Cyl groups
> FREE BLK COUNT(S) WRONG IN SUPERBLK
> SALVAGE? no
> 
> SUMMARY INFORMATION BAD
> SALVAGE? no
> 
> BLK(S) MISSING IN BIT MAPS
> SALVAGE? no
> 
> Os outros dispositivos estão normais...
> Isto representa bad block ou será que é apenas alguma inconsistência?
> Haveria como eu verificar isso. Obs.: executei o fsck -y com a máquina
> em operação. 

É uma falta de atenção ao que já foi explicado algumas vezes na lista:
não se deve rodar fsck com a máquina em produção. Isso gera falsos
positivos.