similar to: e2fsprogs 1.23 problem handling 2.2 version 1 format journals

Stephen et al, You may remember me raising the point that the new e2fsprogs (1.25 as I remember) griped about old journals not having all the appropriate fields zeroed. I've just discovered that the RH 7.2 installer produces journals (ie on partitions created as ext3 from within the installer) that flag these warnings with a modified 1.25 e2fsck (the mods being to clear the errors rather

> > Hi Ady, > > Thank you very much, I prefer this one, add the extN support to > linux/syslinux-nomtools, create a new "e2fs/syslinux" may make things > more complicated for the user, I will make it as: > > 1) If it is a extN device, then root privilege is not required. > 2) Otherwise work as before. > > Any suggestions is appreciated. > > //

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

hi all, sorry when i am off topic, but: i am trieing to compile the new e2fsprogs like the ext3-manual recommend. but it don't want to work, and it's look like i need a programm which is named "makeinfo". does anybody had the same problems, or know where i can find it? thanks for all.. i added my error-log Andreas log: make[1]: Wechsel in das Verzeichnis Verzeichnis

Hi, I am trying out ext3 with an external journal (on a battery backed RAM card). I use data=journal, and sync nfs writes go nice and fast :-) But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot get my filesystem back. It is only a test filesystem so I don't need the data. But I want this to work before I put real data on it. If I "fsck /dev/md1", it

Hi, I''m a long ext3 user (rpmfind.net). I propagated ext3 on some of our server box (W3C webservers are ext3 based too now). I might be tempted of testing out your kernel RPMs but unavailability or the source RPM and the SMP version are definite showstoppers. Please provide them. In the meantime I will stick to my own set of kernel ext3 RPMs at ftp://rpmfind.net/pub/veillard/ext3/

I'd been hoping to move all of our site to ssh protocol 2 whilst we are still small enough to do this without serious pain, however the lack of authentication and connection forwarding is making that difficult at present. I see the current (2.2.0p1) code base does not have the code on either client or server side for ssh2 to handle tunneled connections or authentication agent. Is this

I'm happy to announce the release of e2fsprogs 1.42. You can download the tarball from here: http://prdownloads.sourceforge.net/e2fsprogs/e2fsprogs-1.42.tar.gz Or you can download it from the git repository on git.kernel.org. git://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git. Or, you can wait for your favorite distribution to package it. :-) The release notes are attached

Is there any more docs on this other then the blurb on beta.redhat.com? I got a spare non-critical victim err... test machine I want to try this on and have all the RPMS, but would really like to chew on a little more detail before I leap. Regards, Henri -- "People die." --The Cynic's Book of Wisdom

Hey all. I'm not on the list, so can you please cc me? Thanks. Anyhow, I've got two questions. First, the website says that the 'latest' e2fsprogs are needed. Does this mean 1.23-WIP is needed or will 1.22 do? I'm assuming it's just a generally good idea. Second, has anyone tested this on a BE machine? I'd like to use this on my PPC. I don't mind testing

I want to convert the last of my filesystems to ext3. The only one left is /boot. It is not very big however, only about 10MB itself. Any recommendations on what size journal to put a /boot filesystem of only 10-20MB? Oh, BTW: "tunefs -j -J size=..." is awesome. No more gyrations with dd, chattr, lilo -R, etc. Nice! One note however: even in Stephen's 1.20.WIP.sct-20010216

Long ago, when I wrote the ssh config file on my desktop box, ssh (which might have been the non-openssh one) took 3 possible values for the StrictHostKeyChecking option - yes, no & ask. Today, when I attempted to connect to a new machine, with no DNS entries (so using IP address) from my desktop box, ssh (now 2.3.0p1) SEGVed. Looks like there is some subtle interaction between having an

Dear Ted, I upgraded e2fsprogs and util-linux to the latest versions, as per the instructions on the "ext3 for 2.4" page, to make the switching between ext2-only and ext3-enabled kernels seamless. Now that if the filesystems have not been unmounted cleanly, due to a power failure for example, "fsck -A -a" cannot continue after checking the root filesystem on reboot, issuing

I managed to install 0.5d today. Got all 3 of my mounts converted (even '/' though it was a pain in the ass). Now on boot, I see: mounted /dev/hda1 on / EXT3-fs: mounted filesystem with ordered data mode and the exact same thing for /dev/hda3 and /dev/hdb1. they all come up and appear to be working. so is this normal? Or did I manage to screw up somewhere? -- Douglas J. Hunley (Linux User

I have been playing with external journals some more and thought I should share some experiences. I am running 2.4.16 with the ext3 patches from Andrew Morton and e2fsprogs 1.25 I have an ext3fs filesystem on an 8 drive RAID5 array and place the journal on a partition of the mirrored pair that I boot off (all drives SCSI). I have tried pulling the power cable and seeing what happens. I finally

Hello! I'm using i868 (Pentium III) machine running Windows 2000 and running Linux, installed on dedicated partition, in parallel via VMWare. Linux config is RedHat 7.0 (kernel ) As I'm pretty new to Linux, I'd like to know exact procedure how to install ext3 filesystem support (also which packages do I need). My kernel config is as follows: kernel-headers-2.2.14-5.0

Hi, A critical regression has been discovered in e2fsck. The problem was introduced in upstream 1.41.5 and is causing updates to block group descriptors to be lost after journal replay. Our 1.41.5.sun2 (.sun1 too) e2fsprogs version also suffers from this problem. We are working on rebasing our e2fsprogs package on 1.41.6 (see bug 19852). Until the new rpm is available (should be very soon), we

Hi, A critical regression has been discovered in e2fsck. The problem was introduced in upstream 1.41.5 and is causing updates to block group descriptors to be lost after journal replay. Our 1.41.5.sun2 (.sun1 too) e2fsprogs version also suffers from this problem. We are working on rebasing our e2fsprogs package on 1.41.6 (see bug 19852). Until the new rpm is available (should be very soon), we

CentOS Errata and Bugfix Advisory 2013:0093 Upstream details at : https://rhn.redhat.com/errata/RHBA-2013-0093.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 3c4f23b06d8aad0779eb54116de372431de09bc369e783fac15de4c6bb3652bc e2fsprogs-1.39-35.el5.i386.rpm

CentOS Errata and Bugfix Advisory 2012:1016 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1016.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9c15c4d62e72295c6ab4535879cf96cc0f6e27d634da1ddb71ebe67ecda429f9 e2fsprogs-1.39-34.el5_8.1.i386.rpm