similar to: converting / to ext3-0.0.5d

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

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

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

Kernel 2.4.8 on an Athlon 500. e2fsprogs-1.23 ext3 compiled as a module. I used "tune2fs" to make /boot and /home into ext3, and remounted them OK. (I am so amazed to see the system come right back without an lengthy fsck on these two file systems after a power off! Well done!) I also used "tune2fs -j" on /, it created a /.journal file. The debugfs features command shows

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

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

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

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

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, After mounting -t ext2 an ext3 partition, working with, do I have to recreate .journal when I remount the partition as ext3 ? Thanks ! Liu

hi. i'm using 2.2.18 with ext3-0.0.5e on a dual p3-550 with 1.5 gigs of ram. the system is redhat 6.2-based but with lots of modifications and a clean kernel build. i've been using 2.2.18 and 2.2.17 with ext3 patches on other machines with much success and no problems, up until last night, when the machine mentioned above kernel panicked on me. unfortunately i don't have much of

Hi, I've been experiencing intermittent filesystem corruption on a Compaq Armada M700 laptop w/ IBM Travelstar 30GB drives (both the 40GN and 30GN models). This happens mostly under RH 7.2, w/ ext3 filesystems, but I think it's also happened under win98. All seems fine until power-down, power-up, and boot, where the corruption is discovered. Searching these archives, I found that there

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

Hello Guys, I am looking to extend/create a file system that span networks/device of any kind, shape and manner :) Check out http://www.insync.za.net/openufs/ (also on http://openufs.sourceforge.net - but Iam not here to adv. the site !) I would like to know, where can I find what EXT3 will write to the disk, how it works etc. Surely EXT3 will write something like this : Block 0 - (1024 bytes)

Hello. Look at this: [sergey@gleam sergey]$ uname -s -m -r Linux 2.4.17 i586 [sergey@gleam sergey]$ mount | grep /home /dev/hda11 on /home type ext3 (rw) [sergey@gleam sergey]$ pwd /home/sergey [sergey@gleam sergey]$ id uid=502(sergey) gid=100(users) groups=100(users),10(wheel),13(news),512(ftpadmin),513(dos) [sergey@gleam sergey]$ stat . File: "." Size: 8192 Blocks: 16

Hi there, I'm running software raid 1 across two 60GB IDE drives and booting off the raid device. The raid device holds an ext3 filesystem. Each drive is configured as a master on its own bus. The system is redhat 7.2, stock kernel 2.4.9-31smp. The hardware platform is a Dell precision dual 2Ghz P4 system with 1G of memory. I have two of these systems, both configured identitically.