search for: ext3_journal_start_sb

...er I/O error on device md2, logical block 3511697840 Oct 28 06:00:06 server2 kernel: lost page write due to I/O error on md2 Oct 28 06:00:06 server2 kernel: Aborting journal on device md2. Oct 28 06:05:01 server2 kernel: ext3_abort called. Oct 28 06:05:01 server2 kernel: EXT3-fs error (device md2): ext3_journal_start_sb: Detected aborted journal Oct 28 06:05:01 server2 kernel: Remounting filesystem read-only Now the root filesystem is remounted read-only. Running fsck on it produces the following: server2:~# e2fsck /dev/md2 e2fsck 1.37 (21-Mar-2005) Pass 1: Checking inodes, blocks, and sizes Inode 8 has illegal...

...13, name_len=101 May 6 06:22:27 srv1a kernel: Aborting journal on device drbd0. May 6 06:22:28 srv1a kernel: journal commit I/O error May 6 06:22:28 srv1a kernel: ext3_abort called. May 6 06:22:28 srv1a kernel: journal commit I/O error May 6 06:22:28 srv1a kernel: EXT3-fs error (device drbd0): ext3_journal_start_sb: Detected aborted journal May 6 06:22:28 srv1a kernel: ext3_abort called. May 6 06:22:28 srv1a kernel: EXT3-fs error (device drbd0): ext3_journal_start_sb: Detected aborted journal May 6 06:22:28 srv1a kernel: Remounting filesystem read-only May 6 06:22:28 srv1a kernel: __journal_remove_journal...

...rve_inode_write: Journal has aborted EXT3-fs error (device hda1) in ext3_orphan_del: Journal has aborted EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has aborted EXT3-fs error (device hda1) in ext3_delete_inode: Journal has aborted ext3_abort called. EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only audit(1204110895.260:2): audit_pid=0 old=0 by auid=4294967295 audit(1204110895.270:3): audit_backlog_limit=256 old=64 by auid=4294967295 NET: Registered protocol family 10 lo: Disabled Privacy Extensions IPv6 over IPv4 tunneling driver the...

I recently came across an enormous cluster of x86 clone machines running fedora core 1 (2.4.24) which have typically all intel or amd have VIA IDE chipsets. They frequently experience corrupted journals rendering the ext3 partition in read-only mode. More important than recovering the filesystem, I am interested in finding the root of the problem. The common hardware that all of these

...f PATA drives connected to a 3ware card in RAID10 configuration. EXT3-fs error (device dm-4): ext3_add_entry: bad entry in directory #14370410: rec_len % 4 != 0 - offset=0, inode=1309281588, rec_len=16761, name_len=78 Aborting journal on device dm-4. ext3_abort called. EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device dm-4) in start_transaction: Journal has aborted EXT3-fs error (device dm-4) in ext3_create: IO failure __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data

...kernel: Add. Sense: Logical unit not ready, initializing command required kernel: end_request: I/O error, dev sde, sector 63 kernel: Buffer I/O error on device sde1, logical block 0 kernel: lost page write due to I/O error on sde1 kernel: ext3_abort called. kernel: EXT3-fs error (device sde1): ext3_journal_start_sb: Detected aborted journal kernel: Remounting filesystem read-only I can guess that I/O means Input/Output, but other than that I'm flummoxed. My fear is that the Seagate is defective. Can someone point me in a good direction? Any input would be greatly appreciated.

...try in directory #869973: directory entry across bloc ks - offset=0, inode=3915132787, rec_len=42464, name_len=11 Feb 24 04:48:20 linbackup1 kernel: Aborting journal on device md3. Feb 24 04:48:20 linbackup1 kernel: ext3_abort called. Feb 24 04:48:20 linbackup1 kernel: EXT3-fs error (device md3): ext3_journal_start_sb: Detected aborted journal Feb 24 04:48:20 linbackup1 kernel: Remounting filesystem read-only Feb 24 04:48:33 linbackup1 kernel: EXT3-fs error (device md3): htree_dirblock_to_tree: bad entry in directory #4212181: rec_len % 4 != 0 - offse t=0, inode=4054525677, rec_len=1183, name_len=121 ---- ...

...ernel: EXT3-fs error (device dm-4): read_block_bitmap: Cannot read block bitmap - block_group = 68, block_bitmap = 2228224 Aug 5 10:48:57 inet05 kernel: Aborting journal on device dm-4. Aug 5 10:48:57 inet05 kernel: ext3_abort called. Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal Aug 5 10:48:57 inet05 kernel: Remounting filesystem read-only Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in ext3_reserve_inode_write: Journal has aborted Aug 5 10:48:57 inet05 kernel: EXT3-fs error (device dm-4) in start_transaction: Journal has aborted...

...ur case, just at the problem started found the line in log file as follows: EXT3-fs error (device dm-12): edxt3_find_entry: reading directory #2015496 offset 2 Then one blank line Then the line is Aborting journal on device dm-12. ext3_abort called Ext3-fs error (device dm-12): ext3_journal_start_sb: Detected aborted journal Remounting filesysem read-only Then the continuous line as follows: EXT3-fs error (device dm-12) in start_transaction: Journal has aborted The above message is continuous until we remount the filesystem and partion becomes 'read-write'. We could n...

...e_dirblock_to_tree: bad entry in directory #1330023: rec_len % 4 != 0 - offset=10264, inode=808542775, rec_len=13621, name_len=100 Dec 9 04:30:35 nx10 kernel: Aborting journal on device hda3. Dec 9 04:30:35 nx10 kernel: ext3_abort called. Dec 9 04:30:35 nx10 kernel: EXT3-fs error (device hda3): ext3_journal_start_sb: Detected aborted journal Dec 9 04:30:35 nx10 kernel: Remounting filesystem read-only The second error tonight happened about 5 minutes earlier. With exactly the same directory inode. http://www.google.de/search?as_q=centos+rec_len+4+0&hl=de&num=30&btnG=Google-Suche&as_epq=bad+en...

I've been trying to use fsck to recover a corrupted filesystem. It appears the original superblock is corrupted too, as it has an inode count of 0. When I start fsck with -b 32760, it uses the alternate superblock and proceeds. However, it restarts from the beginning a couple of times and after the second restart it doesn't use the alternate superblock, stopping instead as it can't

.... I have a strange problem with *one* of my domU''s, it seems like as soon as I do some heavy disk I/O, the filesystem goes read-only with this on the console: -- end_request: I/O error, dev hda1, sector 8822 Aborting journal on device hda1. ext3_abort called. EXT3-fs error (device hda1): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device hda1) in ext3_reserve_inode_write: Journal has aborted -- By the time this happens and I halt the domU and e2fsck (EXT3) the file (the domU belongs to) there is enough damage to render the filesystem useless (does not...

...a clamd[3978]: SelfCheck: Database status OK. Oct 18 03:00:03 shiva kernel: end_request: I/O error, dev sdb, sector 51083840 Oct 18 03:00:03 shiva kernel: Aborting journal on device sdb10. Oct 18 03:00:03 shiva kernel: ext3_abort called. Oct 18 03:00:03 shiva kernel: EXT3-fs error (device sdb10): ext3_journal_start_sb: Detected aborted journal Oct 18 03:00:03 shiva kernel: Remounting filesystem read-only Oct 18 03:00:03 shiva kernel: EXT3-fs error (device sdb10) in ext3_reserve_inode_write: Journal has aborted Oct 18 03:00:03 shiva kernel: EXT3-fs error (device sdb10) in ext3_reserve_inode_write: Journal has a...

...omUs were running for long time without any problems and I am pretty sure, that the hard drives are fine (checked with smart checks). [1215379.302679] EXT3-fs (xvda2): error in ext3_new_inode: IO failure [1215379.302689] Aborting journal on device xvda2. [1215379.304193] EXT3-fs (xvda2): error: ext3_journal_start_sb: Detected aborted journal [1215379.304200] EXT3-fs (xvda2): error: remounting filesystem read-only [1215379.329043] EXT3-fs (xvda2): error: remounting filesystem read-only [1215379.329246] EXT3-fs (xvda2): error in ext3_create: IO failure [1215379.330502] __journal_remove_journal_head: freeing b_c...

...rror, dev xvda2, sector 1454 end_request: I/O error, dev xvda2, sector 1522 end_request: I/O error, dev xvda2, sector 1652 end_request: I/O error, dev xvda2, sector 1788 end_request: I/O error, dev xvda2, sector 1902 Aborting journal on device xvda2. ext3_abort called. EXT3-fs error (device xvda2): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only DomU /var/log/messages contains Jun 25 10:34:29 xenpv1 kernel: SELinux: initialized (dev xvda2, type ext3),uses xattr Jun 25 10:34:34 xenpv1 kernel: end_request: I/O error, dev xvda2, sector 264182 Jun 25 10:34:34 xenpv1 kernel: print...

...ked up /proc/sys/dev/raid/speed_limit_min to 15000 so that it would reconstruct in a decent amount of time (the default of 1000 was leading to a 53 hour estimate for the recovery). But memtest.sh started kicking out errors (non-matching diffs). And then I got this: EXT3-fs error (device md0): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only attempt to access beyond end of device md0: rw=0, want=28987566088, limit=4595422208 attempt to access beyond end of device md0: rw=0, want=28987566088, limit=4595422208 attempt to access beyond end of device md0: rw=0, want=28987566088, li...

...up: unlinked inode 19698164 in dir #19696695 init_special_inode: bogus i_mode (73171) init_special_inode: bogus i_mode (154432) init_special_inode: bogus i_mode (34302) init_special_inode: bogus i_mode (131733) init_special_inode: bogus i_mode (30773) ext3_abort called. EXT3-fs error (device sdb2): ext3_journal_start_sb: Detected aborted journal Remounting filesystem read-only

...is too small for name_len - offset=103576, inode=3619715, rec_len=12, name_len=132 2007-08-02 04:02:25 kern.err www kernel: Aborting journal on device md2. 2007-08-02 04:02:25 kern.crit www kernel: ext3_abort called. 2007-08-02 04:02:25 kern.crit www kernel: EXT3-fs error (device md2): ext3_journal_start_sb: Detected aborted journal 2007-08-02 04:02:25 kern.crit www kernel: Remounting filesystem read-only I unmounted the filesystem and ran fsck, but though it detected that the filesystem had errors, it didn't report any findings during the check: fsck 1.35 (28-Feb-2004) e2fsck 1.35 (...

...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 De...

My test server was in very eavy load, running kolab's components: postfix, cyrus-imap and openldap A second test machine was sending, and reading emails as fast as it can. The CPU was never idle ! I left the server at about 17H30 and at 22H I find it "uncommitted" (difficult to work when the partition in read-only !) However the mount command report it as RW ! The /boot is still RW