similar to: Does ext3 file system use a '.journal' file?

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I created all my ext3 partitions a while back, so the journal.dat file is visable. I'd like to remove them and use the new tune2fs functionality. Can I just mount the drives as ext2, rm journal.dat, tune2fs -j /dev/hd?? and then remount as ext3? Or am I missing something? thanks! - -- Douglas J. Hunley (Linux User #174778)

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, After mounting -t ext2 an ext3 partition, working with, do I have to recreate .journal when I remount the partition as ext3 ? Thanks ! Liu

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 Ted and all, I have a couple of questions near the end of this message, but first I have to describe my problem in some detail. The power failure on Thursday did something evil to my ext3 file system (box running RH9+patches, ext3, /dev/md0, raid5 driver, 400GB f/s using 3x200GB IDE drives and one hot-spare). The f/s got corrupt badly and the symptoms are very similar to what Eddy described

Forgive my novice question, but I am a new student of Linux working on presenting the ext3 journaling filesystem to my class. I seek any advice on how to visibly demonstrate (including a purposeful crash of a Linux box) the benefits of ext3 over ext2. I am not worthy to lick the bootstraps of this group, but I beg for any help! The problem I am having extends to even locating the .journal file

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

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

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

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

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 Everyone, I have a server which has a raid array on /dev/sdb. After a crash I tried to mount the array and it failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or other error dmesg reports: EXT3-fs: invalid journal inode. I tried to run e2fsck and it failed (The output can be seen below). If anyone has any suggestions on how I can restore

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

Hello, I'm using RedHat 7.2. I needed to mount my root fs to QNX 6.1. QNX supports ext2 only but I tried that anyway. It was mounted wrong (e.g. the /root directory was symbolic link to non-existing file). When I wanted to boot from the RedHat again, these errors occured: ... Mounting root filesystem EXT3: failed to open journal device unknown-block(0,0):-19 mount: error 22 mounting ext3

Hi In our office environment few servers mostly database servers and yesterday it happened for one application server(first time) the partion is getting "read only". I was checking the archives, found may be similar kind of issues in the 2007-July archives. But how it has been solved if someone describes me that will be really helpful. In our case, just at the problem started found

Hi I have a Firewire connected Micronet 1.5TB RAID with a single large ext3 filesystem on one partition on a dual Xeon system. I am checking out from an extremely large cvs repository (don't ask) to this drive over the course of many days, and intermittently I get bad blocks and the filesystem goes read-only. This is not related to any power failure or anything similar. The RAID is currently

Hi, I've just recently noticed that the ext3 projects is being actiavely maintained (again?). And looking at the new pages for 2.4.x it really made me interested. But I've got a few small questions I'd like to clarify before I start to use it. 1) Tune2fs and mke2fs talk about a "default journal size" that is depending on the partition size but don't give