search for: ext3_creat

...)): 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 failure 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 ... Rebooting didn't help: the journal aborted immediately. I also had some trouble using rootfstype=ext2 because (detecting that...

...309281588, 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

Hi, Could someone point me to documentation or explain in detail, process of creating file.(space reservation, inode....) What is happen at low lavel? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://listman.redhat.com/archives/ext3-users/attachments/20060713/2c862514/attachment.htm>

.../100> Trace; c0150c9f <dqget+15f/1e0> Trace; c0151856 <dquot_initialize+a6/180> Trace; c015cf7b <ext3_new_inode+8cb/a10> Trace; c016bc77 <__jbd_kmalloc+27/80> Trace; c0165874 <start_this_handle+114/150> Trace; c016595c <journal_start+ac/d0> Trace; c0161951 <ext3_create+81/110> Trace; c014239a <vfs_create+10a/160> Trace; c014219d <lookup_hash+8d/c0> Trace; c014253c <open_namei+14c/630> Trace; c014a11c <dput+1c/150> Trace; c0129270 <file_read_actor+0/e0> Trace; c01366e6 <filp_open+36/60> Trace; c0136a34 <sys_open+34/c0>...

...xt3_add_entry(handle, dentry, inode); if (!err) { - d_instantiate(dentry, inode); - return 0; + err = ext3_mark_inode_dirty(handle, inode); + if (err == 0) { + d_instantiate(dentry, inode); + return 0; + } } ext3_dec_count(handle, inode); iput(inode); @@ -465,7 +468,6 @@ static int ext3_create (struct inode * d inode->i_fop = &ext3_file_operations; inode->i_mapping->a_ops = &ext3_aops; err = ext3_add_nondir(handle, dentry, inode); - ext3_mark_inode_dirty(handle, inode); } ext3_journal_stop(handle, dir); return err; @@ -490,7 +492,6 @@ static int ext3_mkn...

...opying files into a different ext3 filesystem (both on LVs), and running pvscan (i.e. invalidate_buffers) repeatedly. At one point, I got several free buffers reported in cleanup_transaction. After that (this is the first time it happened) my kernel compile deadlocked and the kernel is stuck on: ext3_create journal_start start_this_handle log_wait_for_space log_do_checkpoint cleanup_transaction* __wake_up* The last 2 (*) functions appear and disappear from the KDB "bt" output, so I assume they are being called, but never finishing the transaction. I've added more debugging to determine...

Hi Andreas, Stephen, We have a lot working now: 1. journal recovery and initialization stuff is working 2. transactions go to the disk 3. infrastructure is there to do transcactions 4. ext3_create is fully operational. The problems we have seen mostly have to do with differences in which buffer heads are being initialized. Things like b_transaction etc. were not cleaned up. There are more buffer head problems around, but we are debugging them quickly now. You can play with this, make a...

...nal 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_committed_data After shuting down of domUs, fsck failed to repair the filesystem and restore of files was necessary. No updates of XEN or the kernel were made the days before. It was no possible to reproduce the problem yet....

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