search for: ext3_journal_start

A patch that implements acls on ext3 for kernel 2.2.x is available at http://moldybread.net/patch/kernel-2.2/ It looks to be stable. Beat it, break it.

Has anyone tried LFS (ie >2G files support) and Ext3 together? Are there good reasons why this should/should not work? I see the RH enterprise kernel patch set specifically does not attempt both lfs and ext3, but the lfs patches themselves touch some reasonably localised parts of ext2, so I would hope (without having dived in there to test), that the ext3 changes would mirror that

...r your help on something. My /boot filesystem is being remounted shortly after start-up as read-only. I get the following messages... journal_bmap_Ra7a5f568: journal block not found at offset 12 on ide0(3,1) Aborting journal on device ide0(3,1) ext3_abort called EXT3_fs abort (device ide0(3,1): ext3_journal_start: Detected aborted journal Remounting filesystem read-only Any ideas how I can fix this? My fstab looks like this... LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs de...

While compiling two kernels and untarring a third, my root fs was remounted r/w and I got the following in dmesg (kernel 2.4.19-pre9): EXT3-fs error (device ide0(3,2)) in ext3_new_inode: error 28 Aborting journal on device ide0(3,2). ext3_abort called EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal. Remounting filesystem read-only Remounting filesystem read-only EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in ext3_create: IO failur...

...+- 1 files changed, 1 insertion(+), 1 deletion(-) --- 25/fs/ext3/inode.c~ext3-transaction-reserved-blocks Sat Dec 14 18:28:21 2002 +++ 25-akpm/fs/ext3/inode.c Sat Dec 14 18:28:21 2002 @@ -2698,7 +2698,7 @@ void ext3_dirty_inode(struct inode *inod handle_t *handle; lock_kernel(); - handle = ext3_journal_start(inode, 1); + handle = ext3_journal_start(inode, 2); if (IS_ERR(handle)) goto out; if (current_handle && Cheers, Andreas -- Andreas Dilger http://sourceforge.net/projects/ext2resize/ http://www-mddsp.enel.ucalgary.ca/People/adilger/

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

Hi Andrew, The patch below addresses the problem we were talking about earlier where ext3_writepage ends up accessing the inode after the page lock has been dropped (and hence at a point where it is possible for the inode to have been reclaimed.) Tested minimally (it builds and boots.) It makes ext3_journal_stop take an sb, not an inode, as its final parameter. It also sets

...restart the transaction at a conventient checkpoint to make @@ -100,14 +128,9 @@ static handle_t *start_transaction(struct inode *inode) { - long needed; handle_t *result; - needed = inode->i_blocks; - if (needed > EXT3_MAX_TRANS_DATA) - needed = EXT3_MAX_TRANS_DATA; - - result = ext3_journal_start(inode, EXT3_DATA_TRANS_BLOCKS + needed); + result = ext3_journal_start(inode, blocks_for_truncate(inode)); if (!IS_ERR(result)) return result; @@ -123,14 +146,9 @@ */ static int try_to_extend_transaction(handle_t *handle, struct inode *inode) { - long needed; - if (handle->h_buffe...

...t3 partition has just gone crazy, with the following messages in dmesg: EXT3-fs error (device hda3): ext3_readdir: bad entry in directory #4603905: rec_len % 4 != 0 - offset=0, inode=2507704792, rec_len=42, name_len=0 Aborting journal on device hda3. ext3_abort called. EXT3-fs abort (device hda3): ext3_journal_start: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device hda3) in start_transaction: Journal has aborted EXT3-fs error (device hda3) in start_transaction: Journal has aborted [...] I hit a similar problem yesterday, but lost some details so I couldn't make a proper bug r...

...#39; In the messages file, I see: Mar 27 17:28:15 r5 kernel: journal_bmap: journal block not found at offset 1607 on sd(8,17) Mar 27 17:28:15 r5 kernel: Aborting journal on device sd(8,17). Mar 27 17:28:15 r5 kernel: ext3_abort called. Mar 27 17:28:15 r5 kernel: EXT3-fs abort (device sd(8,17)): ext3_journal_start: Detected aborted journal Mar 27 17:28:15 r5 kernel: Remounting filesystem read-only Mar 27 17:28:15 r5 kernel: EXT3-fs error (device sd(8,17)) in start_transaction: Journal has aborted If I reformat the drive as ext2, it behaves quite fine through the whole test. I'm no longer logging any...

...ed since 2.4.18. If my analysis is correct, I can largely avoid the problem by not running "sync" as much (I currently run it every 5 minutes which isn't needed any longer (it's a long story:-)) but that doesn't fix the bug. My guess is that ext3_sync_dquot doesn't need ext3_journal_start at all but that isn't a well-informed guess. Help appreciated. NeilBrown

...orted EXT3-fs error (device sdb1) in ext3_orphan_del: Journal has aborted EXT3-fs error (device sdb1) in ext3_truncate: Journal has aborted __journal_remove_journal_head: freeing b_committed_data __journal_remove_journal_head: freeing b_committed_data ext3_abort called. EXT3-fs abort (device sdb1): ext3_journal_start: Detected aborted journal Remounting filesystem read-only EXT3-fs error (device sdb1) in start_transaction: Journal has aborted

...12 SCSI subsystem driver Revision: 1.00 EXT3-fs error (device ide0(3,2)): ext3_readdir: bad entry in directory #191618: directory entry across blocks - offset=0, in ode=1601332598, rec_len=24932, name_len=116 Aborting journal on device ide0(3,2). ext3_abort called. EXT3-fs abort (device ide0(3,2)): ext3_journal_start: Detected aborted journal Remounting filesystem read-only Remounting filesystem read-only EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)) in start_transaction: Journal has aborted EXT3-fs error (device ide0(3,2)): ext3_readdir: bad entry i...

...on: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide0(3,9)) in ext3_reserve_inode_write: Journal has aborted kernel: EXT3-fs error (device ide0(3,9)) in ext3_dirty_inode: Journal has aborted kernel: ext3_abort called. kernel: EXT3-fs abort (device ide0(3,9)): ext3_journal_start: Detected aborted journal kernel: Remounting filesystem read-only kernel: EXT3-fs error (device ide0(3,9)) in start_transaction: Journal has aborted kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error } kernel: hda: read_intr: error=0x40 { UncorrectableError }, LBAsect=3...

...3_readdir: bad entry in directory #381585: directory entry across blocks - offset=0, inode=0, rec_len=4132, name_len=63 Feb 26 06:25:24 mercurio kernel: Aborting journal on device dm-2. Feb 26 06:25:24 mercurio kernel: ext3_abort called. Feb 26 06:25:24 mercurio kernel: EXT3-fs abort (device dm-2): ext3_journal_start: Detected aborted journal Feb 26 06:25:24 mercurio kernel: Remounting filesystem read-only [...] Feb 26 15:57:21 mercurio kernel: EXT3-fs error (device dm-2) in start_transaction: Journal has aborted Feb 26 15:57:21 mercurio kernel: EXT3-fs error (device dm-2) in ext3_delete_inode: Journal has abor...

Hi, we're working on a stackable versioning file system for 2.4.x. Versioning can easily create lots of files for a file that gets modified frequently, and our current design puts all versions of a file in the same directory as the main file. We are therefore evaluating how stable and efficient different combinations of file systems would be in this scenario. We've run our versionfs on

Hello, I looked through the archives a bit and could not find anything relevant, if you know otherwise please point me in the right direction. I have a ~3T ext3 filesystem on linux software raid that had been behaving corectly for sometime. Not to long ago it gave the following error after trying to mount it: mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many

...erver kernel: EXT3-fs error (device hdc1): ext3_get_inode_loc: unable to read inode block - inode=32915539, block=65830916 Jul 20 04:09:13 server kernel: Aborting journal on device hdc1. Jul 20 04:09:13 server kernel: ext3_abort called. Jul 20 04:09:13 server kernel: EXT3-fs abort (device hdc1): ext3_journal_start: Detected aborted journal Jul 20 04:09:13 server kernel: Remounting filesystem read-only Jul 20 04:10:13 server kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error }Jul 20 04:10:13 server kernel: hdc: dma_intr: error=0x40 { UncorrectableError }, LBAsect=526647391, high=31, low=655...

...add_entry: bad entry in directory #41 009295: rec_len is smaller than minimal - offset=0, inode=3265411686, rec_len=0, name_len=0 Aug 6 15:22:05 adams kernel: Aborting journal on device sda4. Aug 6 15:22:05 adams kernel: ext3_abort called. Aug 6 15:22:05 adams kernel: EXT3-fs abort (device md1): ext3_journal_start: Detected aborted journ al Aug 6 15:22:05 adams kernel: Remounting filesystem read-only Aug 6 15:22:05 adams kernel: Unable to handle kernel NULL pointer dereference at virtual address 00 000000 Aug 6 15:22:05 adams kernel: printing eip: Aug 6 15:22:05 adams kernel: c01b1e61 Aug 6 15:22:05 ad...

Hi - We have had 3 rather major occurances of ext3 filesystem corruption lately, i.e. so bad we couldn't event mount, and fsck didn't help. I am looking for pointers, that could help us investigate the root cause. In general... We are running RedHat WS 3 Update 6, 2.4.21-40.2.ELsmp or 2.4.21-37.ELsmp We have a small SAN system that looks like this