similar to: moving from 2.2 to 2.4

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

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

Redhat 7.2 - ext3 filesystem. Is it possible to recover deleted files immediately after deleting them? I have found utilities for recovering data from ext2 filesystems... Help Regards Matt Cunningham Technology Manager Digital Post matt@digipost.co.nz

I updated my kernel from 0.0.3d to 0.0.3e using the "d-e" patch in the 0.0.3e tarball. When I try to boot the new kernel on a machine with an ext3 root filesystem I am getting the message: JFS: Unrecognised features on journal Does this sound feasible or even somewhat expected? Is there any interest in me doing some debugging of this? Is there any way to deal with this without

Hi, now that Ingo+redhat have discovered the cause of the ext2 corruption under heavy load of 2.4.x a couple of -preX patches ago (BTW ext2/3 gurus - what is the difference between bforget() and brelse() - I'm a bit too dense to understand the explanation given in the -pre patch?) I wonder whether you folks are still finding heavy load corruption problems for 2.4? [My production servers are

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

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

Dear list, pardon my ignorance on ext2/3fs. Is the ext2fs' 4Tb file system and 2GB maximum file size limit still true in ext3fs? Thanks for your reply, Gotze __________________________________________________ Do You Yahoo!? Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com

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

Just fired up a test machine on its first 2.4 kernel - specifically 2.4.9-ac16 (includes ext3 0.9.6). Had also upgraded e2fs tool set to 1.23. This box has previously had 2.2 kernels with Stephen's ext3 patches, and looks like it was last rebuilt from scratch in early March. I suspect it may have an old version 1 format journal on the filesystems. [Unfortunately I managed to destroy the

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

I am running debian unstable. I applied the ext3 patch to the 2.4.9 kernel source, and got ext3 working fine. However, when I shut my system down (shutdown -h now or shutdown from kdm), it does not turn the power off. The whole shutdown sequence runs, and finally displays the message "Power Down", but nothing else happens. At this point, the power switch does not turn off the

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

I've been playing with the -g switch to mke2fs, which controls the blocks per group. This switch isn't documented. I've been using it to balance metadata traffic on RAID 0. This seems to work fine in ext2. Will I have any problems with ext3 where the blocks per group is not a power of 2? -jwb

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

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