similar to: ext3 htree brelse problems look to be fixed!

Hi In ext3_get_parent(), quick string (struct qstr) can do the job, in place of declaring a dentry on stack. Following patch does this and saves few bytes on kernel stack. Thanks, Maneesh namei.c | 69 ++++++++++++++++++++++++++++++---------------------------------- 1 files changed, 33 insertions(+), 36 deletions(-) diff -urN linux-2.5.58-base/fs/ext3/namei.c

I post a patch for comment on ext2-devel for the NFS cookie bug. Did not get any feedback yet. As Ted suggested, it set the cookie to -1 on EOF, even though it is not seek able to there. I only test it with Stephen's "readdir.c". Not have chance to run it on a NFS server yet. Do you have more information about the cache trashing bug? Regards, Chris ===== dir.c 1.5 vs edited

hm, this backtrace actually has info... btw, I think we need this: --- 25/fs/ext3/namei.c~ext3-brelse-fix Sun Dec 29 06:53:39 2002 +++ 25-akpm/fs/ext3/namei.c Sun Dec 29 06:53:54 2002 @@ -576,8 +576,10 @@ int ext3_htree_fill_tree(struct file *di (hinfo.minor_hash < start_minor_hash))) continue; if ((err = ext3_htree_store_dirent(dir_file, - hinfo.hash,

VFS: brelse: Trying to free free buffer buffer layer error at fs/buffer.c:1182 Pass this trace through ksymoops for reporting Call Trace: [<c01468f0>] [<c0146aa9>] [<c0146b57>] [<c0146b84>] [<c0175a17>] [<c023cbfa>] [<c023d2f1>] [<c0175c90>] [<c01728e9>] [<c01ad7d6>] [<c014d215>] [<c0154c68>] [<c0154f79>]

I've backported all of the bugfixes to the 2.5 dxdir/htree patches to 2.4, and have created a new set of patches for Linux 2.4.21rc5. At this point it *looks* like we've fixed all of the htree bugs that people have reported, including the brelse bug, the memory leak bugs, and the NFS compatibility problems. I've done *very* light testing, and things seem to work, but I'm now

In ocfs2_find_entry_dx(), if ocfs2_read_inode_block() failed, both di_bh and dx_root_bh are both released. In this case, for dx_root_bh, it's unnecessary (even buggy if refcount of dx_root_bh is non-zero). This patch fixes this issue by change brelse order of di_bh and dx_root_bh. Signed-off-by: Coly Li <coly.li at suse.de> --- fs/ocfs2/dir.c | 5 +++-- 1 files changed, 3

I got this error in my log reports this morning, from the machine I use as my firewall. This is the first time it has occurred, but the machine is running a very new kernel: Linux fendrian.rimspace.net 2.6.0-test11-fendrian #1 Wed Dec 10 22:25:59 EST 2003 i486 GNU/Linux The kernel was up to date as per the CVS repository at that point. This was just before the CDROM_SEND_PACKET IOCTL fix went

Over the last two days we've been seeing a fair bit of this: ---- # ls -laR > /dev/null ... ls: ./server2/b/user/bxyz/392.: Input/output error ---- This is with the latest htree patches applied to 2.4.19, and latest e2fsprogs-test, on a dual AMD system, with 5x73GB SCSI drives on a MegaRAID controller. We're using the gcc 2.96 that comes with RH7.3. esfsck shows "Inodes that

With indexed dir enabled, now we use ocfs2_dir_lookup_result to wrap all the bh used for dir. So remove the 2 unused variables. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/namei.c | 4 ---- 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/fs/ocfs2/namei.c b/fs/ocfs2/namei.c index 2220f93..33464c6 100644 --- a/fs/ocfs2/namei.c +++ b/fs/ocfs2/namei.c @@

Linus, et al, Here are the outstanding ocfs2 fixes we have for 2.6.30. The important ones are journal credit fixes for the new indexed directories. There's also MAINTAINERS update for my ocfs2 git tree. Please pull. Joel The following changes since commit 612392307cb09e49051225092cbbd7049bd8db93: Ryusuke Konishi (1): nilfs2: support nanosecond timestamp are available in the

Hello, When drop_progress isn't zero, the root->node's usage count is increased in btrfs_search_slot. Therefore, the get_bh in the body of while loop is redundant in most cases. (this change is in accordance with btrfs_defrag_leaves). The second change is decrease root->node's usage count when drop a snapshot. Regards YZ diff -r 29b8cc7794ac extent-tree.c --- a/extent-tree.c

I decided that I would try out 2.5.44, and I noticed that htree was merged. If I don't do the tune2fs -O dir_index, and e2fsck -D, the (exisintg) fs won't use htree, right? Once I do the tune2fs and e2fsck, will I still be able to go back to a non-htree kernel if needed? (Will a htree-ized fs work on a non-htree kernel?) I'm guessing that it won't. I've seen a 2.4 htree

Apologies for the newbie question: I have a (stock) 2.4.20 build (*not* -ac), and I'm trying to work with large ext3 directories. By large, I mean 160,000 files per directory. (Yes, I know it would be better in nested directories but such is life). I feel htree would benefit me. Having upgraded from an earlier version of 2.4, I don't see any change, and close reading of the 2.4 changelog

Well here is what I got from testing htree with NFS. http://labs.zianet.com/benchmarks_html/postmark_benchmarks_NFS_100_htree.html It looks like htree improves performance when the storage device is local(as per my previous post) but it looks like htree degrades performance when used in conjunction with NFS. I am going to try it with gigabit ethernet when I get the time to see if maybe I am

Apologies for the newbie question: I have a (stock) 2.4.20 build (*not* -ac), and I'm trying to work with large ext3 directories. By large, I mean 160,000 files per directory. (Yes, I know it would be better in nested directories but such is life). I feel htree would benefit me. Close reading of the 2.4 changelog suggests that htree isn't in there - only a patch to prevent non-htree

Hello, Could someone create some newer htree patches for the 2.4.x kernel? There are some bug fixes in the 2.4.21-rc releases that would be nice to have but the htree patches preceed those and they won't apply cleanly to later pre/rc kernels. It sounds like Marcelo may be about ready to put out 2.4.21 so it may just be worth holding off until that happens, but I don't suspect much will

Guys, I have recently applied the latest 2.4 htree patch on a heavily loaded nfs server. The nfs server serves around four very busy clients that deliver email in maildir format and pop3/imap clients. Being maildir I presumed that the htree patch would improve performance - but I was wrong. Load on the server went up by around 25-40%. After 3-4 hours of heavy use the clients load went up to

Hi Guys, I am planning on upgrading an existing NFS exported filesystem to the ext3 htree patch on kernel v2.4.23. Will the patch index directories automatically after tune2fs -O dir_index or should I do an e2fsck -Dfy on the filesystem before remounting?

My reading of the kernel.src.rpm doesn't indicate that Severn has ext3 htree patches. Stephen, were there any issues seen during Cerberus testing ? Regards, Yusuf -- Yusuf Goolamabbas yusufg@outblaze.com

Hi, Someone knows if the htree patch is applied in the last kernel for RedHat 8 (kernel-2.4.20-18.8) for the ext2/ext3 filesystems ? Greetings. --- Carles Xavier Munyoz Baldó carles@unlimitedmail.org http://www.unlimitedmail.net/ ---