Guest

Preview Tool

Cisco Bug: CSCtb89163 - CER 7.0.3. file system read-only mode after EXT3 Journal aborted error

Last Modified

Feb 09, 2017

Products (1)

  • Cisco Emergency Responder

Known Affected Releases

7.0(3)

Description (partial)

Symptom:
  
 File system goes to read only mode.

The following may be seen in the (RTMT-System Logs) or "messages" file on the
local server:
-------
kern 2 kernel: EXT3-fs error (device sda2): ext3_journal_start_sb: Detected
aborted journal

kern 2 kernel: Remounting filesystem read-only 
-------

You could also see the following in the "CiscoSyslog" file:
-------
SyslogSeverityMatchFound events generated:  SeverityMatch - Critical kernel:
EXT3-fs error (device sdb1) in start_transaction: Journal has aborted 

or

SyslogSeverityMatchFound Detail: At Tue Sep 01 23:01:03 CDT 2009 on node
10.120.200.33, the following SyslogSeverityMatchFound events generated: 
SeverityMatch - Critical kernel: EXT3-fs error (device sdb1) in
start_transaction: Journal has aborted

------------------------------
      To determine whether the root (/) partition is still writable, enter the
     following from CLI:
     utils iothrottle enable
     
     You should see the following message:
      "I/O throttling has been enabled"
     
     utils iothrottle disable
     
     You should see the following message:
      "I/O throttling has been disabled"
     
      To determine whether the /common partition is still writable, enter the
     following from CLI every 2 minutes:
     
     file list activelog syslog/* detail
     
     You should see the size of the file "CiscoSyslog" change, for e.g.
     
     589,219  CiscoSyslog
     
     and then approx. 2 minutes later:
     
     589,550  CiscoSyslog

        
      Conditions:
   
      Following hardware models are susceptible to the problem when installed or
     upgraded to CER release 7.0.3.10000-7:
            MCS 7835-I2 servers
            MCS 7845-I2 servers
            or
            customer-provided IBM xSeries x3650
      
     CER release can be identified from the product banner displayed on system
     console. Another way to find out CER release is to run platform admin CLI
     command "show version active".
      
      Hardware model can be identified by running platform admin CLI command 
  "show hardware".
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.