similar to: fsck forced on every system crash

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

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'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

Hello. My box has been running flawlessly for months now, but in the last 2 days hasn't stayed up for more than 5 minutes. All this seemed to have started after I did a very very bad thing...... I ran the EXT2 to EXT3 conversion on my root filesystem. I used the "tune2fs -j /dev/sda1" to do the deed. After it completed the machine ran fine (the machine was up and serving when I

What is the correct procedure to fsck a ext3 partition? A system died during a 7.2 upgrade - /usr and /home were selected to convert to ext3 - and I did a fsck -t ext2 /device but the system still complains that the file system is/was not clean unmounted. TIA

Hi there, I'm running RH7.2 with ext3, and everything's been going great, except that my root filesystem won't mount due to some kind of corruption. When I try to mount, I get EXT3-fs: unsupported inode size: 61267 Yikes. Any suggestions? trying 'fsck -n -t ext3' suggests using an alternate superblock, but this doesn't change anything. Even a mechanism to

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 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?

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

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

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

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

I need to find out what the maximum file size in an ext2/3 file system. It appears from the definition of the ext2_inode structure that since the i_size field is a 32 bit integer that the file would be limited by that. Thanks, Jason

All -- I'm curious is if it safe or even wise to run the following command on a mounted filesystem, namely root (/)? tune2fs -j /dev/hda1 What about if someone goes into single user mode and runs this first? mount -o remount,ro / And then to enable it, runs this? mount -t ext2 -o remount,rw / I assume it is not safe to do so, but one user in my LUG assumes otherwise. Just curious,

I created on my 60Gb hdd (data=journal) journal with 16Mb size, i think it not enough. As it is possible to change size of 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

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

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

How can you know beforehand, without running fsck, that all inodes are used of a particular ext3 filesystem? Default systemtools use output from df, which shows only a 50% usage of the filesystem, and pretend nothing is wrong, while you really cant't move or copy a file to it. So I only found out when running fsck. This is my output from fsck (RH7.2, stock kernel, stock? ext3): root# fsck