similar to: fsck still running as of ext2 (even tough it is ext3)

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii Howdy - we have a bunch of dual processor Compaqs with 180GB RAID partitions for email, running with ext2 for the last year or so. I thought I'd try out ext3 (on our development machine :-) to see whether it was a practical proposition for this kind of thing yet. Appears to be working so far, with a

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

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)

Hi! Are these results i got from my benchmarking "normal" or is there something strange happening in my system? This box is going to be a mailserver, so i tested various fs to decide on which i should utilize. I personally dislike reiserfs because it has proven somehow unreliable on our servers (although it got better in the more recent kernels), ext3 would be quite good (fsck'ing

Dear Ted, I upgraded e2fsprogs and util-linux to the latest versions, as per the instructions on the "ext3 for 2.4" page, to make the switching between ext2-only and ext3-enabled kernels seamless. Now that if the filesystems have not been unmounted cleanly, due to a power failure for example, "fsck -A -a" cannot continue after checking the root filesystem on reboot, issuing

Hi, I've recently been playing about with recent ext3 0.0.6b and lvm 0.9.1 beta7 and am now able to trigger an "Attempt to refile free buffer" assertion. This seems to "only" occur when using ext3 on the root filesystem. Possibly that is related to the fact that the lvm utility I'm using to reproduce this problem is modifying data in /etc. The easist reproduction

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

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 14 June 2001 15:58, Stephen C. Tweedie babbled: > ext3 can do both metadata-only and full data journaling. You can > enable data journaling for the entire filesystem or on a per-file > basis (ext3 uses that functionality internally to journal writes to > the quota files to keep them consistent, for example.) I learn