similar to: 2.4 recovery bug

hi, is this rpms differ from redhat's rawhide 2.4.5 kernel which seems to contain ext3. so my question that your rpm contain different ext3 than rh's rpm? or I can simple use rh's rawhide rpms? thanks. yours. ps. please reply to my private address to since I'm not on the list. thanks. > Hi, > > Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.

I just came back after being out for the evening. Apparently there was a power failure long enough to discharge the UPS completely on my Linux box. After powering back up, I received notice that the / filesystem needed "manual fsck"ing. I booted off CD and attempted to fsck. Unfortunately, everything I've tried has proved futile and I'm _desperate_ for some help. I've

Hello, We have run and stopped by chance command "fsck -y" on one of our raid disks (with ext3 file system). After that we have found that SOME files disappeared (they are not seen in the directories where they have been before). The data are extremely important and contain a lot of programs, scripts for some data analysis and very hard to recover by hands. I have run ''fsck

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

I have a damaged Ext3 filesystem which fsck has not been able to recover. If I try to mount it, I get a message like this in dmesg: EXT3-fs error (device sda1): ext3_free_blocks_sb: bit already cleared for block 2370866 If I try fsck on it, I get a series of messages like this: Inode bitmap for group 0 is not in group. (block 0) Relocate<y>? Up to group 95. Some say

I have many systems running current ext3 code. Some of them have hardware problems that lead to frequent reboots, and the journal recovery has worked excellently. However, on the periodic forced fsck on supposedly recovered and clean filesystems, I've many times seen fsck report that i_blocks is too large in one or more inodes. I suspect that i_blocks is somehow escaping proper restoration

Rebooting to try 2.4.7-ac4, I had Xfree86 crash on exit and hang the machine (it does that once a month or so; this notebook gets booted quite often). After fscking the root and another ext2 partition, the system got to the big ext3 partition and just went dead. No message, no disk activity, no keyboard response. I powered down and rebooted 2.4.7-ac3 patched with ext3-2.4-0.9.5-247ac3, and that

I've been running RH 72 on my Dell at work. Since I use more than one system and I test things, I forgot that I had the root partition as ext3. That machine has two kernels on it. One is the stock 2.4.7 RH 72 and the other is the new 2.4.17 that I compiled last week. This morning I logged in and typed startx. The kernel responed by coughing up a lung and segfaulted. Couldn't run any

Can some one help me with a ext3 file sys problem?? I have a raid 0 array that was not shut down properly due to bad contacts in a removable drive bay. It consists of two 80Gb drives. I can create /dev/md0 ok. but if fails during mount. When I run: fsck -n /dev/md0 it reports the following: fsck 1.32 e2fsck 1.32 SuperBlock has a bad ext3 journal (inode 8) clear? no fsck.ext2: illegal inode

This is a 2.2.19 machine with ext3-0.0.7a and quota support running. The symptoms are a particular NFS export hangs (for linux clients but not Solaris clients?) the local filesystem gives the following: EXT3-fs warning (device sd(8,49)): ext3_free_blocks: bit already cleared for block 2213 EXT3-fs error (device sd(8,49)): ext3_free_blocks: Freeing blocks not in datazone - block = 1563120916,

Hello friends, I am trying to learn recovering of file using debugfs. But even though i delete the file and run lsdel in debugfs it always gives me 0 deleted nodes found. Where am i making mistake?. [root at windce7 linux-2.4.32]# fdisk -l Disk /dev/hda: 40.0 GB, 40016019456 bytes 255 heads, 63 sectors/track, 4865 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot

Our main NFS-server, running Debian Potato, died this morning whilst under quite heavy load - due to a runaway perl-script forking of some 200 instances of "/bin/cp" (the load was ~ 50). The server is running 2.2.19pre14 with ext3-0.0.6b. The server is running kernel-nfs. Assertion failure in journal_dirty_metadata() at transaction.c line 796: "bh->b_next_transaction ==

Hi, I'm hoping that someone here may be able to help me ;). I have a filesystem that gets checked everytime my machine boots, (as this is a desktop system this is quite often, and unfortunately takes a while). I decided to attempt to fix it, and booted both a knoppix (3.1) CD and a Gentoo 1.4 CD to attempt to run fsck on the partition when I noticed that running fsck returns the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Please CC me on answers, I'm not subscribed] Hi everyone, I have got a hard disk which was damaged by a fall and would like to recover a few files from that. (There is a backup for most of the data, but a handful of recent files are missing. These are important enough to spend some time on them, but not for paying a professional data recovery

On Sun, Jun 01, 2014 at 07:43:12PM -0700, Keith Keller wrote: > > That's clearly a spurious error, so I checked dmesg: > > [159891.225762] EXT4-fs (dm-0): get root inode failed > [159891.227436] EXT4-fs (dm-0): mount failed The "get root inode failed" is rather unfortunate. Try running "debugfs /dev/dm0" and then use the "stat /" command. You

---------- Forwarded Message ---------- Subject: ext3 for 2.4 Date: Thu, 17 May 2001 21:20:38 +1000 From: Andrew Morton <andrewm@uow.edu.au> To: ext2-devel@lists.sourceforge.net, "Peter J. Braam" <braam@mountainviewdata.com>, Andreas Dilger <adilger@turbolinux.com>, "Stephen C. Tweedie" <sct@redhat.com> Cc: linux-fsdevel@vger.kernel.org Summary:

In the current recovery procedure, recovering node recovers orphans from the slot it is holding and the slots that dead nodes were holding. Other online nodes recover orphans from their slots. But orphans in offline slots are left un-recovered. This patch queues recovery_completion for offline slots. Signed-off-by: Srinivas Eeda <srinivas.eeda at oracle.com> --- fs/ocfs2/journal.c | 21

I have been making off site backups of my CentOS Linux servers using rsync. One of my hosting companies has suddenly gone out of business and I am unable to access the server that I was renting at that location, however, I have a complete system backup on another Linux server at a different location. My question is: Is it possible for me to load that rsync backup to another computer system that

On Sun, Jun 01, 2014 at 11:24:51PM -0400, Theodore Ts'o wrote: > > The "get root inode failed" is rather unfortunate. Heh, I like your understatement. :) I think this helps answer part of my questions in my second email: I should probably try to preserve changes from last backup before getting too deep into a tricky e2fsck. At one point the fs was still mountable, so I

Hi, all, I "found" a big bug either related with Linux Ext3 file system or "bin/ls" command. The problem is: File system is no more than 220GB, but "/bin/ls" reports holding >370GB data! The system is Redhat 8.0, with a Generic Kernel 2.4.20. Any suggestions are greately appreciated. more information can be available upon requests. The following is the