search for: ext3_new_inode

...l. When one of the linux.org.uk machines got rebooted, it performed a full fs check of the main 160GB ext3 partition claiming it contained errors. During the check it found: Deleted inode 142279 has zero dtime. FIXED. The kernel message log contained lots of: EXT3-fs error (device md(9,1)) in ext3_new_inode: error 28 We had used up all the available inodes. Since the above message is generated from __ext3_std_error, it marks the filesystem bad. This doesn't sound like proper behaviour. Kernel: Red Hat 2.4.9-21 -- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux...

Hello, i posted a question about a possible ext3fs bug a few month ago. I see this kernel-msg in the messages: Oct 8 18:30:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 Oct 8 18:35:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 Oct 8 18:40:00 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 they repead periodicaly, because a logging file is now corrupted due to this bug. I have done successfull an e...

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

Hello, Over the last month or so, I've noticed the following error showing up repeatedly in my system logs under kernel 2.4.18-ac3 and more recently under 2.4.19-rc1: EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28 I've now been able to capture the following Oops before the system went down entirely: Assertion failure in do_get_write_access() at transaction.c:611: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" kernel BUG at transaction.c:611! invalid operand: 0000 C...

...:33 viper kernel: end_request: I/O error, dev 21:01 (hde), sector 96469000 Feb 25 21:26:33 viper kernel: EXT3-fs error (device ide2(33,1)): read_inode_bitmap: Cannot read inode bitmap - block_group = 368, inode_bitmap = 12058625 Feb 25 21:26:33 viper kernel: EXT3-fs error (device ide2(33,1)) in ext3_new_inode: IO failure Feb 25 21:26:52 viper kernel: hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 25 21:26:52 viper kernel: hde: dma_intr: error=0x40 { UncorrectableError }, LBAsect=128974919, sector=128974856 Feb 25 21:26:52 viper kernel: end_request: I/O error, dev 21:01 (hde), sector...

hello: I have been reviewin my message slog and have found the following message: Dec 19 06:27:28 server02 kernel: EXT3-fs error (device sd(8,7)) in ext3_new_inode: error 28 What is error 28 and should I be worried about it? Ray Turcotte

...75, sector=10223712 end_request: I/O error, dev 03:41 (hdb), sector 10223712 EXT3-fs error (device ide0(3,65)): ext3_get_inode_loc: unable to read inode block - inode=636706, block=1277964 EXT3-fs error (device ide0(3,65)) in ext3_reserve_inode_write: IO failure EXT3-fs error (device ide0(3,65)) in ext3_new_inode: IO failure hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=36264, sector=36200 hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=3421247, sector=3421184 hdb: dma_...

...l 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail. ----------------------------------------------------------------------------- kernel says: Jul 24 11:34:13 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 ----------------------------------------------------------------------------- fsck says: e2fsck 1.25 (20-Sep-2001) Warning! /dev/sda8 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Inodes that were pa...

...> Trace; c0128f69 <do_generic_file_read+349/460> Trace; c01293cc <generic_file_read+7c/130> Trace; c0129270 <file_read_actor+0/e0> Trace; c01506f1 <read_dquot+91/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 <o...

...it b_state:0x92 b_list:BUF_DIRTY b_jlist:BJ_None on_lru:1 cpu:0 on_hash:1 b_count:2 b_blocknr:1 b_jbd:1 b_frozen_data:00000000 b_committed_data:00000000 b_transaction:0 b_next_transaction:0 b_cp_transaction:1 b_trans_is_running:0 b_trans_is_comitting:0 b_jcount:0 <0> ext3_new_inode() [ialloc.c:465] get_write_access b_state:0x92 b_list:BUF_DIRTY b_jlist:BJ_None on_lru:1 cpu:0 on_hash:1 b_count:2 b_blocknr:1 b_jbd:1 b_frozen_data:00000000 b_committed_data:00000000 b_transaction:0 b_next_transaction:0 b_cp_transaction:1 b_trans_is_running:0 b_trans_is_co...

...there replied with nearly the same error message as I am getting. Anyway, anywhere from once every few hours to 4 days, it will print errors like these on tty1: EXT3-fs error (device sd(8,4)) in ext3_reserve_inode_write: IO Failure I/O error: dev 08:04, sector 0 EXT3-fs error (device sd(8,4)) in ext3_new_inode: IO failure I/O error: dev 08:04 secotor 0 I/O error: dev 08:04 secotor 1050528 EXT3-fs error (device sd(8,4)): ext3_get_inode_loc: unable to read inode block - inode=73040, block=131316 I/O dev 08:04 sector 0 EXT3-fs error (device sd(8,4)) in ext3_reserve_inode_write: IO Failure I am running a h...

I am sorry if you receive it twice. since the mail-list said that i can't send mail to it unless i become one its member. hi, My system will crash when the disk(ext3) is full while i continue to launch 50 proceses to operate files(such as create, rm, mv, ...). Does ext3 have such a capability to stop journaling the changes when it finds there is no space left? or which source file of ext3

...he big difference between ext3/2.2.19 and ext3/2.4.14. Sometimes the latter performs 3 or 4 times faster. Someone has similar results or is there something wrong in my test ? Attached is the benchmark. By the way, during the test, I got the message kernel: EXT3-fs error (device ide0(3,10)) in ext3_new_inode: error 28 I guess this is because I ran out of inode ? But the kernel should not complain about it, the usual message is "no space left on the device" (that I also got during the test). Liu

...tal data loss on both domUs. I have never suffered under this failure before and I guess it is related to XEN. Both domUs 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...

...and therefore wont be dumped. I googled for a while for other users experience with this feature, but it seems to me the nodump flag is not used much or the people feel ok or are unaware. For myself and for now, I solved this problem with the following oneline patch against kernel 2.6.8, ialloc.c/ext3_new_inode(): --- kernel-source-2.6.8-orig/fs/ext3/ialloc.c 2004-08-14 07:36:58.000000000 +0200 +++ kernel-source-2.6.8/fs/ext3/ialloc.c 2005-07-19 11:20:36.000000000 +0200 @@ -566,9 +566,9 @@ ei->i_next_alloc_goal = 0; ei->i_dir_start_lookup = 0; ei->i_disksize = 0;...

...l 2.4.18 with the acl-patches from acl.bestbits.at and the patches for the fileutils and e2fsprogs. If you need more informations please mail. ----------------------------------------------------------------------------- kernel says: Jul 24 11:34:13 o5s kernel: EXT3-fs error (device sd(8,10)) in ext3_new_inode: error 28 ----------------------------------------------------------------------------- fsck says: e2fsck 1.25 (20-Sep-2001) Warning! /dev/sda8 is mounted. Warning: skipping journal recovery because doing a read-only filesystem check. Pass 1: Checking inodes, blocks, and sizes Inodes that were pa...

...ror (device sd(8,51)) in ext3_reserve_inode_write: IO failure Dec 24 13:48:36 10.17.0.2 kernel: SCSI disk error : host 3 channel 0 id 0 lun 1 return code = 10000 Dec 24 13:48:36 10.17.0.2 kernel: I/O error: dev 08:33, sector 0 Dec 24 13:48:36 10.17.0.2 kernel: EXT3-fs error (device sd(8,51)) in ext3_new_inode: IO failure Dec 24 13:48:37 10.17.0.2 kernel: SCSI disk error : host 3 channel 0 id 0 lun 1 return code = 10000 Dec 24 13:48:37 10.17.0.2 kernel: I/O error: dev 08:33, sector 0 Dec 24 13:48:37 10.17.0.2 kernel: EXT3-fs error (device sd(8,51)) in ext3_setattr: IO failure Dec 24 13:48:38 10.17.0...

...0 00 83 c4 14 90 b8 0d 00 00 00 0f b3 45 18 >>EIP; c0146885 <ext3_new_block+635/738> <===== Trace; c01f2fff <cprt+2a1f/a240> Trace; c01f3220 <cprt+2c40/a240> Trace; c0149314 <ext3_alloc_block+30/38> Trace; c0149636 <inode_getblk+d2/20c> Trace; c0148bbf <ext3_new_inode+6ef/7ac> Trace; c0149b27 <ext3_getblk+c7/244> Trace; c0149ccc <ext3_bread+28/118> Trace; c014bb4b <ext3_mkdir+117/634> Trace; c012ee8f <lookup_dentry+15f/1e8> Trace; c012f57d <sys_mkdir+e1/11c> Trace; c010a06c <system_call+34/38> Trace; c010002b <startup_32...

Hi I have mailed about this previously, but back then it was not really confirmed, so I have let it be at that. Anyhow, problem is that for some reason 2.5/2.6 ext3 with HTREE support do not like what perl-5.8.0 does during installation. It *seems* like one of the temporary files created during manpage installation do not get unlinked properly, or gets into the hash (this possible?) and cause