similar to: Creating an ext3 device

We are having problems remounting an ext3 filesystem using an external journal device. The filesystem in question was working fine until the server was rebooted. This is what we see on dmesg when trying to mount: EXT3: failed to claim external journal device. The external journal lives on a LVM2 logical volume and it seems to be accessible ( we can dumpe2fs and see filesystem information).

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

I am new to ext3 + external journal. Is there any howto I can look at? this is what I understand 1. mke2fs -O journal_dev /dev/md5 2. mke2fs -J device=/dev/md5 /dev/md0 3. mount /dev/md0 / -t ext3 ( hmm.. what do I need to put on fstab?? ) /dev/md5 is a two drive RAID 1 partition /dev/md0 is a 4 drive RAID 5 partition. questions: 1. I am running RedHat 9.0. what extra software I need to

The documentation says ... if you want to install it manually, you can do so by using the regapi tool to be found in the programs/regapi/ directory in Wine source. So if you have installed WINE from an rpm, how do you install the registry? Thanks, SJR -------------- next part -------------- An HTML attachment was scrubbed... URL:

----- Forwarded message from Steven Rubenstein <SJR@ElectricSpectric.com> ----- yes the apps matters because some other users might have run into the same problem. Have you check the app database on the codeweavers website ? I never try that app myself so I forwaded the answer to the mailing list ... I'll do a little research on it ;) See you Rico > From: Steven Rubenstein

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

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 noticed something unusual today. If I "du" a small file (couple of bytes) in CentOS 5, it tells me the file is using 8kb, while I was expecting 4kb which is the block size I'm using. I tried this on several CentOS 5 machines, both x86_64 and i386: $ echo test >test.txt $ ls -l test.txt -rw-rw-r-- 1 filbranden filbranden 5 Mar 11 17:24 test.txt $ du -h test.txt 8.0K

The windose application I am trying to run bombs with the following error box. unknown has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created. OK I can't find the alleged "error log." Any ideas where it may be? Thanks, SJr

Hi, I made an ext3 filesystem with 8kB block size: # mkfs.ext3 -T largefile -v -b 8192 /dev/md0 Warning: blocksize 8192 not usable on most systems. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=8192 (log=3) Fragment size=8192 (log=3) 148480 inodes, 18940704 blocks 947035 blocks (5.00%) reserved for the super user First data block=0 290 block groups 65528 blocks per group,

I've been thinking recently that we should re-enable DIR_INDEX in mke2fs by default. When it first came out, we had done this and were bitten by a few bugs in the code. However, this code has been in heavy use for several thousand filesystem years in Lustre, if not elsewhere, and I'm inclined to think it is pretty safe these days. Likewise, RHEL/FC have had RESIZE_INODE as a standard

--- scripts/ovirt-config-boot | 13 +++++- scripts/ovirt-config-storage | 111 ++++++++++++++++++++++++------------------ 2 files changed, 75 insertions(+), 49 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index d545878..8cc127b 100755 --- a/scripts/ovirt-config-boot +++ b/scripts/ovirt-config-boot @@ -29,6 +29,12 @@ ovirt_boot_setup() { local disk2

--- scripts/ovirt-config-boot | 13 +++++++- scripts/ovirt-config-storage | 73 +++++++++++++++++++++++++---------------- 2 files changed, 56 insertions(+), 30 deletions(-) diff --git a/scripts/ovirt-config-boot b/scripts/ovirt-config-boot index d545878..8cc127b 100755 --- a/scripts/ovirt-config-boot +++ b/scripts/ovirt-config-boot @@ -29,6 +29,12 @@ ovirt_boot_setup() { local disk2

On 2013-08-29, at 7:48 PM, Richards, Paul Franklin wrote: > Strange behavior with fsck.ext3: how to remove a long orphaned inode list? > > After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting

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

Wow, it takes a really long time to make a 2TB ext2fs. Are there better-than-default options that could be used for a large filesystem? mke2fs 1.34 (25-Jul-2003) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 244203520 inodes, 488382016 blocks 24419100 blocks (5.00%) reserved for the super user First data block=0 14905 block groups 32768 blocks per group,

Hi everyone, I've been running Redhat 7.2 (new install) for about 2 weeks now without any problems, but today I was not so lucky. My system hung while I was trying to configure the kernel-source RPM using 'xconfig'. After rebooting the system, it seems that my whole ext3 file system is corrupted. I get the message: Mounting root filesystem EXT3-fs: ide0(3,3):couldn't mount

I created a filesystem as follows: mke2fs -j -O dir_index -O sparse_super -T largefile /dev/drbd/6 Here's the the output from df Filesystem Size Used Avail Use% /dev/drbd/6 475G 33M 452G 1% It seems that ext3 has taken 23 GB, which is about 5% of the total disk size, for itself. Is that right? If that is, indeed, the case, why does df just list 33M as being

This lays the groundwork for setting Root and RootBackup onto individual partitions for multiple disk installations in the future. Install, removal, upgrade testing has been performed and all seems to work at this point. --- scripts/ovirt-config-boot | 15 ++++++++------- scripts/ovirt-config-storage | 28 +++++++++++++++------------- scripts/ovirt-config-uninstall | 2 ++

i posted on rhel list about proper creating of 6tb ext3 filesystem and tuning here.......http://www.redhat.com/archives/nahant-list/2006-November/msg00239.html i am reading lots of ext3 links like...... http://www.redhat.com/support/wpapers/redhat/ext3/ http://lists.centos.org/pipermail/centos/2005-September/052533.html http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html ............but