similar to: raid and ext3

In the Red Hat Linux spec file for the 2.2.19 kernel, there is a note not to enable ext3 and LFS at the same time. I'm wondering whether this is an old note, and that it is safe to use ext3 0.0.7a on a system with LFS enabled, or if there are still issues with it. I'm aware that 0.0.7a is a really old version, and 2.2 isn't the most modern kernel, but it is what I have to work with.

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/

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

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 all, I'm looking for some rudimentary insight on GotoIf() which seems to be failing on me in my dial plan. All I basically wish to do is block a particular caller. Sounds easy enough, but my ternary operator/plan currently is not properly being implemented. Can anyone spot where I'm being a momo? All extensions get forwarded to the following macro: [macro-forward] ; arg1 = phone

HI all, Is there a renumbering function in R? I would like to renumber the following id numbers *Input file * Id Father Mother 123 0 0 124 0 0 125 123 124 126 123 0 127 125 126 128 0 127 130 123 125 *Output* Id Father Mother 1 0 0 2 0 0 3 1 2 4 1 0 5 3 4 6 0 7 7 1 2 Any help is highly appreciated in Advance Val K [[alternative HTML version deleted]]

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

Hi, oops in iput - Kernel 2.2.19/i386 + ide-udma patches + ext3 patches (0.0.7a) Intel BX chipset, SCSI Disks Symbios chipset - The crashing process is the master process of "postfix" an MTA. Just before the crash all processes on that machine started to segfault in nameserver resolution (remote dns server) and after 2-3 minutes this oops happened. ksymoops 2.3.4 on i686 2.2.19.

Hello, I packaged the old ext3 patch for Debian, and now I would like to create a patch-package of the current version for kernel 2.4.9. I consider to include Theodore's ext2 and ext3 readdir speedup patches and modify the 0.9.9 patch as needed to apply it on kernel 2.4.9. Does anyone (except of me) use all this parts together and report them to be stable enough? Gruss/Regards, Eduard. --

Hello All, Yesterday, one of our customer's cluster(2 box) server goes down after a I/O error during the backup procedure. When we turn on the cluster again, the 600M database file have been lost, disapear. Now, I'm with one of the disks (the other was used to rebuild the database server) and need to know how can I recover any piece of data from the disk. After the crash we mount 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

Hello All, I have a production server that is running 2.2.20. This server *has* to be up 24X7 - what I'm wondering is: 1) Is ext3 on 2.2.20 rock stable? Or, would you recommend that I just stay with ext2? 2) I have looked far and wide for a the ext3 patch for 2.2.20 - where can I find it? 3) Were are the e2fsprogs that are appropriate to run with the 2.2.X kernel series? Thanks,

Andy, Lang, Thanks for the suggestion. I have spent more time with it today, and I do see some strange things in liveness update. I am not at the actual cause yet, but here is what I got so far: I have the following live ranges when I start scheduling a region: R2 = [0B,48r:0)[352r,416r:5)... R3 = [0B,48r:0)[368r,416r:5)... R4 = [0B,32r:0)[384r,416r:4)... R5 = [0B,32r:0)[400r,416r:4)...

Hi folks, I looked into some slow compiles and filed https://bugs.llvm.org/show_bug.cgi?id=38829. The gist of it is that we spend a lot of time iterating basic blocks to compute local dominance, i.e. given two instructions in the same BB, which comes first. LLVM already has a tool, OrderedBasicBlock, which attempts to address this problem by building a lazy mapping from Instruction* to position.

Hi: When should we use "unnumbered priorities"(n) in extensions.What is the different between these 2 forms of extensions.conf? and ,Are both true? extensions.conf: form1: [Conferencerooms] exten => 333,1,Answer exten => 333,n,meetme(8000|cim) exten => 333,n,playback(vm-goodbye) exten => 333,n,hangup form2: [Conferencerooms] exten => 333,1,Answer exten =>

On Tue, Jul 14, 2009 at 9:48 AM, Adam Rosi-Kessel<adam at rosi-kessel.org> wrote: > The only issue I'm noticing is ogginfo reports: > > Warning: sequence number gap in stream 1. Got page 14 when expecting > page 2. Indicates missing data. > Warning: discontinuity in stream (1) I'd guess this is flagging the data that was overwritten by the bad tagging code. Some

Hi Sergei, Andy, Sorry - I got distracted with some other work. I'm looking into this and PR13719 now. I'll let you know what I find out. Sergei - thanks very much for the investigation. That should help me pin this down. Cheers, Lang. On Tue, Aug 28, 2012 at 2:33 PM, Sergei Larin <slarin at codeaurora.org> wrote: > Andy, Lang, > > Thanks for the suggestion. >

>On Mon, Jun 15, 2009 at 5:49 PM, Gaster, >Benedict<Benedict.Gaster at amd.com> wrote: >> I would like to use the LLVM x86 code generator to emit Intel syntax that >> is >> compatible with Microsoft’s MASM 9.x. Taking the TOT LLVM, from last >> week, I >> have found a number of changes that are required to make this work, most >> of >> which

Hi Lang, Just one more quick question. in LiveIntervalAnalysis.cpp In SlotIndex findLastUseBefore(unsigned Reg, SlotIndex OldIdx) Did you really mean to use for (MachineRegisterInfo::use_nodbg_iterator UI = MRI.use_nodbg_begin(Reg), UE = MRI.use_nodbg_end(); UI != UE; UI.skipInstruction()) {} Aren't we currently dealing with units,