similar to: How to change .journal size

Hello Is it possible to externalize the journal of an already existing (journal inside) ext3 FS ? Here's what I did to create a new FS with external journal for /dev/emcpowerl2 on /dev/emcpowerl2 mke2fs -O journal_dev /dev/sda10 mke2fs -J device=/dev/sda10 /dev/emcpowerl2 it works perfectly , but can I do the same whitout reformating the original FS; /dev/emcpowerl1 which is in

Hello On root Partition is .journal visible . On all other Partitions is invisible. At which way I can move it manually to a hiden inode? I have delete with chattr -i /.journal rm -f /.journal and installed ext3 with tune2fs -j /dev/hdb1 And /.journal is again visible! -- MfG / With best Regards Rusmir Duško Registered Linux user: #130654 http://counter.li.org

Hopefully, someone can tell me if this is OK. I recently had a problem with my system and had to do a complete restore. Fortunately, I had made a full backup just the day before. My filesystems are Ext3 (why else would I be posting this here?). :) Anyway, when I originally changed my filesystems from Ext2 to Ext3, I did while they were still mounted. As a result, the journal file was visible.

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

I have been playing with external journals some more and thought I should share some experiences. I am running 2.4.16 with the ext3 patches from Andrew Morton and e2fsprogs 1.25 I have an ext3fs filesystem on an 8 drive RAID5 array and place the journal on a partition of the mirrored pair that I boot off (all drives SCSI). I have tried pulling the power cable and seeing what happens. I finally

Hi, I installed a new kernel with ext3 support and I want to convert my ext2 partitions to ext3. I used to do tune2fs -j /dev/hdX I did this and it works. Now I converted one of my partitions, the other are system ones (/home, /boot, /) Do I have to do this command when these partitions umounted (the other was)? How do I do that, I cannot start this program if there are not mounted. Or do

Hi all, I'm trying to resize a journal on my root filesystem. This is Ext3, kernel 2.4.19, latest e2fsprogs + htree patch. I've remounted my root filesystem as ext2, but still when I 'tune2fs -O ^has_journal' I get ---- The has_journal flag may only be cleared when the filesystem is unmounted or mounted read-only. ---- So, how can I increase the size of the journal? I

My UPS failed and my server took an 'unscheduled outage' a few weeks ago. The only casualty appears to be a volume I used for backup. I usually maintain data on multiple hard disks, but in this case I errantly had some data (of marginal value) on this file system. At this point, the data is not worth enough for me to send the drive out for data recovery, but it's worth enough to

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

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 was running few tests on the Ext3 filesystem having an external journal; basically trying to check recovery in crash scenarios. I started with simple scripts doing some filesystem operations on the ext3 partition and crashed the system with a direct poweroff. On reboot, I also corrupted the journal device by "dd"ing it out with blocks of zeroes. Now, when I try to mount the

Greetings, I recently cpio-ed some user directories onto a new ext3 partion. After putting this file server's partition into production, I noticed a .journal file in the root directory of the partition dated well before the creation of this partition. I think this .journal file was copied over from the old filesystem and I am concerned that I over-wrote this current filesystem's

On 6/27/13 3:57 AM, Folkert van Heusden wrote: > Eric, Andreas, > >>>> I have a system with an ext4 filesystem with its journal on an other >>>> device (an SSD). >>>> Now this SSD dropped of the sata bus so the filesystem went r/o. >>>> I would like to remove the journal but it says it can't because >>>> needs_check is set.

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

On 6/25/13 3:13 AM, Folkert van Heusden wrote: > Hi, > > I have a system with an ext4 filesystem with its journal on an other > device (an SSD). > Now this SSD dropped of the sata bus so the filesystem went r/o. > I would like to remove the journal but it says it can't because > needs_check is set. What does it actually say? there is no needs_check flag AFAIK. > I

On 2013-06-26, at 9:38 AM, Eric Sandeen wrote: > On 6/25/13 3:13 AM, Folkert van Heusden wrote: >> >> I have a system with an ext4 filesystem with its journal on an other >> device (an SSD). >> Now this SSD dropped of the sata bus so the filesystem went r/o. >> I would like to remove the journal but it says it can't because >> needs_check is set. >

Hi, I have a system with an ext4 filesystem with its journal on an other device (an SSD). Now this SSD dropped of the sata bus so the filesystem went r/o. I would like to remove the journal but it says it can't because needs_check is set. I can't run fsck because the journal is not reachable. Is there any way to solve this? I understand I lost any pending changes in the journal. regards

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