similar to: hole in ext3 filesystem - how to repair?

Hello. I am having a problem with one CentOS 4 box I have installed. It worked perfectly for several days, was used as a gateway on my LAN. After having reached the limit of the disk size by copying stuff from a windows box to a samba shared drive on the centOS box, and after making a reboot, the server didn't come up anymore. Looking at it I was thrown to the repair console and when doing

Hi. One of my ext3 partitions seems to be broken. But the problem is: fsck doesn´t recognize or repair the broken filesystem. But first let me tell how it is broken. There are some files that seems to be broken. for example /etc/resolv.conf in this case. Now, if I´ll try to read /etc/resolv.conf I get a error that /etc/resolv.conf doesn´t exists. But "ls" and so on list the file. I

Hi, I'm running a production server (Debian Sarge install) whose root filesystem (a software raid 1 array of 2 partitions of IDE drive) exhibited the following problem: Oct 28 06:00:06 server2 kernel: attempt to access beyond end of device Oct 28 06:00:06 server2 kernel: md2: rw=1, want=3050401328, limit=16353920 [...] a few of the above line snipped, want is different each time Oct 28

hi All, A fault on our SAN dropped us down to a read-only filesystem and after reboot, we have an "Unexpected Inconsistency" and I am being instructed by the boot to run fsck manually without -a or -p (this was after I think processing around 15% of the filesystem) The specific message is "inode 27344909 has illegal blocks" I recall running fsck some years ago on smaller

On 09/20/2014 12:07 AM, Andreas Dilger wrote: > On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008@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

Hi, I have a 20GB partition on a hard disk that just developed bad blocks. Fortunately, I had backups for the most important data on it, but I'd like to recover some files that were too large to backup. When running 'e2fsck /dev/hdc3', I get the following message: e2fsck 1.27 (8-Mar-2002) Group descriptors look bad... trying backup blocks... e2fsck: Invalid argument while checking

hi All, thanks for the responses. After being dropped into the # Filesystem repair prompt, ( on account of "inode 27344909 has illegal blocks" ) following warm reboot (via "reboot") after finding (SAN ) filesystem in read-only mode yesterday morning (possibly because of HBA fault on SAN) , I ran fsck -r /data (Linux version 2.6.18-92.1.18.el5 , Red Hat 4.1.2-42 , ext3

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

I am testing EXT3 as a filesystem for a server whose power supply is failure prone. In order to do the test, I have a lever that I can control from PC1 that can press the reset button on PC2. PC2's reset button is automatically pressed once every 120 seconds (the boot sequence on PC2 takes 80 seconds). While PC2 is booted, PC1 directs email and web requests at PC2, so that the PC2 disks are

Hello, First, sorry for my english. I'm new in this list, and I'm having troubles because a lack of disk on my Raid 5. The server have a LVM system on the Raid 5 and the partitions on LVM is ext3. I can't identify where the ext3 superblock is on this LVM partition to use the fsck. I've tried many ways: fsck -b 8192 /dev/VolGroup/LogVol04 dumpe2fs /dev/VolGroup/LogVol04 | grep

I've Found a page with interesing discussion about images backup http://forums.fedoraforum.org/archive/index.php/t-28255.html This give a "dirty" solucion for remove special thing of ext3 (Selinux remove resize_inode and ext_attr features) witch cause the error in ghost. I hope somebody help with the problem of norton ghost and clone centos 4. :) ----------- sfabkk 2005-07-11,

I need to downgrade a system from Centos x4.2 to v3.6 (x86) due to performance problems with Arkeia Network Backup and AIT-4 tape drives. The backup database is stored on a v4.2 created ext3 partition. When accessing this partition after the downgrade, Centos complains on boot that fsck.ext3: Filesystem has unsupported feature(s) (/dev/sda5) *fsck: Get a newer version of e2fsck! [fail] If I

(There really doesn't seem to be a dedicated e2fsprogs list, so this was the next-best place I could find. I don't place much faith in the sourceforge forums..) The filesystem in question is a 480 gig ext3 partition, on a hardware RAID5 controller. It's approximately 90% full, with something like 115K files. Kernel 2.4.20-pre4, on a Duron 900. As I type this, e2fsck has used up

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

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 am unable to mount an ext3 filesystem on RHEL AS 2.1. This is not the boot or root filesystem. When I try to mount the file system, I get the following error: mount: wrong fs type, bad option, bad superblock on /dev/sdj1, or too many mounted file systems When I try to run e2fsck -vvfy /dev/sdj1 I get the following error: Group descriptors look bad... trying backup blocks...

I have a bit of a problem with the machine I use at home for backups. The main partition the backups reside on is a 4 disk RAID-5, totaling around 240GB. This has had some sort of corruption inflicted on it, in the content of the (at least) one directory, where there are now corrupted directory entries. This happened after I added an additional SiS PCI IDE controller card to the machine and put

Peter Kjellstr?m wrote: > On Monday 23 January 2006 16:46, Plant, Dean wrote: >> I need to downgrade a system from Centos x4.2 to v3.6 (x86) due to >> performance problems with Arkeia Network Backup and AIT-4 tape >> drives. The backup database is stored on a v4.2 created ext3 >> partition. When accessing this partition after the downgrade, Centos >> complains on

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

Hi, Using dumpe2fs I have been able to determine that all of my alternate ext3 superblocks are corrupted (not clean), and only the primary superblock is valid, i.e. mount works and the ordered journal is applied. When the primary superblock gets flakey, i.e. the ext_attr Filesystem feature goes missing - not sure why this occurs. At this point, the mount does not apply the journal using the