similar to: How To Fix Duplication Block Error?

Hi there, I am very new in linux and met the filesystem problem as described in the following, I tried to use 'fsck' and tried to find some support documents but failed. Your hints and helps are very appreciated. Millions of thanks, Annie The error message is (sorry for it's length, I just want to make it clear) ====================================================================

Hey all, Had a power failure and subsequent ext3 disk corruptions. Attempting to fix, but not working. Its a 120 gig IDE disk, 3 partitions. /boot, /, and swap. Basically can't boot up since the box can't get to the system files in /usr/ or anything. So I'm booting off of a FC2 disk 1 in recovery mode and trying to fix the filesystem with e2fsck The boot partition cleaned up

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

Hello. We have, over the last few months, lost ext3 filesystems three times. The whole filesystem left unusable. nfs-server:~# mount /dev/rd/c0d1p1 /mnt -t ext3 mount: wrong fs type, bad option, bad superblock on /dev/rd/c0d1p1, or too many mounted file systems (in dmesg) EXT3-fs: journal inode is deleted. EXT3-fs: get root inode failed nfs-server:~# fsck /dev/rd/c0d1p1 Parallelizing

Hi I am running a PC under Linux SuSE 7.2 with kernel 2.4.18, self compiled. I changed some days ago the partition of my second HD from ext2 to ext3 with the help of tune2fs -j /dev/hdb2 and everything was running OK. Today, I had a problem with a frozen display and I had to reboot the box cold. During the corresponding forced check I got the following messages: Quote --------- /dev/hdb2: reading

I subscribed this morning but have no traffic. Sometimes no traffic is a good thing. Since I've gone to ext3 on my 2.4.5 kernel, the only time I ever had problems was when the filesystems were not unmounted cleanly and the journal was lost. About 60 minutes of searching and reading and I found out how to recreate the journal. So far, so pleased with ext3fs. --

Getting this oops on one of our production servers pretty much hangs the server. Do we have a corrupted Journal? how would ewe rebuild it? Any idea how to recover from it? Assertion failure in journal_bmap() at journal.c:636: "ret != 0" invalid operand: 0000 CPU: 0 EIP: 0010:[journal_bmap+70/96] Not tainted EIP: 0010:[<c016b646>] Not tainted EFLAGS: 00010282

Hi - We have an ext3 file system which is 3.5TB in size (on top of lvm). Free are 172049011 out of 854473728 4096K blocks, and 396540654 out of 427245568 inodes. This is using Scientific Linux 4.4 (a RHEL clone). The filesystem consists of multiple backups created with rsync using --link-dest, which hard links files which haven't been modified to the previous copy. There are several hundred

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, simple question: how can I execute a "fsck.ocfs2 /dev/sdf"? All I get is - ---snip--- myhost:~ # fsck.ocfs2 /dev/sdf fsck.ocfs2 1.4.3 Checking OCFS2 filesystem in /dev/sdf: Label: SAP01 UUID: 5969C8CABB854F8EA9C17B5B8DE48EC6 Number of blocks: 183500800 Block size: 4096 Number of

Hello all, I'm having trouble compiling ocfs2-tools-1.6.3 on slackware64-13.1 These are my configure flags (the last 2 I added after googling this problem, but didn't help): ./configure \ --sbindir=/sbin \ --bin=/bin \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --datadir=/etc/ocfs2 \ --sharedstatedir=/var/ocfs2 \ --libexecdir=/usr/libexec \

I recently rebooted one of my machines and was greeted with a message about one of my ext3 partitions having some errors. I dutifully started e2fsck on the partition, but after a few hours of some useful messages about fixing inodes, it then started printing out lists of ascending numbers which I'm not sure how to interpret. The first time I noticed this, these numbers were in the 4000000

hi, i have a tricky situation here and and don't know where to start with the solution. i happened to set up a linux system, but i had to install the base system on another machine. i used e2fsprogs 1.30-WIP (30-Sep-2002) for this. now the machine is up and running, but i have to use e2fsprogs 1.27 (8-Mar-2002). it's a debian system and i wanted to stay sane & stable, hence using

Hello everybody, I am new to this list, so welcome everybody. Last 2 week I had two harddisk crashes with my ext2 file system. This is what sort of happed with both of the disk: I pluged in my USB to SATA converter in my harddisk that has an ext2 filesystem. I mounted the partition, went to a directory that had a DVD image. I mounted the dvd image in the same directory and started watching the

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Hello , I use kernel 2.4.7 patched with corresponding ext3 patch. The problem I have is that when I startup I get a panic in a kernel. I started to debug util-linux and found that mount does a segmentation fault when trying to open /etc/mtab file. The segmentation fault ocurrs on open() call inside mtab_is_writable() procedure: printf("mtab_writable: pass 1\n"); if (ret ==

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.

On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. > > I am reporting this per suggestions made to me on the Fedora Users Mailing List. I would

Hi, I just tried the 2.6.22-r1 candidate to test whether some bug I have hit in the past still exists. I did use 2.6.20.6 so far. So, I have cleanly rebooted to use the new kernel, after the machine came up I tried to mess with the bug, and had to reboot again to play with kernel commandline parameters. Unfortunately, on the next reboot fsck was schedules on my filesystem after 38 clean

I am reporting this on the advice of the Fedora Users Mailing List Member. This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. I am reporting this per suggestions made to me on the Fedora Users Mailing List. The following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On

Hello, I looked through the archives a bit and could not find anything relevant, if you know otherwise please point me in the right direction. I have a ~3T ext3 filesystem on linux software raid that had been behaving corectly for sometime. Not to long ago it gave the following error after trying to mount it: mount: wrong fs type, bad option, bad superblock on /dev/md0, or too many