similar to: FS-corruption on ext3 with HTrees

Hi, we're working on a stackable versioning file system for 2.4.x. Versioning can easily create lots of files for a file that gets modified frequently, and our current design puts all versions of a file in the same directory as the main file. We are therefore evaluating how stable and efficient different combinations of file systems would be in this scenario. We've run our versionfs on

I'm NOT the authority here, but AFAIK, Htree is presently available only as a patch for 2.4 kernels (which includes RH8). I think that Htree was still beta code at the time RH8 was frozen (and may still be, from RedHat's perspective). I do not have the impression that the Htree patch has been applied in any standard RedHat kernels or kernel updates. I hope I am wrong, and that

Didn't hear back from anyone regarding if there is a way to determine if I am running the ext3fs with htree. Is there a way I can do it without checking the src code since I am running the precompired redhat kernel with 8.0? Perhaps an entry under /proc somewhere? Pj -----Original Message----- From: Parker Johnson Sent: Tuesday, January 14, 2003 3:34 PM To: 'Andreas Dilger';

Andreas was kind enough to point out that not neccesarily all ext3fs have htrees ready to go. I am running redhat8.0 out of the box. How can I check if ext3fs with htrees is running? I can download the kernel source, but I don't know what options were used when it was built by redhat. Thanks much for all of your help. -Parker -----Original Message----- From: Andreas Dilger

Ape is an R package for "analyses of phylogenetics and evolution". The first version (0.1) has been released on 27 August 2002 and is available on CRAN. >From the 'Description' file of version 0.1: Ape provides functions for reading, and plotting phylogenetic trees in parenthetic format (standard Newick format), analyses of comparative data in a

At 11:57 25/10/00 +0100, Brian Ripley wrote: >> Date: mer., 25 oct. 2000 12:38:55 +0200 >> From: Emmanuel Paradis <paradis@isem.univ-montp2.fr> > >> I think it would be nice to have par(ask=T) set by default in termplot(), >> like it is in plot.lm(). > >Well, it isn't really the default in plot.lm, the default for `ask' being > >interactive()

There seems to be a bug with var() when the argument is a vector with exactly three values of 1e30 (or close to this value). This does not happen with twice, four (or more) times this value, or another value. > var(rep(1e30, 3)) [1] 2.971056e+28 > var(rep(1.2e30, 3)) [1] 2.971056e+28 > var(rep(0.9e30, 3)) [1] 2.971056e+28 > var(rep(0.8e30, 3)) [1] 0 > var(rep(1e29, 3)) [1] 0 >

C?dric Finet wrote: > > I thank you for your answer but I do not understand yet why the Fisher?s exact > test does not work. And why is a "negative key". > > C?dric Finet > Running the original TOMS643 fortran code (R uses an f2c translation of this) says: FEXACT ERROR: 30 Stack length exceeded in f3xact. This problem should not occur. The integer hash key is

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

Dear list members, If I install with R-devel r74500 on Windows (sessionInfo below) the attached 'bugdemo' package with the single function foo <- function() { ? named <- c("bar"=TRUE) ? print(named) ? return(named) } then run > bugdemo::foo() [1] TRUE [1] TRUE The "bar" name is lost. It is not lost when I define foo in the R session instead of using

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

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

Hi Guys, I am quite keen to try out the new htree extensions to ext3 however I wish to use them under NFS. I have noticed comments from the developers saying that it doesn't work properly under NFS. What exactly is the current status of the issue?