Hi

[EMAIL PROTECTED] wrote:

> Hi everyone,
>
> I've just recently upgraded from 2.4.1 with ReiserFS utils a to 2.4.8
> ReiserFS utils j.
>
> Things went well, although I haven't been able to convert my filesystems
> from 3.5. to the new 3.6 yet.
>
> Anyhow, I'm seeing data corruption and my box has frozen twice!  The server
> is a very active centralized syslog server.
>

It looks like you got corrupted files which were being appended at the time of crash. 
As
reiserfs does only metadata journalling then such files may appear to contain 
unexpected
data after filesystem mounting.
It would be interesting to find at which offset in a file the corruption starts. If it
starts at a block boundary - then metadata of file pointing to data  block managed to 
reach
disk, where as data block itself did not.
If not then I am not sure what happened with contents of log file. If block of file is 
not
filled completely it should contain 0s at unfilled areas, not random data.

As for reason of lockups, reiserfs could be a reason of it. Unfortunately, as you did 
not
notice what did the system say last (maybe it did not say anything) - the only thing 
we can
do is to recommend you to check reiserfs filesystems.

Thanks,
vs

>
> Any suggestions?  Please help, this a production system.
>
> Here is a sample from a log file.  As you can see, everything is fill till
> 14:15:01.  Then it locks.  And I rebooted (hard reset) at 10:29.
>
> Sep  6 14:15:00 hosvrlog CRON[2868]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch4-2.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:00 hosvrlog CRON[2869]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch4-1.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:00 hosvrlog CRON[2870]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch3-3.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:00 hosvrlog CRON[2874]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch3-2.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:00 hosvrlog CRON[2875]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch3-1.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:00 hosvrlog CRON[2876]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch2-3.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:00 hosvrlog CRON[2880]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch2-2.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:00 hosvrlog CRON[2881]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch2-1.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:01 hosvrlog CRON[2882]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoswitch1-1.cfg --logging /var/log/mrtg.log)
> Sep  6 14:15:01 hosvrlog CRON[2885]: (root) CMD (/usr/bin/mail_log.sh
> /var/log/powerpay.warn_email 0 [EMAIL PROTECTED]
> [EMAIL PROTECTED] > /dev/null 2>&1)
> Sep  6 14:15:01 hosvrlog CRON[2886]: (root) CMD (/usr/bin/mail_log.sh
> /var/log/powerpay.crit_email 0 [EMAIL PROTECTED]
> [EMAIL PROTECTED] > /dev/null 2>&1)
> 70.153.36.200</A> ICMP TTL:253 TOS:0x0 ID:0 IpLen:20 DgmLen:31 DF<br>Type:0
> Code:0  ID:512  Seq:32583  ECHO REPLY</code> <A HREF
> 
>="/LOGS/hosnortice/20010901/20010901.17/snort_logs/170.153.42.175/ICMP_ECHO_REPLY">[Snort
>
> log]</A>
> </td></tr>
> <tr><td bgcolor=#D5E2CE><code>[**] <a href
> ="../../../sig/sig11.html">HOTFALSE -   ICMP Unknown Type</A>
> [**]<br>09/01-17:27:54.341809 0:2:FD:6:C5:50 -> 0:D0:B7:47:7E:EB type:0x800
> len:0x3C<br><A HREF
> ="../../../192/168/20/src192.168.20.201.html">192.168.20.201</A> -> <A HREF
> ="../../../170/153/36/dest170.153.36.200.html">170.153.36.200</A> ICMP
> TTL:252 TOS:0x0 ID:0 IpLen:20 DgmLen:31 DF<br>Type:0  Code:0  ID:512
> Seq:32839  ECHO REPLY</code> <A HREF
> 
>="/LOGS/hosnortice/20010901/20010901.17/snort_logs/192.168.20.201/ICMP_ECHO_REPLY">[Snort
>
> log]</A>
> </td></tr>
> <tr><td bgcolor=#E7DEBD><code>[**] <a href
> ="../../../sig/sig11.html">HOTFALSE -   ICMP Unknown Type</A>
> [**]<br>09/01-17:27:54.346743 8:0:20:CD:BF:82 -> 0:D0:B7:47:7E:EB
> type:0x800 len:0x3C<br><A HREF
> ="../../../192/168/10/src192.168.10.201.html">192.168.10.201</A> -> <A HREF
> ="../../../170/153/36/dest170.153.36Sep  7 10:29:38 hosvrlog
> syslog-ng[344]: syslog-ng version 1.5.5a starting
> Sep  7 10:29:38 hosvrlog inetd[357]: Online and ready (2 sockets)
> Sep  7 10:29:39 hosvrlog xntpd[368]: xntpd 3-5.93 Wed Jan 31 12:09:04 CST
> 2001 (1)
> Sep  7 10:29:39 hosvrlog xntpd[368]: tickadj = 5, tick = 10000, tvu_maxslew
> = 495, est. hz = 100
> Sep  7 10:29:39 hosvrlog xntpd[368]: precision = 11 usec
> Sep  7 10:29:39 hosvrlog cron[372]: (CRON) STARTUP (fork ok)
> Sep  7 10:30:00 hosvrlog CRON[449]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hoinet.cfg^I^I^I--logging /var/log/mrtg.log)
> Sep  7 10:30:00 hosvrlog CRON[447]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/coninet.cfg^I^I--logging /var/log/mrtg.log)
> Sep  7 10:30:00 hosvrlog CRON[452]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/concache.cfg^I^I--logging /var/log/mrtg.log)
> Sep  7 10:30:00 hosvrlog CRON[453]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hortrmain.cfg^I^I--logging /var/log/mrtg.log)
> Sep  7 10:30:00 hosvrlog CRON[457]: (root) CMD (/usr/bin/mrtg
> /etc/mrtg/hocache.cfg^I^I--logging /var/log/mrtg.log)
>
> John Delisle
> Corporate Technology
> Ceridian Canada Ltd
> 204-975-5909
>
> **********************************************************************
> This e-mail and any files transmitted with it are considered
> confidential and are intended solely for the use of the
> individual or entity to whom they are addressed (intended).
> This communication is subject to agent/client privilege.
> If you are not the intended recipient (received in error) or
> the person responsible for delivering the e-mail to the
> intended recipient, be advised that you have received this
> e-mail in error and that any use, dissemination, forwarding,
> printing or copying of this e-mail is strictly prohibited.  If
> you have received this e-mail in error please notify the
> sender immediately.
>
> **********************************************************************

Reply via email to