similar to: Ext3 performance vs. Ext2 for synchronous I/O

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

Reading archives I did found letter related to my question: Stephen C. Tweedie: > > On Fri, Jul 20, 2001 at 08:27:44PM +0300, Nikolaos Kefalas wrote: >> I want only to ask , if it is necessary to run tun2fs -J the kernel to have >> support for ext3 . >> I want to boot , from another linux to convert my partions since the partition >> must not be >> mounted

Hi, Also I do have some problems mounting an ext3fs which gets just mounted as an ext2fs. (Yeap, I looked a little bit around in the mailling list and found similiar problems which haven't help me ;-( ) I have a root ( /) and a /mnt partition. both are converted via tune2fs -j into a journaled fs. my fstab looks like this: /dev/hda1 / ext2 defaults

Hi there, I tried to setup my linux box with an ext3 root file system. That failed because of wrong initrd settings. Sorry. Now the filesystem is marked having a journal but there is no /.journal file anyway. I tried to buikd that journal by hand (tune2fs -j /dev/hda3 - in my case). That fails also. :-( /sbin/tune2fs -l /dev/hda3 says: ... Journal UUID: <none> Journal

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

I'm using the ext3-patched version of Linux 2.4.13 (the patch from Andrew Morton's UOW site). I compiled both ext3 and ext2 into the kernel. I've also done "tune2fs -j /dev/hda3" and changed /etc/fstab to ext3. However, when I boot up, the filesystem still gets mounted as ext2. I've been trying to figure out why for many days now.. any ideas? Here's my setup:

Hi, I try to convert my RedHat 7.3. partitions from ext3 to ext2. I have found a thread dealing with this issue. Thus: "tune2fs -O ^has_journal /dev/foo" and "e2fsck /dev/foo" will do the magic! This works fine for "/boot" but when I try to convert "/" my kernel panics? The kernel panics message appears shortly after the attempt to startup kjournald. How

Hi, I want to change my running software raid1 from ext2 to ext3. I'am currently running RH 7.1 with 2.4.18. The raid constist of two 40GB disks on a seperate UDMA Controller (HPT370). The system is installed on another disk. Can I just use tune2fs -j /dev/md0, or do need to rebuild the raid from scratch with ext3? Many thanks for your help! Regards, Ingo

Can anyone comment on whether or not it is possible to successfully disable the journal of an ext3 root file system prior to reboot? My application is to try and make sure there is no journal prior to installing and rebooting into a system which does not support ext3. I know that as long as the root is cleanly remounted r/o with no journal updates pending, this will be compatible. I'm

Hi, I have installed Red Hat Linux 7.3 with ext2 file system and I have multiple partition. I converted them to ext3 using following command. tune2fs -j -i 0 /dev/hdaX And I modified /etc/fstab as below. LABEL=/ / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts

Hi, I am a new ext3 user and I am having problems similar to what many people are facing on this list. I have done everything as the emails suggest. I am using SuSE 7.3 with the the 2.4.10 kernel and ext3 compiled as a module. Because it is 2.4.10 kernel, I created all my journals from a rescue disk and everything seems to be working right for the non-root filesystems. My fstab has all my

Hi, Suppose you have an ext2 Partition at 14GB which is 80-90% full. Most files are smaller than 1 MB (there are just 20 or so which are over 100MB where 800MB is the biggest one). Block size etc - everything is default. Now you do this: mke2fs -j /device Important is the "-j" switch. What happens without the "-j" switch? All superblocks and inodes are overwritten. Is this

fsck (Red Hat Enterprise Linux AS 2.1) returns an exit code 127 on an ext3 file system when run from a shellscript started by cron. Here is the pertinent part of the script: ... fsck -p /dev/${BK_SLICE} 1>/dev/null 2>&1 STATUS=$? if [ ${STATUS} -ne "0" ] then echo "${MIR_PID}: file system check of /dev/${BK_SLICE} failed, status = ${STATUS}" >>${LOG}

Hi guys'n'girls, I think my question is : How can I tell a redhat 2.4.x kernel (via grub or LILO command-line parameters) that the root filesystem is ext2 and not ext3 ? I thought it would just look in /etc/fstab, but presumably it needs to know what fstype the root is before mounting it; the words 'chicken' and egg' spring to mind. Or does some initrd jggerypokery go on?

Hi. I'm using Debian. Is this a Redhat-only list, or is it only hosted by RedHat? I recently changed my filing systems over to ext3, but deliberately left the forced boot check parameters alone so my system checks after 20 mounts. I notice that the fsck takes a good ten times longer than under ext2, to perform the cleanly unmounted check. (On the occasion where I did unmount dirtily, the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 14 June 2001 13:05, Rick Sivernell babbled: > Doug > > Educate me please. What is the diff between ext2 & 3. I am using reiserfs > now and do like it. But I do like to have the stuff going, if I can. Be warned, I know nothing about reiserfs other than what I've read. short version: ext3 is a further development of

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

I am using SuSE 7.3 compiled ext3 support into the kernel and installed it. All my partitions load up as ext3 except / . I ran tune2fs several times, still doesn't take on the / drive. Most recent dumpe2fs -h show no features on that drive=, I keep going around in circles, removing .journal from / and running tune2fs but it never works for / What am I doing wrong? ( thanks in advance)

greetings. i have been three days now trying to add ext3 to an existing suse-7.3 machine. i am using suse's own 2.4.13 kernel source. here is what i have done: following install, i ran tune2fs -j /dev/hda2 (also hda3 and hda4). .journal files were created on each partition, apparently uneventfully. wishing to avoid ai irreversable situation, i initially edited /etc/fstab thusly:

I have a partition that is formatted as ext3 however, due to apparent performance issues (not sure if they are related to journaling - data=ordered, BTW) I have mounted this file system as ext2. The file system was clean when it was shutdown, and has been cleanly mounted as ext2, and I currently have no problems with the partition. My question is, is there any harm in mounting this partition as