similar to: ad: converting / to ext3-0.0.5d

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

Hi, recently I recognized, that some of the files of my laptop (mostly binary-files, StarCalc, PDF, ...) are corrupted. The files couldn't be viewed or opened (with SO) anymore. The files from older backups, before I used ext3-0.0.5 in ordered mode work still pretty well. I had no fatal crash or something simillar between these dates (OK, I had two times a powerloss of my laptop), but nothing

Hi all, I've been working with the ext3-fs for several months (since 0.0.2c), and it works pretty fine for me, but I haven't found out, how I works to migrate my root-partition from ext2 to ext3. I tried it with the commands at the lilo-prompt, but it didn't work. I only received a kernel panic. Any ideas, how I can migrate to ext3 on my root-partition? tnx, Joachim -- Joachim

Hi Stephen, could you give us an idea, when we could expect the patch for the 2.4-series kernels? Do you have a 'roadmap' here or are you waiting here for the 'complete' kernel-API for the journaling filesystems? thanks, Joachim -- Joachim Kunze Alte Marktstrasse 16 Tel.: +49-7042-830006 D-71665 Horrheim Fax: +49-7042-830006 Germany eMail:

Hi, ext3-0.0.5d.tar.gz is now up on ftp.uk.linux.org:/pub/linux/sct/fs/jfs/ and ftp.*.kernel.org:/pub/linux/kernel/people/sct/ext3/ as patches against 2.2.18. This only contains the kernel bits: we're in the process of syncing up on some e2fsprogs so I'll do another release shortly once we've got all of the pending changes for the user-mode tools assembled. This release is mostly

Hi, i am having problems converting the rootfs - I created a journal and booted with "rw rootflags=journal=<inode>" - Before i changes the fstab and put the WIP fsck to /sbin/fsck.ext3. The kernel seems to mount the filesystem ok and then the bootup scripts (debian potato) try to fsck the rootfs which leads to e2fsck 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 JFS DEBUG:

Hi all, OK, here is ext3-0.0.5e. Changes since 5d are summarised below. The major changes are the barrier support: this infrastructure should be sufficient to allow the snapshotting interface which LVM is wanting for ext3. The journal initialisation fix will also help people adding ext3 to an existing filesystem. Look for ext3-0.0.5e.tar.gz on:

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

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 :) when using ext3, i can't get my hard disks to go to standby mode any more. i am using timeouts set by hdparm with 2.4.18 kernels. even when i issue a standby command manually, the disk spins up again after a few seconds. however, (to my knowledge) no user space program accessed this disk at that time. i suspect ext3's journal to be causing the disk accesses. is that possible?

According to this: http://www.redhat.com/support/wpapers/redhat/ext3/why.html ext3 is forward and backward compatible with ext2... Any user who wishes to un-journal a file system can do so easily... I am assuming un-journalling is the equivalent of converting it to ext2. How do you do this? I haven't been able to find anything. The reason I want to do this is so I can modify my

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! Today I switched over to devfs. I'm on Debian unstable, installed devfsd, installed a kernel with devfs support and "devfs mount on boot". Reboot, devfs is being used. All over a sudden, dmesg reports: Linux version 2.4.21-ac1 (root@hummus) (gcc version 3.3 (Debian)) #1 Sun Jun 15 19:06:13 CEST 2003 ... kjournald starting. Commit interval 5 seconds EXT3-fs: mounted

My guinea pig laptop has only a / partition, and a small /boot partition. I installed the ext3 kernel succesfully (I think). Now, how do I get / converted to ext3? I'm thinking: * Use mkbootdisk on a floppy, to create a boot disk with the ext3 kernel. * Boot off the floppy. * Follow the instructions to convert / to ext3. * Change the filesystem type in /etc/fstab to ext3. * Reboot.

Our main NFS-server, running Debian Potato, died this morning whilst under quite heavy load - due to a runaway perl-script forking of some 200 instances of "/bin/cp" (the load was ~ 50). The server is running 2.2.19pre14 with ext3-0.0.6b. The server is running kernel-nfs. Assertion failure in journal_dirty_metadata() at transaction.c line 796: "bh->b_next_transaction ==

Hi, yesterday I upgraded my kernel to 2.4.15-pre6 (after months of using only ac-kernels) and had my first ext3-error since 0.0.3 . syslog tells me : Nov 20 18:16:31 enterprise kernel: EXT3-fs error (device ide0(3,9)): ext3_readdir: bad entry in directory #47390: inode out of bounds - offset=0, inode=404363549, rec_len=4096, name_len=23 and the system remounted /usr to ro. I don't have

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)

Hello, sorry if the question was asked a couple of times before but I couldn't find any useful hinds to this problem using google and the listman search-engine of the archive of this list. Somehow the ext3 filesystem on one of my machines died an after a reboot grub wouldn't come up again. What I did so far: fsck -y /dev/hda4 fsck 1.35 (28-Feb-2004) e2fsck 1.35 (28-Feb-2004)

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

Hi I am running a PC under Linux SuSE 7.2 with kernel 2.4.18, self compiled. I changed some days ago the partition of my second HD from ext2 to ext3 with the help of tune2fs -j /dev/hdb2 and everything was running OK. Today, I had a problem with a frozen display and I had to reboot the box cold. During the corresponding forced check I got the following messages: Quote --------- /dev/hdb2: reading