similar to: using non-default blocks per group

Hi guys, Is there any way to mount an ext3 fs that is on ro media? I get an error: EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access unavailable, cannot proceed. Specifically this is with an LVM snapshot.

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

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

hello, i am a newbie to this list and i don't know if this has been posted before (if so, plzz accept my apologies) i just noticed a nice mini-howto on ext2-ext3 conversion at http://www.symonds.net/~rajesh/howto/ext3/index.html i think that maybe a link can be added to this after the download section... cheers Sayamindu *********************************************************************

Hi, One of my shared volumes crashed the other day on a RH-7.2, 2.4.9-31 system. These are the first errors in the log: kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is smaller than minimal - offset=0, inode=2553887680, rec_len=0, name_len=0 kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #2424833: rec_len is

Hi, I am upgrading the tomsrtbt rescue distribution from kernel 2.0.39 to 2.2.20. Fitting a 2.4.x kernel on the floppy is not practical at this time. I am trying to support both ext3 and reiser filesystems. However, there are symbol collisions, it is impossible to use both. Is there any chance of getting the 2.2.x patch fixed? -Thanks -Tom

Hello guys, I have a question about ext3 on Linux 2.2: Are there the same file size limitation (2Gb) like with ext2? I tried google but I still with this question. ps.: Include Reply-to me, I'm not subscribed on list. Thaks for aswners, []'s -- ::: .''`. ::: ::: : :' : ::: Rodrigo Morais Araujo (rma) <rma@cin.ufpe.br> ::: `. `'` ::: UIN: 101720839

Hi, I'm running 2.4.9-ac7 with ext3 compiled in, and I ran across this problem. Now that I look back, it makes sence, but it wasn't obvious at first... I wanted to change the journal mode on my / partition, so I changed my fstab to: /dev/hda1 / ext3 defaults,errors=remount-ro,data=journal 0 1 as well as several other partitions, and rebooted. After rebooting I had a read only / that I

Hello guys, I began testing ext3 w/ a 2.2.19 patched kernel several months ago. I'm now wanting to move to a new 2.4 kernel w/ ext3 and was wondering if there was any reason to create a new journal file. Also I noticed that the oldstyle journal files are named "journal.dat" and now they are named ".journal". Any suggestions for upgrading? Thanks, Nick

quotacheck takes longer than fsck on our ext2 fileservers. Is this redundant in ext3? Do I need data=journal? Cheers, Matt

It turns out that if you specify filesystem type `auto' in /etc/fstab, updatedb (the thing which updates your `locate' database) ceases to work. Here's the contents of my /etc/updatedb.conf: PRUNEFS="devpts NFS nfs afs proc smbfs autofs auto iso9660" PRUNEPATHS="/tmp /usr/tmp /var/tmp /afs /net" export PRUNEFS export PRUNEPATHS deleting the `auto' entry

Hi. What are the right steps to convert a file system from ext3 back to ext2 ? I need to use GNU Parted to resize my root file system and Andrew Clausen said I have to convert it to ext2, resize, and then convert back to ext3. My journal is visible. My initrd.img (from which I plan to use Parted) contains both ext2 and ext3. I compile ext2 as a module in my other boot images. --

Hi, I've downloaded and installed kernel-2.4.9 from rawhide in order to use ext3 support (I've also upgraded the necessary packages). I've used tune2fs to make the current ext2 partitions (incluind /) and changed fstab to reflect that. In order to test if everything is ok (this is a test machine) I've switched off with no shutdown. Except the / all other partitions accused

Something bad must have happened when I first ran e2fstune on my root file system. Now I cannot mount it ext3 and when I try to run tune2fs -j on it, I get this error message: permission denied while trying to create journal file There is a .journal file in /: [root@monster log]# ls -l /.journal -rw------- 1 root root 33554432 Sep 29 10:21 /.journal But dumpe2fs

Hi Andreas, Any plans to do a release of the online resizing patch for ext3-1.0? I've put off asking about this until Al Viro's superblock handling and other fixes were done, but now that LVM 1.0.1 seems to be approaching a stable and -linus/-ac mergeable state, this would certainly make deploying ext3+LVM a lot simpler. Regards, Bill Rugolsky

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 If ext3 is compiled in, how can you tell which version it is? For example, how can I log into the systems I admin and tell if they are ext3 6b or 7a? - -- Douglas J. Hunley (Linux User #174778) http://hunley.homeip.net/ http://linux.nf/ Adults are just kids who owe money. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For

Hi, again I ran into some difficulties while setting up my / - partition under v0.0.5. With the conversion of my /home - partition went everything well. Even under heavy load I didn't remark anything unusal - apart from a little performance-issue. My current setup is now the following: / - partition: no conversion possible: V1-journal with journal-data mode /home - partition: conversion

After a rather severe hard boot, my machine refuses to mount homes, which are on an ext3 partition. Here is the error i get while mounting... # mount /dev/sdc1 EXT3-fs: invalid journal inode EXT3-fs: get root inode failed mount: wrong fs type, bad option, bad superblock on /dev/sdc1, or too many mounted filesystems However I am able to mount it as ext2 and continue. I am using ext3-0.0.6b on

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

Erm, sheez having alot of problems :( I have just been reading all the archives on the mailing list for the past few hours and decided to try make the journal with: tune2fs -j -J10 /dev/hdc1 [root@tkw /]# tune2fs -j -J10 /dev/hdc1 tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3