similar to: Recovering deleted files - possible?

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

Hi, [Background] I've been trying (unsuccessfully) to get a reliable RH linux distribution installed on my Intel machine with journaling on my large disks (not interested in journaling the root fs). I've tried using ReiserFS and eventually had some success, but it would seem that they are more in bed with Suse. It would appear that RedHat has chose ext3 as it's current journaling

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.

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

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

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 because of strange reasons my notebook sometimes crashes short after startup (but that's not ext3's fault, maybe mem?, when i wait several minutes it works without problems) the problem is that after 3 crashes at startup, when my notebook finally worked i got the msg: Sep 23 23:29:17 blackbox kernel: EXT3-fs warning (device ide0(3,3)):

In a fit of irony, while preparing to burn a CDROM with some software I've been writing for about six months, I did a rm *>o instead of rm *.o on an ext3 filesystem. And I'm well aware that under normal circumstance you can't undelete, especially a ext3 filesystem. However, I need to at least *try* to recover this. I've built lde (linux disk editor) and if I can isolate a

Hello all. I am currently using ext3 0.0.5d with great success. I am a bit conflicted about what to tell the system regarding my root filesystem however. I have my root filesystem configured and working as an ext3 filesystem, but it is/was not without some fraught. Using RedHat 7.0, if you simply create your journal on the root file- system, figure out it's inode number, issue a lilo -R

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

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