similar to: fsck

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

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

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

Hi all, I seem to be having a problem whereby my ext3 filesystem forces a full fsck on every hard system crash. This takes over 20 minutes on my 40GB drive and is driving me nuts. I've verified that the partition is, in fact, being mounted as ext3 and have tried removing ^has_journal and re-creating the journal file but nothing has worked. I'm running RH7.2... Any ideas would be much

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?

So you know, I don't know too much about file systems. Here is what I did: I have two linux boxes. the first box had many hardrives in it, but needed to be used in other ways. So I took 4 harddrives out of it and placed it in the other Linux box. I thought it would be able to read these right away. (maybe this was my mistake?) I could mount all of the drives in there. three of my

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

Something bad must have happened when I first ran e2fstune on my root file system. Now I cannot mount it ext3 and when I try to run tune2fs -j on it, I get this error message: permission denied while trying to create journal file There is a .journal file in /: [root@monster log]# ls -l /.journal -rw------- 1 root root 33554432 Sep 29 10:21 /.journal But dumpe2fs

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 subject about says it all. should this only be done once per device or periodically? thanks! - -- Douglas J Hunley (doug at hunley.homeip.net) - Linux User #174778 Admin: Linux StepByStep - http://www.linux-sxs.org and http://jobs.linux-sxs.org Illiterate? Write for help! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux)

In a fit of irony, while preparing to burn a CDROM with some software I've been writing for about six months, I did a rm *>o instead of rm *.o on an ext3 filesystem. And I'm well aware that under normal circumstance you can't undelete, especially a ext3 filesystem. However, I need to at least *try* to recover this. I've built lde (linux disk editor) and if I can isolate a

Hello all... I have RH7.2, with ext3 filesystem. My problem is: It is not possible to write or delete and change owner or permission in /usr/share/locale/ga/LC_MESSAGES Also, I can´t write/delete files in this directory, and also in ../locale/ga/ Therefore I cannot upgrade to RH8.0, because installer needs to write to this directory, but he cannot. Owner of ../ga/LC_MESSAGES is root, group

When I first installed ext3, it worked as expected. After a crash, journals would be played, and no fsck. Now, every crash causes an fsck, just like it were a regular ext2, even though / has a journal and is being mounted as ext3. Some fs info for / Filesystem features: has_journal filetype sparse_super Filesystem state: not clean Errors behavior: Continue Some fs info for

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

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.

Hi, I am getting the following errors on /boot partition on a production server running 2.4.18 kernel. ------------- Aug 10 00:19:37 kernel: EXT3-fs error (device sd(8,1)): ext3_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0 ------------- /boot is not readable at all and attempt to do an ls will return the same error.

Hello, I'd like to read superblock's information on Redhat 7.3, but I don't know how to do it. For example, Input : "/dev/sdj2" Output : ext2_super_block struct's s_wtime (I saw it at "/usr/include/ext2fs/ext2_fs.h") Input : "/dev/sdj1" Output : ext3_super_block struct's s_wtime (I saw it at

VFS: brelse: Trying to free free buffer buffer layer error at fs/buffer.c:1182 Pass this trace through ksymoops for reporting Call Trace: [<c01468f0>] [<c0146aa9>] [<c0146b57>] [<c0146b84>] [<c0175a17>] [<c023cbfa>] [<c023d2f1>] [<c0175c90>] [<c01728e9>] [<c01ad7d6>] [<c014d215>] [<c0154c68>] [<c0154f79>]

hello: I have been reviewin my message slog and have found the following message: Dec 19 06:27:28 server02 kernel: EXT3-fs error (device sd(8,7)) in ext3_new_inode: error 28 What is error 28 and should I be worried about it? Ray Turcotte

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