similar to: Often seeing i_blocks too large after recovery(ies)

Hi all, I'm running ext3 with Linux 2.4.19pre5aa2 (and thus ext3 0.9.17) and e2fsprogs 1.27 on an x86 laptop with an IDE disk (with DMA enabled). The partition in question was mounted with the data=journal and nosuid options set. All the partitions are set to be fscked on bootup every 30 days (although I don't think this is strictely necessary, better safe than sorry). ext3 has been

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?

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

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

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 warrant an upgrade for production machines. Its effects are: 1) errors are

I appear to have a broken filesystem on this box to the point where I am probably going to rebuild the system since I have lost trust in it.... I was wondering if there was any reasonable postmortum work I could do on it before it gets rebuilt. History is that the laptop has a much mauled partition set on it - initially it came with 100% win2k, I then shrunk that and added linux (a RH71 install

/an ocfs2 bug: a truncate races with ocfs2_get_block(...,0). 1) 'dd' is doing a truncate, clearing the page cache and reset inode size./ /2) between clearing page cache and resizing inode, a read comes and create a / /new page and insert it to page cache./ /3) the read(from `cat`) set buffer head in the new page as mapped but doesn't increase / /ip_mmu_private in ocfs2_get_block()

I'd like to try 2.4.11pre2, but I need ext3; and the 0.9.10 patch that works on 2.4.10 has two non-trivial rejections in fs/buffer.c. Has anyone successfully integrated ext3 with 2.4.11pre2? -- Chip Salzenberg - a.k.a. - <chip@pobox.com> "We have no fuel on board, plus or minus 8 kilograms." -- NEAR tech

This is a maintenance release of NeoMagic DDX for X.Org X Server. No testing has been done due to the lack of equipment availability. Please note that the code may not compile against X Server 1.20 since it no longer supports 24-bit color. [1] The DDX compiles cleanly without compilation warnings on X Server 1.19.6. Kevin Brace Brace Computer Laboratory blog https://bracecomputerlab.com [1]

Adam Jackson (1): Use own thunk functions instead of vgaHW*Weak Dave Airlie (1): neomagic: fix build against master X server. Julien Cristau (2): Fix compiler warning with recent X servers Bump to 1.2.9 git tag: xf86-video-neomagic-1.2.9 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-neomagic-1.2.9.tar.bz2 MD5: 4b5b52e9da0a954cd3d6068a33975bc1

Adam Jackson (2): Death to RCS tags. neomagic 1.2.0 Alan Coopersmith (2): Replace references to XFree86/XF86Config in man page renamed: .cvsignore -> .gitignore Brice Goglin (1): Define NEO_*_VERSION using PACKAGE_VERSION_* Dave Airlie (3): neomagic: port to libpciaccess neo: finish pciaccess conversion finish pciaccess conversion Matthieu

Adam Jackson (2): fbpseudocolor no longer exists, don't try to use it. neomagic 1.2.1 Paulo Cesar Pereira de Andrade (2): Compile warning fix. Don't include fbpseudocolor.h, as it is no longer available. git tag: xf86-video-neomagic-1.2.1 http://xorg.freedesktop.org/archive/individual/driver/xf86-video-neomagic-1.2.1.tar.bz2 MD5: a72f57fca4f4dff9a2c82eb1fe7456f4

Hi, (I'm not subscribed to ext3-users, please CC: me) Kernel: 2.4.18. I've just converted a 100(ish) MiB ext2 filesystem to ext3 (umount, tune2fs -j, e2fsck, mount) and it seems to be happy, except... 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

I have a 1.5 TB (1,475,720,773,632) partition that I wanted to convert from ext4 to btrfs. It is currently used as / for ubuntu 10.10. I booted into 11.04 beta2 and tried a ''btrfs-convert /dev/sdc1'', but after about 20 minutes it segfaulted. I performed a: sck.ext4 -cDfty -C 0 /dev/sdc1 After everything was clean, I downloaded the debugging symbols for btrfs-convert and

I did not write that. On Jan 29, 2008 9:05 AM, S Ellison <S.Ellison at lgc.co.uk> wrote: > >>> "Gabor Grothendieck" <ggrothendieck at gmail.com> 29/01/2008 12:35:27 > >>> > > As is common in human affairs, even > > the illusion of understanding is preferred to a lofty digression > upon > > why the audience does not understand.

Al writes: > On Thu, 22 Mar 2001, Andreas Dilger wrote: > > If this is the case, then all of the other zero initializations can be > > removed as well. I figured that if most of the fields were being > > zeroed, then ones _not_ being zeroed would lead to this problem. > > Other zero initializations in inode->u certainly can be > removed, but whether it's

I'm constructing a raid 5 of 3 160gb sata drives. They're connected to a promise sx4 150 card, using the kernel drives (not promise's binary only drivers). the raid builds fine, as does creation of the ext3 filesystem. however, if i then run e2fsck (with the -f option since the filesystem is brand new) i get thousands of these type of errors: Inode 15461 has imagic flag set.

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,

use i_size_read() instead of accessing inode->i_size directly. Signed-off-by: Wengang Wang <wen.gang.wang at oracle.com> -- diff --git a/fs/ocfs2/aops.c b/fs/ocfs2/aops.c index b2c52b3..4491851 100644 --- a/fs/ocfs2/aops.c +++ b/fs/ocfs2/aops.c @@ -1920,7 +1920,7 @@ int ocfs2_write_end_nolock(struct address_space *mapping, out_write_size: pos += copied; - if (pos >

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: