similar to: [Q] Do you trust fsck?

I'm trying to do an fsck on an ext3 partition but I'm seeing abysmally slow disk throughput; monitoring with "dstat" (like vmstat) shows ~1200-1500KB/s throughput to the disks. Even with 24hrs of fsck-ing I only get ~3% (still in pass1). The filesystem is ext3 running "e2fsck -C0 /dev/sda3" and about 3.7TB on an x86_64-based system with 4GB RAM. e2fsprogs is 1.41.9.

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

I can't seem to find the answer to this question via web search... I changed some hardware on a server, and upon powering it back on, got the "/dev/xxx has gone 40 days without being check, check forced" message. Now it's running fsck on a huge (2 TB) ext3 filesystem (5400 RPM drives no less). How can I stop this in-progress check? Ctrl-C doesn't seem to have any effect.

Recently, our backup software oddly decided to rebackup a good portion of our file server instead of just doing an incremental. When I examined various sets of presumably identical files, I discovered that the modification dates on these files were no longer the same. Many files were re-dated to exactly one hour later such that if a file had been modified on 3/24/04 at 2:24:53 PM, it's

i posted on rhel list about proper creating of 6tb ext3 filesystem and tuning here.......http://www.redhat.com/archives/nahant-list/2006-November/msg00239.html i am reading lots of ext3 links like...... http://www.redhat.com/support/wpapers/redhat/ext3/ http://lists.centos.org/pipermail/centos/2005-September/052533.html http://batleth.sapienti-sat.org/projects/FAQs/ext3-faq.html ............but

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

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

I tried it on loop. 1. mount /dev/loop0 /mnt/test -t ext3 2. cp files to 100% full 3. umount /mnt/test 4. fsck.ext3 -f /dev/loop0 Inode xxxxx, i_blocks is xxx, should be yyy. Fix?

Hi, After our big ext3 file server crashes, I notice the fsck spends some time replaying the journals (about 5-10 mins for all volumes on the server in question). I guess it must do this should you want to mount the volumes as ext2. My question--is it (theoretically) possible to tell fsck only to replay half-finished and to knock out incomplete transactions from the journals, leaving the kernel

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

On Thu, March 9, 2017 09:46, John Hodrien wrote: > On Thu, 9 Mar 2017, James B. Byrne wrote: > >> This indicated that a bad sector on the underlying disk system might >> be the source of the problem. The guests were all shutdown, a >> /forcefsck file was created on the host system, and the host system >> remotely restarted. > > fsck's not good at finding

Hello, I have a 1.3TB ext3 filesystem that has been in service for about 3 months. About 6 days ago the Emulex fibrechannel controller logged a SCSI error and the filesystem changed to RO. It appears that the filesystem instantly changes to RO and prevents the journal from working, therefore invalidating the filesystem. The filesystem was unmounted and a remount was attempted. The mount failed

System info: ------------ [root@angel root]# cat /etc/issue Red Hat Linux release 7.2 (Enigma) Kernel \r on an \m [root@angel root]# uname -a Linux angel 2.4.9-34 #1 Sat Jun 1 06:25:16 EDT 2002 i686 unknown This problem occured after upgrade to kernel 2.4.18-17.7, backed out to previous version now (2.4.9-34). All other system RPMs are up to date according to RHN, and nothing, aside from

We have a remote warm standby system running CentOS-6.8 as a KVM system with multiple guests. One of the guests began reporting an error when running aide. Caught SIGBUS/SEGV while mmapping. File was truncated while aide was running? Caught SIGBUS/SEGV. Exiting The /var/log/messages file contained this: Mar 9 09:14:13 inet12 kernel: end_request: I/O error, dev vda, sector 14539264 Mar 9

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 All, Trying to run fsck on a local linux raid partition gave the following. [root at ... /]# fsck.ext4 /dev/md0 e2fsck 1.41.12 (17-May-2010) /dev/md0 has unsupported feature(s): 64bit e2fsck: Get a newer version of e2fsck! Odd as the server is 64bit running latest kernel and using latest "e2fsprogs.x86_64". Any ideas awould be much appreciated. Cheers Steve k

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.

Looks like the fsck bug has been stomped! I did a 960G drive this morning, and I'm 90% of the way through a 1.4T drive, both of which have *lots* of files and hard links, and it has *not* hung at 70.1%, and is running at reasonable speed. Thanks to the folks who got this one. I *really* needed to do this, esp. to our backup drives. mark

Hi, I run several hundred servers that are used heavily (webhosting, etc.) all day long. Quite often we'll have a server that either needs a really long fsck (10 hours - 200 gig drive) or an fsck that evntually results in everything going to lost+found (pretty much a total loss). Would rebooting these servers monthly (or some other frequency) stop this? Is it correct to visualize this as

Hi, We've got some units in client's vehicles which are running Fedora core 1. We've can log into them over ssh remotely there is no console attached to them. I suspect one of them has some filesystem corruption, and I'd like to both force a fsck at next reboot (which I think I can do with shutdown -F) but I'd also like to make this fsck not require any human intervention.