similar to: 1.36 rpm

Given that no 1.36 has appeared from Fedora Core, I thought I would create the rpm myself. I took the 1.35-11.2 src.rpm from FC3 and updated the spec file for 1.36. However, the build fails. Has anyone successfully created a 1.36 rpm for FC3? If so, what did you need to do? Gene

I've just made e2fsprogs 1.36-rc1 available on Sourceforge: http://sourceforge.net/project/showfiles.php?group_id=2406&package_id=2383&release_id=295092 Fedora Core 3 users will be strongly encouraged to upgrade to e2fsprogs 1.36, since it has numerous bug fixes to some of the Fedora-specific enhancements to e2fsprogs --- in particular, supporting on-line resizing feature using the

SUMMARY We are getting many ``Free blocks count wrong for group'' errors when running e2fsck on a 245-GB ext3 filesystem. This is when the file system is cleanly unmounted on a relatively quiet system to do a resize. From reading other messages here, my suspicion is that this is because we have e2fsprogs 1.32. Questions: * Should we use e2fsck/e2fsprogs 1.36 and will that probably

boy, if you really care about your problem, *USE* ext3-users: > oh, and please respond on-list, perhaps other ppl are curious > about some details too ;) really. Tobias Amon schrieb: > Hi, > > I use e2fsprogs version 1.5.2 (I think) http://e2fsprogs.sourceforge.net/ exists, latest version is 1.35. > I got another solution. Yast, which came with Suse > is not able to

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11,

Recently, I had some experiences that raises the question as to how compatible (how safe) it is to mount and then read/write a partition using a system such as FC1 or debian where the partition was created under FC3. 1. I recently attempted to run e2fsck running on a FC1 system against a FC3 ext3 partition ... the program refused to run. When I took the e2fsprogs package from FC3 and

When I try to compile e2fsprogs-1.24a I receive the following snippet: tillarium:/home/tilleyrw/downloads/ext3 Files/e2fsprogs-1.24a# mkdir build;cd build tillarium:/home/tilleyrw/downloads/ext3 Files/e2fsprogs-1.24a/build# ../configure <<SNIP>> ./mk_cmds: Files/e2fsprogs-1.24a/lib/ss: No such file or directory mk_cmds: Couldn't find mk_cmds's template files. make[2]: ***

Im intending use Ext3 file system in my web farm. Im using RedHat 6.2 (kernel 2.2.16-3) and Turbo Linux Cluster Server 6.0. I have NO SUCCESS in path my own kernel. I downloaded the following ext3 packages: ext3-0.0.2f.tar.gz (linux-2.2.16-3.kdb.diff , linux-2.2.16-3.ext3.diff ) e2fsprogs-1.20-0.WIP.i386.rpm e2fsprogs-1.20-0.WIP.src.rpm e2fsprogs-1.20-0ext3.i386.rpm

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

Hey Stephen or Ted, Since ext3 is incorporated in linux-2.4.15-pre3 do you think we should update the Documentation/Changes since so many people had troubles with e2fsprog-2.1.19 and ext3 ? I couldn't see any RPM's after 2.1.19 so I removed RPM from the Changes file. Albert --- linux/Documentation/Changes.orig Sun Nov 11 22:17:34 2001 +++ linux/Documentation/Changes Sun Nov 11 22:21:07

On Fri, Apr 18, 2014 at 06:56:57PM +0200, Patrik Horn?k wrote: > > yesterday I experienced following problem with my ext3 filesystem: > > - I had ext3 filesystem of the size of a few TB with journal. I correctly > unmounted it and it was marked clean. > > - I then ran fsck.etx3 -f on it and it did not find any problem. > > - After increasing size of its LVM volume by

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

Hello, Hope you will forgive me for asking some very simple question about e2fsprogs. I am very new to the kernel as well as file system programming. My task is to collect superblock, inode, bitmap ( or free list) information from ext2/ext3 filesysteam. After searching the google, I came to know about e2fsprogs, which I was able to install and use at least "dumpe2fs" utility. This

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 all, I am running fedora 11 with kernel 2.6.30.9-102.fc11.x86_64 #1 SMP Fri Dec 4 00:18:53 EST 2009 x86_64 x86_64 x86_64 GNU/Linux. I am noticing a partition on my drive is reporting incorrect size with "df", the partition is ext3 size 204GB with about 79GB actual usage, the "df" result show the partition size to be 111GB, 93GB is missing. Please advice on what

Hi, it seems you got it right! I don't know if you read email I sent you before posting to the mailing list, but I accidentally diagnosed the cause... :) I've noticed that inodes fsck warned me about, at least ones that I checked, all have all four timestamps latest in 2010... The filesystem has maximum 1281998848 inodes, which is timestamp in august 2010. I don't know how it got

Hi, Theodore, Thanks for your tests. But I got the problem and got it FIXED by flushing out the contents of /etc/blkid.tab before cloned clients reboot. I'm using the e2fsprogs-1.34-1 comes with Fedora Core 1. hello06.alexa.com root 135% rpm -qf /sbin/fsck e2fsprogs-1.34-1 hello06.alexa.com root 136% and the original contents in /etc/blkid.tab are attaching below, while my

One of my servers appears to have some filesystem corruption. I'm running Red Hat 6.2 with kernel 2.2.19pre6 and ext3 0.5e. That server currently has e2fsprogs-1.20-WIP-0117 installed. Is it OK to upgrade to the latest e2fsprogs (i.e.: 1.22) prior to running the e2fsck on the filesystem? --Shawn