similar to: 1000''s of classes and filters

> The former co-author contributed, so he is still author and probably copyright > holder and has to be listed among the authors, otherwise it would be a CRAN > policy violation ... It's a bit of a philosophical question right now, but at some point in a developing package's life - particularly one that starts small but is subsequently refactored in growth - there may be no code

Hello all, Been a while since I've strolled this way. Apologies in advance if this is a common line of questioning. I've just bought a new Intel 865G based board with a P4 Hyperthreading processor. I believe I've gotten SMP set up correctly: in the menuconfig I specified SMP and told acpi to enumerate processors. Did I leave out anything? Anyway, the dmesg looks good and the

I tried to install and boot a 2.6.7 Dom0 xenLinux Kernel on an SMP (Dual-Xeon) Machine with 2 3-ware Controllers installed (1 4-channel Controler and 1 8-channel Controler, both Parallel ATA) and no other HDs present (except the ones connected to the 3ware controlers, of course). First of all I got a compilation error after activating the SMP option in the kernel config. After deactivating the

Hello! After upgrade to version 2.0, now using 2.0.1, I'm experiencing problems with glusterfs stability. I'm running 2 node setup with cliet side afr, and glusterfsd also is running on same servers. Time to time glusterfs just hangs, i can reproduce this running iozone benchmarking tool. I'm using patched Fuse, but same result is with unpatched.

The following 6 patches cleanup the jbd code and kill about 200 lines. First of 4 patches can apply to 2.6.13-git8 and 2.6.13-mm2. The rest of them can apply to 2.6.13-mm2. fs/jbd/checkpoint.c | 179 +++++++++++-------------------------------- fs/jbd/commit.c | 101 ++++++++++-------------- fs/jbd/journal.c | 11 +- fs/jbd/revoke.c | 158

Hi Ext3! I'm running about 30 dedicated MySQL machines under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had

Hi, A couple of our important servers, both running FC4 but one i386 and one x86_64, have been crashing recently. They both are running ext3 data=journal with large external journals and high commit intervals. Both machines use the gdth driver for their hardware RAID sets, if that's of any use. I think the hardware is good in both cases. I hope someone finds this data useful enough to be

Hi all, One of our mx servers started misbehaving today (postfix would timeout internally, load rising) and after I tried to reboot it, I got this: Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:613: "transaction->t_forget == NULL" ------------[ cut here ]------------ kernel BUG at fs/jbd/checkpoint.c:613! invalid operand: 0000 [#1] PREEMPT SMP Modules

Hello all, Last night a server of mine went belly up with my remote log server telling me this log entry: kernel: Assertion failure in __journal_drop_transaction() at fs/jbd/checkpoint.c:615: "transaction->t_forget == NULL" During this time, we had high email loads and I have my 2 /var/spool/postfix_1 and /var/spool/postfix_2 partitions mounted with "data=journal" option.

I have a multi-port PCI-X card that is causing me some grief. An older version of the system bios allowed this to work correctly, and the on-board devices to work correctly. the newer system bios has fixed a 'bug' where the interrupts were routed incorrectly according to the PCI bridge specification. The system vendor indicates that I am likely missing the support for multiple IOxAPIC,

It appears that this bug in data=journal mode, https://listman.redhat.com/archives/ext3-users/2005-February/msg00045.html isn't fixed in 2.6.11.11. Andrew, I've CC'd you since you have previously looked at this specific issue. I'm seeing this problem on dual-Opteron x86-64 boxes serving NFS + Samba3 to a few dozen clients; it takes several hours at high load to reproduce. We

While writing a file to an ext3 filesystem, i get some drive errors on the console. I guess is a drive/ide related problem more that a ext3 one, but anyway the debug output is here if you want to take a look. And, by the way, what means that DRQ thing?? Oct 7 20:31:36 fargo kernel: (journal.c, 218): kjournald: kjournald wakes Oct 7 20:31:36 fargo kernel: (journal.c, 202): kjournald: