similar to: 0.0.7a for kernel 2.2.19 concerns

Could anyone help me out, i've got a situation here. :-) I already contacted RTLinux users with no success, I hope ext3 users can help! I have a 2.2.19 kernel patched with RTLinux 3.1, clean and working. I found and applied the ext3 for 2.2.19 kernel patch. Patch went fine (like in README). I was able to tune2fs -j /dev/hda1 (activate the journal). And it actually works. 1) I was not able

Hi, i am seeing something interesting since the upgrade to 2.2.19/0.0.7a - I am experimenting with the am930 wireless driver and i am crashing on module exit. Everytime i reboot afterwards the var fs on /dev/hda8 is inconsistent [...] Checking all file systems... Parallelizing fsck version 1.21-WIP (01-Jun-2001) /dev/hda7: recovering journal /dev/hda7: clean, 39160/320640 files, 354596/640702

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the

The latest errata kernel-2.2.19-6.2.7.src.rpm contains old patches linux-2.2.17-ext3.patch linux-2.2.17-kdb+ext3.patch Is there somewhere a 0.0.7a version of the above that will patch cleanly in the errata kernel (considering all the other patches that get applied before ext3)? I read about ftp://ftp.clusterfilesystem.com/pub/ext3 but when I do $ rpm -qpl

We have a machine that is trying its darndest to house a linux kernel cvs repository. The machine is a dual 733mhz p3 netfinity of some kind. 512M of mem. Filesystem 1k-blocks Used Available Use% Mounted on /dev/sda1 16484504 4015876 11631240 26% / /dev/sda2 31079 3199 26276 11% /boot /dev/sdb2 16516084 32828 15644264 1%

While ripping one of my cds on my laptop this happened: Message from syslogd@theirongiant at Thu Jul 5 09:52:16 2001 ... theirongiant kernel: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0" from the kern.log: Assertion failure in do_get_write_access() at transaction.c line 551: "handle->h_buffer_credits > 0"

SYSTEM: rh6x based system, 2.2.19-6.2.7 rh errata kernel + 0.0.7a patch, I rebuilt rpm for i686; celeron466, 64MB, PIIX4. root fs is on software raid1 ext2, 6 additional fs's on software raid1 ext2. There's a 3rd HD, not mirrored, which is mounted ext3. EXT3-fs: mounted filesystem with ordered data mode. I enabled journal with tune2fs -j with unmounted fs. The 3 HDs are tuned with

Hi all, ext3-0.0.7a is now out, at the usual places: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and propagating now from ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ This fixes one major bug in ext3 recovery for metadata-only journaling. Because recovery can also happen in e2fsck, users should also upgrade to at least e2fsprogs-1.21-WIP-0601 (also provided at the above ftp sites).

I get 2 rejects applying 2.2.19-ext3 to latest errata rh 2.2.19 kernel. 1) fs/buffer.c Should I put "J_ASSERT(buf->b_count > 0);" before or after " *(int *)0 = 0;"? ===== ext3 0.0.7a patch --- 934,946 ---- if (buf->b_count) { buf->b_count--; + if (!buf->b_count && + (buf->b_jlist != BJ_None && buf->b_jlist

Hello, Now that kernel 2.2.20 is out with security fixes, I'd be interested in using it with ext3. The latest patch for 2.2.19, 0.0.7a, applies with some offset (both with and without kdb), and even compiles (without kdb), but I scarcely know what I am doing so haven't tried it yet. Could people in the know enlighten me on that point? I guess there is little chance for another ext3

I've not been happy with the stories about the "stable" 2.4.x kernels. Everywhere I read people saying "not for production use". Would you recommend adding ext3 to 2.2.19 (ext3-0.0.7a) or moving to 2.4.1x and using ext3 there (ext3-0.9.12)? -- -IAN! Ian! D. Allen Ottawa, Ontario, Canada idallen@ncf.ca Home Page on the Ottawa FreeNet: http://www.ncf.ca/~aa610/

R version: 1.7.1 OS: Red Hat Linux 7.2 In this example, I would expect an error for the overly long variable name. This is always reproducable for me. > formula(paste("y~",paste(rep("x",50000),collapse=""))) Segmentation fault Sincerely, Jerome Asselin -- Jerome Asselin (Jérôme), Statistical Analyst British Columbia Centre for Excellence in HIV/AIDS St.

I am trying to fit a lognormal distribution on interval-censored data. Some of my intervals have a lower bound of zero. Unfortunately, it seems like survreg() cannot deal with lower bounds of zero, despite the fact that plnorm(0)==0 and pnorm(-Inf)==0 are well defined. Below is a short example to reproduce the problem. Does anyone know why survreg() must behave that way? Is there an alternate

Hi, Here is the situation, I've got a very old webmail system running on kernel version 2.2.10 (I know, upgrade :) and it runs with quotas as the above suggests with ext2. I upgrade the system to kernel revision 2.2.19 + Stephen Tweedie's patches at ext3-0.0.7a.tar.gz (off kernel.org) with the kdb and ext3 patch applied. Booting up the new kernel still on ext2 reveals that quotas still

Hi, I would like to recommend a minor modification in axis() which I believe can simplify the making of plots for publications. I am trying to define default values for par() in order to make labels bigger and lines thicker, so that the resulting plots look good when resized for publication purposes. I ran into the following problem... axis() does not use par() values as default for

hi, is this rpms differ from redhat's rawhide 2.4.5 kernel which seems to contain ext3. so my question that your rpm contain different ext3 than rh's rpm? or I can simple use rh's rawhide rpms? thanks. yours. ps. please reply to my private address to since I'm not on the list. thanks. > Hi, > > Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.

Hi, after my X froze i had a fs inconsistency after the journal replay [...] EXT3-fs: 03:06: 1 orphan inode deleted EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 64k freed INIT: version 2.78 booting Loading /etc/console-tools/default.kmap.gz Activating swap... Adding Swap: 264560k

R version: 1.7.1 OS: Red Hat Linux 7.2 When "covmat" is supplied in princomp(), the output value "center" is all NA's, even though the input matrix was indeed centered. I haven't read anything about this in the help file for princomp(). See code below for an example: pc2$center is all NA's. Jerome Asselin x <- rnorm(6) y <- rnorm(6) X <- cbind(x,y)

I am confused on how the log-likelihood is calculated in a parametric survival problem with frailty. I see a contradiction in the frailty() help file vs. the source code of frailty.gamma(), frailty.gaussian() and frailty.t(). The function frailty.gaussian() appears to calculate the penalty as the negative log-density of independent Gaussian variables, as one would expect: >

I would like to document my findings (with a potential FIX) regarding the issue of calculation of the degrees of freedom with nlme(). The program given at the bottom of this email generates and fit 20 data sets with a mixed-effects LINEAR model, but using the function nlme() instead of lme(). In each case, the correct number of degrees of freedom for the intercept parameter is 12. However, in