search for: i_block

...As a test, I then filled the filesystem up, lastly copying /usr/bin (as root, so the filesystem became brim full). I then umounted it, and ran e2fsck -n -f /dev/hda6, and got the following: e2fsck 1.23, 15-Aug-2001 for EXT2 FS 0.5b, 95/08/09 Pass 1: Checking inodes, blocks, and sizes Inode 4113, i_blocks is 142, should be 64. Fix? no Inode 5902, i_blocks is 2, should be 0. Fix? no Inode 5903, i_blocks is 2, should be 0. Fix? no Inode 5904, i_blocks is 2, should be 0. Fix? no Inode 5905, i_blocks is 2, should be 0. Fix? no Inode 5906, i_blocks is 2, should be 0. Fix? no Inode 5907, i_blocks i...

Hello I found that after defrag a file, the corresponding inode's i_blocks become incorrect. I hope following description address the real reason. i_blocks is decreased in 'btrfs_drop_extents' when something are drop/truncated and 'run_delalloc_range' calls 'btrfs_drop_extents' at first place, so 'run_delalloc_range' may decrease the i_b...

Fix "h_buffer_credits<0" assert failure during truncate. The bug occurs when the "i_blocks" count in the file's inode overflows past 2^31. That works fine most of the time, because i_blocks is an unsigned long, and should go up to 2^32; but there's a place in truncate where ext3 calculates the size of the next transaction chunk for the delete, and that mistakenly uses a si...

I have many systems running current ext3 code. Some of them have hardware problems that lead to frequent reboots, and the journal recovery has worked excellently. However, on the periodic forced fsck on supposedly recovered and clean filesystems, I've many times seen fsck report that i_blocks is too large in one or more inodes. I suspect that i_blocks is somehow escaping proper restoration during the log replay. This is obviously not a critical problem, but it seems to have persisted through several minor ext3 revisions, so I thought it would be a good idea to mention it here. PS: T...

...stem (AFAIK, the partition in question unmounted cleanly, although I wasn't paying attention to it particularly); when linux started to load again, it chose to do a periodic fsck of all the partitions. Everything was clean except for /dev/hda5, which had many fsck warnings like so: Inode 8387: i_blocks is 2, should be 0. FIXED (sorry, don't have the exact text, but that was the gist of it) Those errors occurred for a lot of inodes (70+), a lot of them numbered sequentially (8387->8393, 14424->1453, etc). For most of these inodes, i_blocks was 2 and should have been 0 -- other variati...

I tried it on loop. 1. mount /dev/loop0 /mnt/test -t ext3 2. cp files to 100% full 3. umount /mnt/test 4. fsck.ext3 -f /dev/loop0 Inode xxxxx, i_blocks is xxx, should be yyy. Fix?

This fixes the "i_blocks went wrong when the disk filled up" problem. In ext3_new_block() we increment i_blocks early, so the quota operation can be performed outside lock_super(). But if the block allocation ends up failing, we forget to undo the allocation. This is not a serious bug, and probably does not warra...

...(had done some successful backups). The error message was ANS1028S Internal program error. Please see your service representative. which helps little :-) I decided to force a fsck, so did touch /forcefsck and rebooted The fsck threw up many thousands of errors, all of the form INODE nnnn i_blocks is 32, should be 16 with the i_blocks & should-be values various multiples of 8. I suspect that parted has screwed up, and so ext3 has been running on a losing wicket ever since... however even after the fsck (which obviously won't be able to fix everything if parted has broken things),...

...vate) is not / /increased in last prepare write./ BUG is described in s://bug.oraclecorp.com/pls/bug/webbug_print.show?c_rptno=7183894. solution: /1) moves the clearing of page cache truncate_inode_pages() from ocfs2_truncate_file() to/ /ocfs2_set_inode_size() after resizing inode size and i_blocks./ /2) in ocfs2_get_block(), add checks on iblock >= inode->i_blocks. if true, return -EIO. 3) //a kernel bug fix is needed for 2.6.9 kernel. //see https://bugzilla.redhat.com/show_bug.cgi?id=453359/ aops.c | 6 ++++++ file.c | 4 ++-- 2 files changed, 8 insertions(+), 2 deletions(-)...

...= IFTODT(e_inode->i_mode); inode->size = e_inode->i_size; @@ -156,6 +156,7 @@ static void fill_inode(struct inode *inode, const struct ext2_inode *e_inode) inode->flags = e_inode->i_flags; inode->file_acl = e_inode->i_file_acl; memcpy(PVT(inode)->i_block, e_inode->i_block, sizeof PVT(inode)->i_block); + PVT(inode)->i_ino = inr; } static struct inode *ext2_iget_by_inr(struct fs_info *fs, uint32_t inr) @@ -169,11 +170,32 @@ static struct inode *ext2_iget_by_inr(struct fs_info *fs, uint32_t inr) if (!(inode = alloc_inode(fs, inr...

...c.c linux-2.4.3p6-aed/fs/ext2/ialloc.c --- linux-2.4.3p6/fs/ext2/ialloc.c Fri Dec 8 18:35:54 2000 +++ linux-2.4.3p6-aed/fs/ext2/ialloc.c Fri Mar 23 00:47:46 2001 @@ -432,16 +416,13 @@ inode->i_blksize = PAGE_SIZE; /* This is the optimal IO size (for stat), not the fs block size */ inode->i_blocks = 0; inode->i_mtime = inode->i_atime = inode->i_ctime = CURRENT_TIME; + /* The inode->u struct is zeroed for us by new_inode() */ inode->u.ext2_i.i_new_inode = 1; inode->u.ext2_i.i_flags = dir->u.ext2_i.i_flags; if (S_ISLNK(mode)) inode->u.ext2_i.i_flags &= ~...

...e optimized out> ext2_scan = 0xce2300 ext2_ino = 37359452 objectid = 37359706 ext2_inode = {i_mode = 16877, i_uid = 1000, i_size = 16384, i_atime = 1303466526, i_ctime = 1296464377, i_mtime = 1296464377, i_dtime = 0, i_gid = 1000, i_links_count = 2, i_blocks = 32, i_flags = 528384, osd1 = {linux1 = {l_i_version = 1981}, hurd1 = {h_i_translator = 1981}}, i_block = {193290, 4, 0, 0, 1, 149430439, 1, 3, 149430464, 0, 0, 0, 0, 0, 0}, i_generation = 2854948622, i_file_acl = 0, i_dir_acl = 0, i_faddr = 0, osd2 = {linux2 = { l_i_b...

...in use, but has dtime set. Fix<y>? no Inode 15468 is in use, but has dtime set. Fix<y>? no Inode 15331 has compression flag set on filesystem without compression support. Clear<y>? no Inode 15331, i_size is 15275251971216207939, should be 0. Fix<y>? no Inode 15331, i_blocks is 154520075, should be 0. Fix<y>? no Inode 15333, i_size is 5330692746792616550, should be 0. Fix<y>? no Inode 15333, i_blocks is 3419793554, should be 0. Fix<y>? no Inode 15330 has INDEX_FL flag set but is not a directory. Clear HTree index<y>? no it appears to be...

The only non-fix here is Joel's new configfs convenience macros, but nobody is using them yet, so I think the patch is safe. By the way, these patches (as usual) are all rebased on top of your latest tree. I think that since the vast majority of ocfs2 and configfs patches are self-contained and within a small area of the kernel that this should probably be fine. If you feel otherwise however,

...ile size (%lld) is too small!\n", - inode->i_size); + i_size_read(inode)); status = -EINVAL; goto done; } - mlog(0, "inode->i_size = %lld\n", inode->i_size); + mlog(0, "inode->i_size = %lld\n", i_size_read(inode)); mlog(0, "inode->i_blocks = %llu\n", (unsigned long long)inode->i_blocks); mlog(0, "inode->ip_clusters = %u\n", OCFS2_I(inode)->ip_clusters); @@ -1120,7 +1120,7 @@ static int ocfs2_force_read_journal(struct inode *inode) memset(bhs, 0, sizeof(struct buffer_head *) * CONCURRENT_JOURNAL_FILL...

...t2_fs, ext2_inode)) { - btrfs_set_stack_inode_size(btrfs_inode, inode_size + 1); - ret = create_file_extents(trans, root, objectid, btrfs_inode, - ext2_fs, ext2_ino, 1, 1); - btrfs_set_stack_inode_size(btrfs_inode, inode_size); - return ret; - } - - pathname = (char *)&(ext2_inode->i_block[0]); - BUG_ON(pathname[inode_size] != 0); - ret = btrfs_insert_inline_extent(trans, root, objectid, 0, - pathname, inode_size + 1); - btrfs_set_stack_inode_nbytes(btrfs_inode, inode_size + 1); - return ret; -} - -/* - * Following xattr/acl related codes are based on codes in - * fs/ext3/xattr....

While I untar a large archive on xfs , ext3 (ver 1.3 and ver 1.4) file systems , on ppc processor and kernel ver 2.6.21 , I get an error. Also sometimes, on ext3 (1.3 and 1.4) the file system goes read-only while untarring. The same tar file when untarred on a i386 machine works properly. ERROR: -------------- tar: Skipping to next header gzip: stdin: invalid compressed data--crc error tar:

...al block #19 (1701978685) in inode 991327. CLEARED. Illegal block #20 (1852994932) in inode 991327. CLEARED. Illegal block #21 (1936683040) in inode 991327. CLEARED. Illegal block #22 (1752457076) in inode 991327. CLEARED. Too many illegal blocks in inode 991327. Clear inode? yes Inode 991248, i_blocks is 21744, should be 21760. Fix? yes Inode 991247, i_size is 4946696, should be 5099520. Fix? yes Inode 991247, i_blocks is 9688, should be 9984. Fix? yes Inode 991246, i_size is 3581284, should be 3719168. Fix? yes Inode 991246, i_blocks is 7008, should be 7272. Fix? yes Inode 991252 has...

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and

...rs, check forced. Pass 1: Checking inodes, blocks, and sizes Inode 3905 has illegal block(s). Clear<y>? yes Illegal block #2 (31285248) in inode 3905. CLEARED. Illegal block #4 (164077568) in inode 3905. CLEARED. Inode 3905, i_size is 2914, should be 24576. Fix<y>? yes Inode 3905, i_blocks is 8, should be 24. Fix<y>? yes Inode 18145 has illegal block(s). Clear<y>? yes Illegal block #2 (134492160) in inode 18145. CLEARED. Illegal block #4 (74215424) in inode 18145. CLEARED. Inode 18145, i_size is 2290, should be 24576. Fix<y>? yes Inode 18145, i_blocks is 8,...