[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Ext3 journal abort FC4+Updates




Dear All

Problem with ext3 fs on 3ware 9500S controller:

Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_add_entry: bad entry in directory #145998372: rec_len is smaller than minim
al - offset=0, inode=0, rec_len=0, name_len=0
Dec  7 05:59:50 stams kernel: Aborting journal on device sda1.
Dec  7 05:59:50 stams kernel: ext3_abort called.
Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
Dec  7 05:59:50 stams kernel: Remounting filesystem read-only
Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1) in ext3_reserve_inode_write: Journal has aborted Dec 7 05:59:50 stams kernel: EXT3-fs error (device sda1) in start_transaction: Journal has aborted Dec 7 05:59:51 stams kernel: EXT3-fs error (device sda1) in ext3_ordered_writepage: IO failure Dec 7 05:59:54 stams sshd(pam_unix)[25816]: session opened for user root by (uid=0) Dec 7 05:59:55 stams kernel: __journal_remove_journal_head: freeing b_committed_data
Dec  7 05:59:59 stams last message repeated 5 times
Dec 7 05:59:59 stams kernel: __journal_remove_journal_head: freeing b_frozen_data
Dec  7 05:59:59 stams last message repeated 5 times
Dec 7 05:59:59 stams kernel: __journal_remove_journal_head: freeing b_committed_data Dec 7 05:59:59 stams kernel: __journal_remove_journal_head: freeing b_frozen_data Dec 7 05:59:59 stams kernel: __journal_remove_journal_head: freeing b_frozen_data

On remount it suggests an fsck which seems to have recovered the problem.

System details:

Fedora Core 4 + all updates

uname -a
Linux <host>.strath.ac.uk 2.6.14-1.1644_FC4smp #1 SMP Sun Nov 27 03:39:31 EST 2005 i686 i686 i386 GNU/Linux

Tyan S5150 Tomcat i7221 motherboard
3GHz P4
3ware 9500S
4 disks in raid5:

//stams> info c0

Unit UnitType Status %Cmpl Stripe Size(GB) Cache AVerify IgnECC
------------------------------------------------------------------------------
u0    RAID-5    OK             -      64K     1117.56   ON     OFF      OFF

Port   Status           Unit   Size        Blocks        Serial
---------------------------------------------------------------
p0     OK               u0     372.61 GB   781422768     3NF02MK6
p1     OK               u0     372.61 GB   781422768     5NF14KV2
p2     OK               u0     372.61 GB   781422768     5NF14JQ9
p3     OK               u0     372.61 GB   781422768     5NF14KVK
p4     NOT-PRESENT      -      -           -             -
p5     NOT-PRESENT      -      -           -             -
p6     NOT-PRESENT      -      -           -             -
p7     NOT-PRESENT      -      -           -             -

//stams> info c0 p0 model
/c0/p0 Model = ST3400832AS

All disks the same as this, Seagate Barracuda 7200.8 SATA NCQ 400GB

Should I be concerned about this problem ?

Should I open a fedora bugzilla for it ?

Many thanks

Ian
--
Ian Thurlbeck                http://www.stams.strath.ac.uk/
Statistics and Modelling Science, University of Strathclyde
Livingstone Tower, 26 Richmond Street, Glasgow, UK,  G1 1XH
Tel: +44 (0)141 548 3667           Fax: +44 (0)141 552 2079


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]