similar to: ext3 0.9.12 for 2.4.10-ac11

Displaying 20 results from an estimated 900 matches similar to: "ext3 0.9.12 for 2.4.10-ac11"

2001 Sep 24
1
ext3-2.4-0.9.10
An ext3 patch against linux 2.4.10 is at http://www.uow.edu.au/~andrewm/linux/ext3/ This patch is *lightly tested* - ie, it boots and does stuff. The changes to ext3 are small, but the kernel which it patches has recently changed a lot. If you're cautious, please wait a couple of days. The patch retains the buffer-tracing code. This will soon be broken out into a separate patch to make
2001 Oct 11
4
ext3 on 2.4.10-ac11 w/ext3-2.4-0.9.12-2410ac11
I am trying to compile 2.4.10-ac11 w/ the ext3-2.4-0.9.12-2410ac11 patch. I'm getting unresolved symbols w/ ext3 module: cd /lib/modules/2.4.10-ac11; \ mkdir -p pcmcia; \ find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.10-ac11; fi depmod: *** Unresolved symbols in
2003 Sep 22
3
journal buffer_credits problem
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
2002 Sep 22
2
Assertion failure in ext3_get_block() at inode.c:853: "handle != 0"
Hi, Got the following on Linux 2.5.37 trying to run apt-get update. MikaL Sep 21 23:10:05 devil kernel: Assertion failure in ext3_get_block() at inode.c:853: "handle != 0" Sep 21 23:10:05 devil kernel: kernel BUG at inode.c:853! Sep 21 23:10:05 devil kernel: invalid operand: 0000 Sep 21 23:10:05 devil kernel: CPU: 1 Sep 21 23:10:05 devil kernel: EIP:
2001 Sep 07
4
ext3-2.4-0.9.9
Patches against 2.4.10-pre4 and 2.4.9-ac9 are at http://www.uow.edu.au/~andrewm/linux/ext3/ It's a fairly large change. The most significant parts are * the inclusion of Stephen's error-handling work, which is designed to remount the fs read-only in the presence of software and hardware errors, rather than forcing a panic. * Stephen's fix for the journal_revoke assertion
2001 Oct 11
1
ext3-0.9.10 hang with kernel 2.4.10
Hi Maybe you allready fixed this problem but here goes: with ext3-0.9.10 and linux-2.4.10-SMP I get a hang doing the following: # mkdir test # cd test # rmdir ../test # ls There are no problems in ext3-0.9.12 and linux-2.4.10-ac11. Regards -- Lars Munch P.S. plz cc me, as I'm not on the list.
2001 Oct 16
1
Ext3 on NON-SMP system
Hi folks, I successfully installed EXT3 on my non-SMP system. This is a (single) P3-450 with kernel 2.4.10-ac11 with the ext3-2.4-0.9.12-2410 patch applied. Works like a jiffy, although I only converted a single disc (and a not really important one too)! (Oh and this is a SuSE 7.0 system) I'd like to note that the Util-Linux installation is pretty hard to do and can go horribly wrong. In
2001 Oct 13
3
2.2.19+ext3 or 2.4.1x+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/
2001 Sep 23
3
Ext3, 2.4.10, and 2.4 in general
Hello, The 0.9.9 2.4.10pre4 patch doesn't apply. There are 5 rejects. The first three are easy to fix, but the fourth in vmscan.c will be very difficult without being a developer. The fifth I am not sure about. This brings up the fact that many of us are using ext3 and have to patch every time a new kernel comes out. I really think we need to strong arm Linus or something and get
2001 Oct 12
0
ext3 and 2.4.10-ac12
Does anyone know if the 2.4.10-ac11 ext3 patch applies cleanly to 2.4.10-ac12? If so, do you think it's safe to use? Thanks!
2013 Mar 30
2
R/Sweave/cairo/freetype bug fix.
The problem was first seen with R/Sweave (#c0) then reproduced directly with cairo (#c10) and was eventually traced to freetype. The 5-part bug fix: 610ee58e07090ead529849b2a454bb6c503b4995 da11e5e7647b668dee46fd0418ea5ecbc33ae3b2 e1a2ac1900f2f16ec48fb4840a6b7965a8373c2b 869fb8c49ddf292d6daf4826172a308973d3e11f d56e544d653b09c657911629557ffc5277a503e3 was committed to freetype in January and will
2013 Mar 30
2
R/Sweave/cairo/freetype bug fix.
The problem was first seen with R/Sweave (#c0) then reproduced directly with cairo (#c10) and was eventually traced to freetype. The 5-part bug fix: 610ee58e07090ead529849b2a454bb6c503b4995 da11e5e7647b668dee46fd0418ea5ecbc33ae3b2 e1a2ac1900f2f16ec48fb4840a6b7965a8373c2b 869fb8c49ddf292d6daf4826172a308973d3e11f d56e544d653b09c657911629557ffc5277a503e3 was committed to freetype in January and will
2001 Oct 10
1
ordered data
Hi, I have a detailed question about ordered data writes. Suppose we (i.e. intermezzo) does a transaction, which is closed and then followed by an ordered write. Let's assume the ordered write doesn't require new allocation metadata. Is the write still postponed until the first transaction has committed? As far as I can see, prepare_write always starts a transaction, but I'm
2001 Sep 23
3
Patch for 2.4.10?
Will there be a patch of the latest version of ext3 for kernel 2.4.10 forthcoming? -- David Hollister Driversoft Engineering: http://devicedrivers.com Digital Audio Resources: http://digitalaudioresources.org
2001 Oct 12
3
ext3 mounted fs still needs fscking after crash
Hi there, I'm new to ext3, so I hope you won't find my question to be stupid. I also hope this isn't the 1,000,000th time someone posts it. My problem is the following: I converted my ext2 systems to ext3 using tune2fs -j /dev/sda2 (or 5 for my /home, 2 is my root) Then I modified fstab and put ext3 for each. After a reboot, the mount command says they are mounted as ext3. But when I
2001 Oct 10
1
ext3 patch for 2.4.11
Hi ! Is a ext3 patch against latest kernel 2.4.11 available ? Dirk
2002 Jul 08
0
(no subject)
Which version should I use out of the list? Or do I install all of them, one after the other? ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog) ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9) ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog) patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))
2002 Jul 11
1
(no subject)
Which version should I use out of the list? Or do I install all of them, one after the other? ext3-2.4-0.9.9-2410p4.gz 05Sep01 (Against 2.4.10-pre4) (Changelog) ext3-2.4-0.9.9-249ac9.gz 05Sep01 (Against 2.4.9-ac9) ext3-2.4-0.9.10-2410.gz 23Sep01 (Against 2.4.10) (Changelog) patch-rml-2.4.10-ac3-ext3-0.9.9-with-dir-speedup-1.gz 01Oct01 (From Robert Love. Unofficial :-))
2002 Jan 20
0
[ANNOUNCE] Bug in kernel == 2.4.10 causing netfilter problem
--AkbCVLjbJ9qUtAXD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all! On behalf of the netfilter core team I have the following announcement: The following kernel versions habe a bug in include/linux/list.h, which causes netfilter's connection tracking code to misbehave: 2.4.10-pre10 2.4.10-pre11 2.4.10-pre12 2.4.10
2001 Oct 20
2
FSCK?
An EXT3 filesystem technically isn't supposed to require an fsck, correct? Well, as per my last email re: EXT3 Crash?! I ran an fsck on a couple of my LVMs. It said they were clean, but then I decided to be 100% sure and force an fsck. Error after Error after Error after Error. I wound up losing almost half the data on my LVM due to all the errors. What's the real deal? Am I doing