similar to: ext3 journal from windows

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

Are we likely to see patches to allow 16TB ext3 in the mainstream kernel any time soon? I am working with a storage box that has 16x750GB drives RAID5-ed together to create a potential 10.5TB of potential storage. But because ext3 is limited to 8TB I am forced to split into 2 smaller ext3 filesystems which is really cumbersome for my app. Any ideas anybody?

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

Hi! Is there a way to view ext3 filesystem's maintained journal (in a human-readable-format)? I ask, because i have had a server crash before and now i'm wondering if i might take a look at last things that my server did straight before crash. I guess clarifying log insertions might be lost before buffers were flushed to disk. Thx.

Hi, I am trying out ext3 with an external journal (on a battery backed RAM card). I use data=journal, and sync nfs writes go nice and fast :-) But.. I had to power cycle it (buggy VM.. grumble :-) and now I cannot get my filesystem back. It is only a test filesystem so I don't need the data. But I want this to work before I put real data on it. If I "fsck /dev/md1", it

Stephen et al, You may remember me raising the point that the new e2fsprogs (1.25 as I remember) griped about old journals not having all the appropriate fields zeroed. I've just discovered that the RH 7.2 installer produces journals (ie on partitions created as ext3 from within the installer) that flag these warnings with a modified 1.25 e2fsck (the mods being to clear the errors rather

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

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

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

SUMMARY We are getting many ``Free blocks count wrong for group'' errors when running e2fsck on a 245-GB ext3 filesystem. This is when the file system is cleanly unmounted on a relatively quiet system to do a resize. From reading other messages here, my suspicion is that this is because we have e2fsprogs 1.32. Questions: * Should we use e2fsck/e2fsprogs 1.36 and will that probably

Suppose I have the latest and greatest e2fsprogs. >From reading the docs I understand that 1) boot ext3, clean umount - you can remount ext3 or ext2 2) boot ext3, unclean umount - you can remount ext3 - you can e2fsck and remount ext2 Does this mean that normal linux init script e2fsck will do it, in case fstab says ext2? Or you should make sure to run e2fsck by hand with -f? 3) boot

Im intending use Ext3 file system in my web farm. Im using RedHat 6.2 (kernel 2.2.16-3) and Turbo Linux Cluster Server 6.0. I have NO SUCCESS in path my own kernel. I downloaded the following ext3 packages: ext3-0.0.2f.tar.gz (linux-2.2.16-3.kdb.diff , linux-2.2.16-3.ext3.diff ) e2fsprogs-1.20-0.WIP.i386.rpm e2fsprogs-1.20-0.WIP.src.rpm e2fsprogs-1.20-0ext3.i386.rpm

Hi, I'm about to roll out a whole bunch of Redhat Enterprise 4 workstations and have run into problems cloning from the original. Normally I would use ghost (v7.5) because it does a nice job when cloning to a different sized disk.Unfortunately it comes up with read error 29004. Looking around it seems that Symantec don't support Fedora Core 3 (with Ghost v.8 - don't know if v.9 works

For some time now I have been puzzled as to why certain portions of my system boot were quite slow -- but only after journal recoveries. I was fearing that there was some ugly interaction between the recovery and the use of the journal shortly afterward but alas that is not the case. So just in case anybody else is seeing this problem and decides to try to hunt it down, let me save you some

One of my servers appears to have some filesystem corruption. I'm running Red Hat 6.2 with kernel 2.2.19pre6 and ext3 0.5e. That server currently has e2fsprogs-1.20-WIP-0117 installed. Is it OK to upgrade to the latest e2fsprogs (i.e.: 1.22) prior to running the e2fsck on the filesystem? --Shawn

Hello, seems like the new default ext2/ext3 256 bytes inode size problem applies to extlinux. HPA, could you confirm it? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=491076 http://e2fsprogs.sourceforge.net/e2fsprogs-release.html E2fsprogs 1.40.5 (January 27, 2008) "Mke2fs will now create new filesystems with 256 byte inodes and the ext_attr feature flag by default. This allows for

I have an apple Xserve RAID attached to a Linux Box, serving one Raided LUN of 2500Gigs, it was functional until the box crashed. When I hard booted it, even though it mounted the FS, I've been unable to access it. Cd-ing to any of its directories gives "Input/Output error". The ls ?la on the FS shows "?" for every field with no permission information. The /var/log/messages

Hi, I'm using ext3 filesystems in embedded devices (storage is on 512Mb or 1Gb CF cards). A typical development cycle would see the filesystem created on the desktop PC running linux 2.4 (eg. RedHat 9). The CF card would be installed in the hardware and linux 2.4 (eg. Montavista Pro 3.1, on PPC) would boot from the CF. Recently I tried a linux 2.6 desktop (CentOS) for the same task and

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

Hello, I have a 1.3TB ext3 filesystem that has been in service for about 3 months. About 6 days ago the Emulex fibrechannel controller logged a SCSI error and the filesystem changed to RO. It appears that the filesystem instantly changes to RO and prevents the journal from working, therefore invalidating the filesystem. The filesystem was unmounted and a remount was attempted. The mount failed