Displaying 20 results from an estimated 20000 matches similar to: "visibility of ".journal" file"
2001 Nov 02
3
Ext3 and external journals...
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
2001 Aug 14
8
Redhat Roswell
Hi all
i installed Redhat beta Roswell, then i updated to Kernel 2.4.8
patched him and installed the newest util-linux + e2fprogs without any
custoumized Options. Bootloader is Grub. Now when i boot he says mount -O or -0
is an invalid Option. tune2fs -j /dev/hdXX says "The filesystem already has a journal"
lsmod says that no jbd or ext3 Modules is loadet but i have pachted the Kernel
2001 Sep 25
2
not mounting ext3, 2.4.10
Hi,
I just attempted to convert my only partition, /, to ext3. I downloaded
the patch and compiled the kernel with ext3 support built-in, along with
the JBD Debugging support. Compiled the kernel and rebooted, everything
was fine.
Did a tune2fs -j /dev/hda2 on the partition in single-user mode, with
e2fsprogs 1.24a. It complained about not having enough space, or something
like that, (I have
2001 Dec 27
2
Visible /.journal
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
2006 Jan 25
1
EXT3: failed to claim external journal 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).
2001 Oct 23
3
Recreate journal after switch between ext2/ext3 ?
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
2002 May 01
1
Existance of .journal file
Hi,
please take my apologies if this is a FAQ but I couldn't find it
anywhere.
I do run all my machines on ext3 for quite some time. Now, by accident,
I found out that some partitions have a visible .journal file while
others do not. In fact on the two machines I checked .journal was
visible in / but not in any other directory that is a mount point for an
ext3 partition. I even tried
2001 Dec 04
2
journal file exists but feature missing
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
2001 Aug 19
1
Question About Relocating Journal on Other Device
Hi. I'm using e2fsprogs 1.23 on a Roswell system with a patched 2.4.7
kernel (using patch ext3-2.4-0.9.5-247) and am trying to create an ext3
filesystem whose journal is located on another device. The incantation I'm
trying is:
mke2fs -j -J device=/dev/hdc2 /dev/hdc3
I keep getting an error along the lines of "mke2fs: Journal superblock not
found". I've tried creating
2001 Jul 29
1
My fault (not ext3's!) and kernel panic on 2.4.7 .
Hello all.
I was playing with tune2fs to see how large the .journal file should
be on a 17G partition with 512M ram (it's 32M, by the way).
I am using plain 2.4.7 with ext3-2.4-0.9.4-247,
compiled with gcc-2.96-85 on a RH7.1 distribution with the relevant
changes, i.e. e2fsprogs-1.22-1, mount-2.11g-4 and
util-linux-2.11f-3 taken from rawhide.
I don't have any ext3 statement in /etc/fstab,
2001 Oct 12
3
ext3 mounted fs still needs fscking after crash
Hi there,
I'm new to ext3, so I hope you won't find my question to be stupid. I also
hope this isn't the 1,000,000th time someone posts it.
My problem is the following: I converted my ext2 systems to ext3 using
tune2fs -j /dev/sda2 (or 5 for my /home, 2 is my root)
Then I modified fstab and put ext3 for each. After a reboot, the mount
command says they are mounted as ext3.
But when I
2004 Apr 21
2
Separate common journal device
Hi,
Is it possible to use a separate journal device (one on a separate
drive or a partition) shared among more than 1 Ext3 file systems ?
I appreciate any inputs.
thanks,
Vijayan
2007 Jan 24
1
ext3 journal from windows
hai
is there any way to view the contents of ext3 journal form windows?
regards
______________________________________
Scanned and protected by Email scanner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/ext3-users/attachments/20070124/02f1d0a5/attachment.htm>
2002 Feb 27
2
external journal device
I'm trying to setup an external journal device, but it won't mount as
ext3. I can only mount it as ext2. Everything seems happy when I run the
commands. It will work when I don't use the external device. This is on
RH7.2, linux-2.4.18-rc2.
[root@dhcp4 root]# mke2fs -O journal_dev /dev/hdb5
[root@dhcp4 root]# mke2fs -j -J device=/dev/hdb5 /dev/hdb6
[root@dhcp4 root]# mount -t ext3
2001 Dec 11
1
More external journal woes.
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
2006 Sep 26
3
EXT3-fs: invalid journal inode.
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
2001 Mar 20
3
Interesting interaction between journal recovery and slow boots
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
2002 Oct 04
4
Resize journal on root filesystem
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
2001 Aug 18
2
ext3->ext2->ext3 and unclean umount
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
2001 Jan 18
2
root fs type in fstab
Hello all.
I am currently using ext3 0.0.5d with great success. I am a bit
conflicted about what to tell the system regarding my root filesystem
however. I have my root filesystem configured and working as an ext3
filesystem, but it is/was not without some fraught.
Using RedHat 7.0, if you simply create your journal on the root file-
system, figure out it's inode number, issue a
lilo -R