similar to: forced fsck (again?)

If I have the 6th column in fstab (the pass column) set to 0, does that mean disk checks will never be forced at boot regardless of anything like File System State, Mount Count, and Check Interval on the file system itself, or are there exceptions to this? I know `man fstab` says: If the sixth field is not present or zero, a value of zero is returned and fsck will assume that the filesystem does

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.

I have worked quite a bit with CentOS 4.x with SAN, multipathing, LVM etc. The way I mount my file systems is using a script that is called during startup that runs fsck, imports the physical volumes, and volume groups, activates the logical volumes, creates the mount point if needed then mounts the volume, I mainly made it for software iSCSI due to the iscsi stack loading after the system mount

well, the next place to go, if fsck isn't enough would be to to try debugfs(1) man debugfs. On Wed, Nov 18, 2015 at 8:39 PM, Boylan, Ross <Ross.Boylan@ucsf.edu> wrote: > I guess some of the trouble was that the virtual disk was mounted > read-only at the VM level. When I mounted read/write I was able to do > fsck, which gave messages about replaying the logs and a couple

Hello, I have been having an annoying problem with a multi-partition domain. This domain has a separate partition for : /, /home, /usr, /var, /tmp and /data. I created it using xen-tools and the custom partitionning scheme option. The partitions are inside a LVM. When I boot the domain, it mounts the / and swap partition but none of the others. Therefore it doesn''t work... I get the

Hello, I have recently installed a lustre cluster which is in a test phase now but will potentially be in 24x7 production if its accepted. I would like input from the list on what the recommendations/best practices are for configuration of a lustre cluster startup. Is it advisable to have lustre on the various server pieces (mgs/mdt/oss''s) start automatically? If not why not?

I found a thread that has almost the exact same symptoms as me, but didn't seem to come to a resolution: https://listman.redhat.com/archives/ext3-users/2004-December/msg00018.html I have an LVM(2) array that I've just lvextend'd and want to resize2fs, but I can't get through the e2fsck. I get these errors when fsck-ing: Group 3125's inode table at 102400545 conflicts with

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

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

I have a CentOS-6.8 system which has a suspected HHD failure. I have booted it into rescue mode from a CentOS-6.5 minimal install CD in order to run fsck -c on it. The system hosts several vms. I have activated the lvs associated with these vm using pvscan -s ; vgscan ; vgchange -ay. An lvscan shows the lvs as ACTIVE. None are mounted. When I try to run fsck on any of them I see the

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

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

Hi people, i had created encrypted device with cryptsetup/LUKS which i setup with an ext4 filesystem. This device is an external USB harddisk. When i plugin this device it will be automatically mounted by my gnome3 system (Debian Wheezey/Testing), but this week i got an error. I did ask the ask the LUKS developers what is the problem and they told me that this is an ext4 problem. The error

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

There were no live connections. The problem what we had was more related to OS requirement for some software. This drive was not in a bad shape. On 12 July 2016 at 23:03, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 07/12/2016 09:52 AM, Hersh wrote: > >> There was some problem with our system so I re-installed the server with >> CentOS 7. Now, when I am

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

Hi! I was testing 2.6.0-test5, but got lots of journal aborted errors. Then I Sysrq-s/u/b and wanted to boot 2.4.23-pre3 or 2.4.22, but ext3 error: cannot find root fs cannot mount because of unsupported optional feature (4) after trying to mount it with ext2 (rootfstype=ext2, not working) I rebooted again into 2.4.22, this time there was just severe fs corrpution, illegal blocks, inodes,

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

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