similar to: Centos-6.8 fsck and lvms

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

I am checking a file system (ext3) as shown below. It is actually a fresh file system, as I had deleted all partitions and created an ext3 file system. But when I run the check with the verbose option, it says I have one large file. Am I missing something here, or is it odd that I cannot find this large file it is reporting? I reviewed some documentation on ext3 file systems, and experimented

This is CentOS-6x. I have cloned the HDD of a CentOS-6 system. I booted a host with that drive and received the following error: checking filesystems /dev/mapper/vg_voinet01-lv_root: clean, 128491/4096000 files, 1554114/16304000 blocks /dev/sda1: clean, 47/120016 files, 80115/512000 blocks /dev/mapper/vg_voinet01-lv_home: clean, 7429/204800 files, 90039/819200 blocks

On 2013-08-29, at 7:48 PM, Richards, Paul Franklin wrote: > 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

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

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

greetings one and all. when attempting to install centos 6.8 to an i386 mid tower, during setup of hard disk partitions, selection is for /dev/sde. if continued, after reboot, error is displayed after 'welcome to centos'. lines read: Checking filesystem fsck.ext4: no such file or directory while trying to open /dev/sda3 /dev/sda3: The superblock could not be read or does not describe a

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. I'm attempting to setup a box here to be a file-server for all my data. I'm attempting to resize an ext3 partition to demonstrate this capability to myself before fully committing to this system as the primary data storage. I'm having some problems resizing an ext3 filesystem after I've resized the underlying logical volume. Following the ext3 resize, fsck spits out lots

Hello, This may be a slightly rambling and inexpert question from point of view of the learned folks on this list - feel free to go and read something more interesting, but I am curious and a little alarmed about a recent event. I am running Linux from Scratch ("LFS"), under a locally compiled Kernel 2.4.20 (SMP). The root filsytem was created as ext2 and converted to ext3 with an

Dear Ted, I upgraded e2fsprogs and util-linux to the latest versions, as per the instructions on the "ext3 for 2.4" page, to make the switching between ext2-only and ext3-enabled kernels seamless. Now that if the filesystems have not been unmounted cleanly, due to a power failure for example, "fsck -A -a" cannot continue after checking the root filesystem on reboot, issuing

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 folks, For unknown cause I encounter following mounting problem; # /mnt/hda8 mount: wrong fs type, bad option, bad superblock on /dev/hda8, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg | tail via82cxxx: timeout while reading AC97 codec (0x9A0000) via82cxxx: timeout while reading AC97 codec (0x9A0000)

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 Everyone, I have a server which has a raid array on /dev/sdb. After a crash I tried to mount the array and it failed with: mount: wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or other error dmesg reports: EXT3-fs: invalid journal inode. I tried to run e2fsck and it failed (The output can be seen below). If anyone has any suggestions on how I can restore

Hello ext3 list, I am having an odd issue with one of my filesystems, and I am hoping someone here can help out. Yes, I do have backups. :) But as is often the case, it's nice to avoid restoring from backup if possible. If there is a more appropriate place for this question please let me know. After quite a while between reboots, I saw a report on the console that the filesystem was

I posted this to the Fedora-list, but thought I might get some additional information here as well. I have a HD that refuses to mount with a 'bad magic number in super-block'. I'm running FedoraCore 6 x86_64. [root at moe ~]# fdisk -l /dev/hdc Disk /dev/hdc: 250.0 GB, 250059350016 bytes 255 heads, 63 sectors/track, 30401 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes

Hi, Jan On Wed, Jul 27, 2016 at 11:56 PM, Jan Kara <jack at suse.cz> wrote: > Hi! > > On Wed 27-07-16 15:58:55, Zhangfei Gao wrote: >> Hi, Michael >> >> I have met ext4 error when using vhost_scsi on arm64 platform, and >> suspect it is vhost_scsi issue. >> >> Ext4 error when testing virtio_scsi & vhost_scsi >> >> >> No

Hi, Jan On Wed, Jul 27, 2016 at 11:56 PM, Jan Kara <jack at suse.cz> wrote: > Hi! > > On Wed 27-07-16 15:58:55, Zhangfei Gao wrote: >> Hi, Michael >> >> I have met ext4 error when using vhost_scsi on arm64 platform, and >> suspect it is vhost_scsi issue. >> >> Ext4 error when testing virtio_scsi & vhost_scsi >> >> >> No

Hi All I just installed a 2 node ,10 r2 rac on centos Linux 4.6 My rac install was done by following Jeff Hunters document (excellent work!) http://www.idevelopment.info/ For storage I used openfiler with the iscsi protocol http://www.openfiler.com/ everything went perfect... to the letter, I gracefully shutdown the 2 nodes , then the openfiler appliance, when I went to start it back up,