similar to: ext3-0.0.6b available

Hi all, ext3-0.0.5c is now up at: ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ The most important part of this release is the e2fsprogs: e2fsck now supports the journal changes for metadata-only journaling. Ted, I've changed around the use of jfs* include files in e2fsprogs quite heavily here. In each build directory --- the lib/ext2fs

Hi, ext3-0.0.6a has been uploaded to ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ext3-0.0.6a.tar.gz and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ext3-0.0.6a.tar.gz This version changes the way dirty buffers are marked to protect against device drivers which might block in the ll_rw_block() function. (Loop and lvm are examples.) It should also fix a rare but persistent report of

Hi, ext3-0.0.5d.tar.gz is now up on ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ as patches against 2.2.18. This only contains the kernel bits: we're in the process of syncing up on some e2fsprogs so I'll do another release shortly once we've got all of the pending changes for the user-mode tools assembled. This release is mostly

Our main NFS-server, running Debian Potato, died this morning whilst under quite heavy load - due to a runaway perl-script forking of some 200 instances of "/bin/cp" (the load was ~ 50). The server is running 2.2.19pre14 with ext3-0.0.6b. The server is running kernel-nfs. Assertion failure in journal_dirty_metadata() at transaction.c line 796: "bh->b_next_transaction ==

Hi all, OK, here is ext3-0.0.5e. Changes since 5d are summarised below. The major changes are the barrier support: this infrastructure should be sufficient to allow the snapshotting interface which LVM is wanting for ext3. The journal initialisation fix will also help people adding ext3 to an existing filesystem. Look for ext3-0.0.5e.tar.gz on:

Hi all, I've pushed my current set of ext3 diffs (against Marcelo's current tree) to http://people.redhat.com/sct/patches/ext3-2.4/dev-20030314/ This includes: 00-merged/ diffs recently merged into 2.4 10-core-fixes-other/ misc fixes/tweaks from akpm, adilger 11-core-fixes-sct/ misc fixes/tweaks from sct 20-tytso-updates/ Ted's recent updates 21-updates-sct/ recent sct diffs

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

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

If a Xen guest has a bootloader configured, then it will fail to start on a blktap image. The problem is blkdev_uname_to_file, which cannot parse the "tap:aio:$filename" image strings: it tries to split the string apart at ":" and assign the result to a 2-tuple, and this results in a python error if the split results in three or more strings. The fix is to split only at the

Hi! A few weeks ago we upgraded 9 large webservers from ext2 to ext3. Since then we've seen very strange behavior on several of the machines. Permissions of files are repeatedly changed at random occasions. Several times, ownership of files have been totally mangled. Several users have logged in to discover that all their files suddenly are owned by another user! At two of these occasions

Hi all (and developers in particular) I just got bitten by this Assertion. The one that starts as in the subject, and ends with: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" Google reminds me that it was mentioned a few times earlier this year, but I couldn't find any statement saying that it has been fixed. I got this in a 2.4.16 kernel, though the

I am trying to obtain adjusted means and standard errors for a three way ANOVA I have three effects, two continuous; fire frequency and annual precipitation, and one categorical; soil type in an unbalanced design. I am testing the effect of annual precipition (AP), soil type (ST), and fire frequency (FF) on stem count (SCt) My data table looks as such: ST FF AP SCt 3 Coy

While investigating erratic performance on one our our servers, I'm getting some very odd performance stats coming from vmstat. What initially appeared to be happening is the machine goes into a hard loop in some mod_perl webserver code. Now there still may be an issue with the code, but my code examinations show no possible way this could be happening, but what I'm writing to you

Hello All! I've asked this question on others lists but didn't found any answer - full distro upgrade was only reasonable option. I understand why ext3 patches require up-to-date e2fsprogs - ext2 in heavy development. Q1: Why ext3 requires 'very' up-to-date util-linux? I've tryed to upgrade from tarball - but realized that I can run into problems with my distro. SuSE

Hi, I have uploaded ext3-0.0.5b.tar.gz to ftp.*.kernel.org:/pub/linux/kernel/people/sct/fs/ext3/test/ and ftp.uk.linux.org:/pub/linux/sct/fs/jfs/test/ New in this release is a functionally complete implementation of metadata-only journaling: data writes will no longer have to be written to the journal. Journaling still imposes some extra serialisation points between interacting processes, so

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

Hello everybody, Could someone please explain to me what is the difference between kjournald and jbd (precisely, what does each of them do?) Thank you, Alina _________________________________________________________________ Chat with friends online, try MSN Messenger: http://messenger.msn.com

On Mon, Nov 26, 2001 at 10:00:39PM +0800, Yusuf Goolamabbas wrote: > Hi Andrea, The following is a thread on ext3-users in which sct mentions > that this is due to a core VFS bug introduced in 2.4.10 which applies > ulimits to block devices. Maybe this could be due to some interaction > with your blockdevice in pagecache > > I don't know if you already have a fix in your

Fellow riders of the bleeding edge of ext3 technology, I've been playing with ext3 on my workstation. For the most part it has worked very well, but right now I have a non-functional system. I've got patches out the wazoo on this kernel - 2.2.18 + Alan's 2.2.19pre13 + ext3-0.0.6a + i2c-2.5.5 + lm_sensors-2.5.5 + udf-0.9.3. Here is the output I get: EXT3-fs: WARNING: recovery