similar to: not mounting ext3, 2.4.10

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 all, On my slackware 7.1 system, in rc.S fsck is started. In fstab there's the following line: /dev/hda2 / ext3 defaults,noatime 1 1 from the readme I figured that I should put the line append="rw rootflags=journal=102" in lilo.conf The system boots up, but I get the error message that the root partition is already rw. Should I just skip the filesystem

Dear all, I'm looking to create a formula within a function to pass to glmer() and I'm having a problem that the following example will illustrate: library(lme4) y1 = rnorm(10) x1 = data.frame(x11=rnorm(10), x12=rnorm(10), x13=rnorm(10)) x1 = data.matrix(x1) w1 = data.frame(w11=sample(1:3,10, replace=TRUE), w12=sample(1:3,10, replace=TRUE), w13=sample(1:3,10, replace=TRUE)) test1 <-

Good morning, I try to use the last release of ext3 patch with a 2.4.10 linux kernel. I have two troubles : - when the kernel is booting, I receive : NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 208k freed Adding Swap: 128480k swap-space (priority -1) Adding Swap: 128480k swap-space (priority -2) Why my root

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

I've just set up a brand new system with software raid1 (in degraded mode) with one IDE 20GB drive, using kernel 2.2.19pre16 with ext3 0.0.6b. It's split like this.. 32MB /dev/hda1 /boot 2GB /dev/hda2 / ~18GB /dev/hda3 /home all partitions are marked as 0xfd (autostart raid) with the patches from http://people.redhat.com/mingo/raid-patches for 2.2.17. And I've made all the ext3

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

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

Hi, hoping that someone on this list can help me here is the Problem. After a crash it seems the journal could not be recovered. This is what mount gives: root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt mount: wrong fs type, bad option, bad superblock on /dev/hdb2, or too many mounted file systems and this is the corresponding logfile-entry: Nov 27 11:16:13 wuehlkiste kernel: attempt to

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 there, I'm new to ext3, so I hope you won't find my question to be stupid. I also hope this isn't the 1,000,000th time someone posts it. My problem is the following: I converted my ext2 systems to ext3 using tune2fs -j /dev/sda2 (or 5 for my /home, 2 is my root) Then I modified fstab and put ext3 for each. After a reboot, the mount command says they are mounted as ext3. But when I

'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

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

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 , our centos os has an ext3 file system. and i cant create any more directories, it gives me a too many links error, even when doing a manual mkdir. is there any workaround for this? without changing it to a different file system like reiserFS? we dont have a reiserfs module in the os so it will have to be installed. and can it be possible to install a reiserFS without having to reformat the

What's the easiest way to transition to a larger HD when using LVM2? I'm running Centos 4.4. I'm going from a 20gb HD to a 40gb HD. I've already DD'd it to the 40gb HD. So now I have 20gb of unused space. Ideally, I'd like to make it one big physical space for the logical space instead of making another physical partition to expand the logical. Here is what I have now

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

Hello, it seems I am having a problem with loop mounting on ext3. I am doing this: - make an ext2 filesystem in a file - loop mount this file - write into the loop mounted file system - umount the file Sometimes this works; occasionally the file remains empty after the umount. A sync before the umount seems to help. Is this a known problem? Thanks, Andreas.

Hi all (and developers in particular) I just got bitten by this Assertion. The one that starts as in the subject, and ends with: "!(((jh2bh(jh))->b_state & (1UL << BH_Lock)) != 0)" Google reminds me that it was mentioned a few times earlier this year, but I couldn't find any statement saying that it has been fixed. I got this in a 2.4.16 kernel, though the