similar to: ext3-0.0.5b test release is available

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, 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

---------- Forwarded Message ---------- Subject: ext3 for 2.4 Date: Thu, 17 May 2001 21:20:38 +1000 From: Andrew Morton <andrewm@uow.edu.au> To: ext2-devel@lists.sourceforge.net, "Peter J. Braam" <braam@mountainviewdata.com>, Andreas Dilger <adilger@turbolinux.com>, "Stephen C. Tweedie" <sct@redhat.com> Cc: linux-fsdevel@vger.kernel.org Summary:

An update to the ext3 filesystem for 2.4 kernels is available at http://www.uow.edu.au/~andrewm/linux/ext3/ The diffs are against linux-2.4.7 and linux-2.4.6-ac5. The changelog is there. One rarely-occurring but oopsable bug was fixed and several quite significant performance enhancements have been made. These are in addition to the performance fixes which went into 0.9.3. Ted has put out a

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'm setting up a new fileserver. It has two RAID controllers, a PERC 3/DI providing mirrored system disks and a PERC 3/DC providing a 1TB RAID5 volume consisting of eight 144GB U160 drives. This will serve NFS, Samba and sftp clients for about 200 users. The logical drive was created with the following settings: RAID = 5 stripe size = 32kb write policy = wrback read policy =

Howdy, Some ext2/3 benchmarks on a IBM-DPTA-372050 connected to k7 650MHz. The same partition was used on all tests roughly with the same disk usage. bonnie on ext2: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU

Hi, I've recently benchmarked btrfs v0.11 & v0.12 against ext2, ext3, ext4, jfs, reiserfs and xfs. OS: Ubuntu Hardy Kernel: 2.6.24(-5-server) Hardware: --------- Fu-Si Primergy RX330 S1 * AMD Opteron 2210 1.8 GHz * 1 GB RAM * 3 x 73 GB, 3Gb/s, hot plug, 10k rpm, 3.5" SAS HDD * LSI RAID 128 MB Fu-Si Econel 200 * Intel Xeon 5110 * 512 MB RAM

Hi, I'm looking for some experience regarding using ext3 journaled, ordered or writeback modes through NFS. I wonder what is the best ext3 mode to use with NFS: journaled, ordered or writeback ? And what is provided for atomicity and ordering of write requested through a NFS client with these 3 modes ? As there is some NFS caching and segmentation policies, that are done independently of

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.6b is now available at the usual places: ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ and ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ The only significant change in this release is the fix to the orphan list recovery, and that fix also affects e2fsprogs, so please pick up the new e2fsprogs from the same directory when you grab the ext3 release. I've put tarballs,

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 14 June 2001 13:05, Rick Sivernell babbled: > Doug > > Educate me please. What is the diff between ext2 & 3. I am using reiserfs > now and do like it. But I do like to have the stuff going, if I can. Be warned, I know nothing about reiserfs other than what I've read. short version: ext3 is a further development of

Hi, I have a question on fsync() and ext3's journaling modes. Assume that I call fsync(fd) on a file. If that file is in 'data=journal' mode, would the fsync() return once the data gets safely into the journal ? On the other hand, if that file is in 'data=writeback' mode, would the fsync() return only when the data gets safely into its actual location ? Any help is

Okay, after playing around a bit more, I'm getting two oopes in a row when running dbench 16 or dbench 32. Decoded, here they are: Assertion failure in unmap_underlying_metadata() at buffer.c:1530: "!buffer_jlist_eq(old_bh, 3)" kernel BUG at buffer.c:1530! Oops: Exception in kernel mode, sig: 4 NIP: C003BB34 XER: 00000000 LR: C003BB34 SP: CF881E00 REGS: cf881d50 TRAP: 0700 Using

Hi, ext3-0.9.18 is now available for 2.4.19-pre8. Some of the fixes in this release are already in the 2.4.19-pre8, but there are some important new fixes in the patch and users are encouraged to upgrade. This release fixes all known outstanding bug reports. The full patch against linux-2.4.19-pre8, and a tarball of the individual fixes in this patch set, is now propagating to

Hi. While reading Documentation/filesystems/ext2.txt I noticed that the information about ext3 is outdated: The ext3 code is currently (Apr 2001) available for 2.2 kernels only, and not yet available for 2.4 kernels. Journaling (ext3) ftp://ftp.uk.linux.org/pub/linux/sct/fs/jfs/ The file was touched when I applied the 2.4.7 patch from Linus, so I suspect it's maintained. --

I have a question regarding a thread in June called "Distinct transactions", which I have included below. It seems to me that the solution is not atomic for daemons opening the file as there is a moment where the filename is not in the directory (i.e. unlink then link). In summary, poster Charlie Woloszynski wanted to update a configuration file in a safe manner (i.e. as a

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