similar to: ext3 corruption

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

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

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

hi all, I intend to write a snapshot module for Ext2/3 file-systems. For that i need to make sure that FS is in consistent state before taking snapshot. For ex. in case of UFS, the superblock has a fs_clean flag which is set to be FSSTABLE to tell that its in consistent state. (otherwise its set to FSACTIVE) I m not able to find any such information for Ext2/Ext3. (The

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

I decided to start using ext3. My kernel 2.4.15p9. I downloaded and build util-linux-2.11m and e2fsprogs 1.25. I compiled ext3 in the kernel. I started converting my filesystems and thing went ok for the first few. I then started getting the following on each additional filesystem. [root@joker /root]# tune2fs -j /dev/hdc4 tune2fs 1.25 (20-Sep-2001) Creating journal inode: done This filesystem

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

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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Searching in the ext3 filesystem mailing list I have seen that there is an indexed directory extension for it. Is this extension stable code ? Has anyone test it ? How may I obtain and install it ? Is it available in any of the last kernel releases ? Greetings. - --- Carles Xavier Munyoz Baldó carles@descom.es Descom Consulting Telf: +34

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.

Hi, I have an ext3 file system on top of LVM and i use journaled mode. I would like to make a snapshot of my filesystem while the application is running in order to backup on another physical storage. For that i have to create an LVM snapshot and then to mount it in read-only for copying the content. This is not possible as far as ext3 needs to do a log replay at mount time ( AFAIK). I would

Hello folks, I had an ext3 filesystem mounted as the root of a Linux MOO server. Unfortunately, the filesystem was on one of the infamous DTLA-3070xx drives - and the drive decided to fail at the worst moment it possibly could, trashing the filesystem fairly well. The situation is as follows: I used dd_rescue to create an image of what is left of the filesystem, but I ended up with some 65MB

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

Hello: We trying to configure one machine (Compaq Proliant ML760) with 8 disks (72GB each disk) with RAID. We are thinking to use ext3 and LVM in RedHat 7.2 for manage one filesystem with 500GB. This filesystems have to store near off 5.000.000 of files. Is this possible? Could I resize the filesystems/volume to 1TB? what are the ext3 and LVM limits? someone have tested sismilar environment? I

I am having some trouble with an ext3 partition, getting the following error when i go to fsck the partition: fsck.ext3: Bad mgic number in superblock while opening /dev/sda2 I tried the -b 8193 option, to no avail. Can anyone out there help me recover this partition?? ---- Michael B. Weiner Senior Systems Administrator/WebOps AmericanGreetings.com Three American Road, Cleveland, OH 44144

Hello, If I made a cpio backup of an ext3 fs. Then created a new fs and restored everything including the .journal file, What would happen?? Regards John

Hi! I would like to know how well ext3/(ext2) will tolerate underlaying errors (I am planning to use loop-AES backed ext3 fs). So if there is 1024 bytes corruption of data what will be the worst case: - If this data belongs to some file, this part of data(file) has been lost? - If this data belongs to superblock, I have to repair ext3 and use another superblock? - If this data belongs to

Hi Andrew, The patch below addresses the problem we were talking about earlier where ext3_writepage ends up accessing the inode after the page lock has been dropped (and hence at a point where it is possible for the inode to have been reclaimed.) Tested minimally (it builds and boots.) It makes ext3_journal_stop take an sb, not an inode, as its final parameter. It also sets

Hello, I had something interesting happen on a RH8 ext3 system I setup.I am at a loss to understand what happened. Info: This system has two IDE disks, partitioned identically, and the largest partition on each (/dev/hda3 and /dev/hdb3, 96GB each) was mirrored in a linux software RAID-1 configuration. It was running fine for many months. Then I updated the kernel and needed to reboot accordingly.