similar to: Problem with root file system

I am using a Redhat 7.1 system with the Kernel 2.4.10. I have the two partitions on the system: /dev/hda1 = / /dev/hb5 = /extra I was able to create the journal for both filesystems using the tune2fs -j command. I have also updated my "fstab" file to reflect "ext3" When I try to reboot the machine without unmounting the filesystems. It still shows that I have not cleanly

I just came back after being out for the evening. Apparently there was a power failure long enough to discharge the UPS completely on my Linux box. After powering back up, I received notice that the / filesystem needed "manual fsck"ing. I booted off CD and attempted to fsck. Unfortunately, everything I've tried has proved futile and I'm _desperate_ for some help. I've

Hi everyone, I've been running Redhat 7.2 (new install) for about 2 weeks now without any problems, but today I was not so lucky. My system hung while I was trying to configure the kernel-source RPM using 'xconfig'. After rebooting the system, it seems that my whole ext3 file system is corrupted. I get the message: Mounting root filesystem EXT3-fs: ide0(3,3):couldn't mount

'df' doesn't report my root partition, but does report my /boot partition when both are mounted with <type> auto. But when mounted with <type> ext3, both partitions are reported. Details: The system has mount-2.11m, tune2fs-1.25 and df (fileutils) 4.1 I just created an ext3 fs on a new Debian Woody install initially running linux-2.2.19 on ext2, but upgraded to

Erm, sheez having alot of problems :( I have just been reading all the archives on the mailing list for the past few hours and decided to try make the journal with: tune2fs -j -J10 /dev/hdc1 [root@tkw /]# tune2fs -j -J10 /dev/hdc1 tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3

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:

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

I decided to start using ext3. My kernel 2.4.15p9. I downloaded and build util-linux-2.11m and e2fsprogs 1.25. I compiled ext3 in the kernel. I started converting my filesystems and thing went ok for the first few. I then started getting the following on each additional filesystem. [root@joker /root]# tune2fs -j /dev/hdc4 tune2fs 1.25 (20-Sep-2001) Creating journal inode: done This filesystem

> Hello, Hi! > I just need a little clarification regarding applying the ext3 patch > to the latest kernel. > I have 2.4.7-10 that came with RH 7.2. > I have ext3 running. > I need to upgrade those (to get some USB device working). > So I got the latest kernel, 2.4.14, patched it with the ext3-2.4- >0.9.15-2414 patch, picked ext3 from 'make xconfig', built the

Hello, I just need a little clarification regarding applying the ext3 patch to the latest kernel. I have 2.4.7-10 that came with RH 7.2. I have ext3 running. I need to upgrade those (to get some USB device working). So I got the latest kernel, 2.4.14, patched it with the ext3-2.4-0.9.15-2414 patch, picked ext3 from 'make xconfig', built the kernel, but the new stuff in /boot, etc.,

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

Hello, I recently implemented ext3 using tune2fs -j /dev/hda1, and have been using it successfully for a while. However the .journal file is huge and growing on my limited amount of disk space. How can I rotate or re-initialize the file, preferably without rebooting, on a daily/weekly basis? Regards, Dan Barber Mojolin --------------- Mojolin: Linux, Unix and Embedded Jobs and Resumes.

All -- I'm curious is if it safe or even wise to run the following command on a mounted filesystem, namely root (/)? tune2fs -j /dev/hda1 What about if someone goes into single user mode and runs this first? mount -o remount,ro / And then to enable it, runs this? mount -t ext2 -o remount,rw / I assume it is not safe to do so, but one user in my LUG assumes otherwise. Just curious,

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 tried to convert my root partition from an ext2 to ext3 fs using tune2fs. I'm running a 2.4.10 kernel with ext3 support, but the partition is not mounted ext3. In fact the journal feature is missing from the superblock: # cat /proc/filesystems | grep ext ext3 ext2 # tune2fs -l /dev/hda6 | grep features Filesystem features: filetype sparse_super # ls -l /.journal

I referred to the entry rootfs / rootfs rw 0 0 in the output of "cat /proc/mounts", that is not really very much explicative, due to the setting "auto" in /etc/fstab and to the fact that file system had has_journal flag and no ext3 module was mounted. But I was wrong: I think that if you have an ext3 fs and you mount it as ext2, you continue to see the has_journal flag with

~ ~ ~ ~ ~ rss:/etc # 358C written rss:/etc # man mount Reformatting mount(8), please wait... MOUNT(8) Linux Programmer's Manual MOUNT(8) NAME mount - mount a file system SYNOPSIS mount [-lhV] mount -a [-fFnrsvw] [-t vfstype] mount [-fnrsvw] [-o options [,...]] device | dir mount [-fnrsvw] [-t vfstype] [-o options] device dir

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