similar to: ext3 convert

I created on my 60Gb hdd (data=journal) journal with 16Mb size, i think it not enough. As it is possible to change size of journal ?

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

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! I would like to know how well ext3/(ext2) will tolerate underlaying errors (I am planning to use loop-AES backed ext3 fs). So if there is 1024 bytes corruption of data what will be the worst case: - If this data belongs to some file, this part of data(file) has been lost? - If this data belongs to superblock, I have to repair ext3 and use another superblock? - If this data belongs to

After a (hardware) crash yesterday, I was unable to boot up due to unrecoverable ide errors (according to the printk()s) when accessing the root filesystem's journal for recovery. Unable to recover, I tried deleting the has_journal option, but that was disallowed given that the needs_recovery flag was set. I saw no way to unset that flag. Unable to access the backups (they were on a fw

HI, I have just upgraded my Linux 7.1 to 7.2 (so I can have ext3 available for use). My question is how do I format a partition for an ext3 file system? We can normally run the command 'mkfs' or 'mkfs.ext2' to format an ext2 file system, or 'mkfs.xfs' for an xfs file system. I was looking for some utilily like 'mkfs.ext3' or similar. Question: Does ext3 support

Our Invoice posting routine (intensive harddrive io) freezes every few seconds to flush the cache. Reading this: https://listman.redhat.com/archives/ext3-users/2002-November/msg00070.html I decided to try: # elvtune -r 2048 -w 131072 /dev/sda # echo "90 500 0 0 600000 600000 95 20 0" >/proc/sys/vm/bdflush # run_post_routine # elvtune -r 128 -w 512 /dev/sda # echo "30 500 0 0

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

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: I have been reviewin my message slog and have found the following message: Dec 19 06:27:28 server02 kernel: EXT3-fs error (device sd(8,7)) in ext3_new_inode: error 28 What is error 28 and should I be worried about it? Ray Turcotte

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,

I am in the odd situation of needing to revert my root partition back to ext2 so that it may be resized. I prefer to use Partition Magic at the moment and it can only work with partitions of ext2, not ext3. I believe that the documentation for ext3 exists at the main web site, http://www.uow.edu.au/~andrewm/linux/ext3/. That is my next destination but as the answer may not exist there, I

Apologies for the newbie question: I have a (stock) 2.4.20 build (*not* -ac), and I'm trying to work with large ext3 directories. By large, I mean 160,000 files per directory. (Yes, I know it would be better in nested directories but such is life). I feel htree would benefit me. Close reading of the 2.4 changelog suggests that htree isn't in there - only a patch to prevent non-htree

Recently I've encountered a problem, and now I would preciate any help about being able to undelete files. My /var filestructured is mounted at /dev/hdc1 Part of my /etc/mtab looks like this: /dev/hdc1 /var ext3 rw 0 0 I'm using the e2fsprogs-1.23-2 package currently installed with Redhat 7.2 So, could anyone give me a hint of how things could be done to find deleted inodes? I've

Hello. My box has been running flawlessly for months now, but in the last 2 days hasn't stayed up for more than 5 minutes. All this seemed to have started after I did a very very bad thing...... I ran the EXT2 to EXT3 conversion on my root filesystem. I used the "tune2fs -j /dev/sda1" to do the deed. After it completed the machine ran fine (the machine was up and serving when I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, just wondering... if i upgrade my kernel + ext3 patch, do i have to recreate the journal? if so (or if not) how do i recreate it? i tried to delete the .journal, reboot and mounting everything as ext2 and do a tune2fs -j /dev/hdxx but it say "The filesystem already has a journal." Thanks, Mark -----BEGIN PGP

Is there an ext3 version of this? Something in ext3 makes e2undel unable to recover unlinked inodes. I just deleted something, umounted the drive to preserve the state. I used e2undel to look for stuff to recover and it found 0 deleted files. I have been using e2undel for quite a while with great success and I know hwo to use it, but it seems to not be able to recover stuff on ext3. Is there

Hello, I'd like to read superblock's information on Redhat 7.3, but I don't know how to do it. For example, Input : "/dev/sdj2" Output : ext2_super_block struct's s_wtime (I saw it at "/usr/include/ext2fs/ext2_fs.h") Input : "/dev/sdj1" Output : ext3_super_block struct's s_wtime (I saw it at