search for: fsckoptions

...ee whether it was a practical proposition for this kind of thing yet. Appears to be working so far, with a 300MB journal (based on the rule of thumb in the ext3 README), but we did notice that whereas our (RedHat) /etc/rc.d/rc.sysinit said to do a... initlog -c "fsck -C -T -R -A -a $fsckoptions" to check the non-root filesystems, we actually got a crash from the fsck parent process until we changed to serialized fscking, viz. initlog -c "fsck -s -C -T -R -A -a $fsckoptions" If this isn't a known problem (I've only been skimmed the list postings, so apolog...

...So I dug a little, and found that putting some comments in /etc/rc.d/rc.sysinit would circumvent *the error* and allow the box to boot. Here are the lines - (around line 375) if [ "${RHGB_STARTED}" != "0" -a -w /etc/rhgb/temp/rhgb-console ]; then fsck -T -a $rootdev $fsckoptions > /etc/rhgb/temp/rhgb-console else initlog -c "fsck -T -a $rootdev $fsckoptions" fi Here are the grub.conf boot settings: title CentOS (2.6.9-22.ELsmp) root (hd0,0) kernel /vmlinuz-2.6.9-22.ELsmp ro root=LABEL=/ rhgb quiet initrd /initrd-2.6.9-22.ELsmp....

...> Bear with me on this. The last time I did anything like this I ended up having to boot into recovery mode from an install cd and do this by hand. This is not an option in the present circumstance as the unit is a headless server in a remote location. If I do this: echo '-c' > /fsckoptions touch /forcefsck shutdown -r now Will this repair the bad block and bring the system back up? If not then what other options should I use? The bad block is located in an LV assigned to a libvirt pool associated with a single vm. Can this be checked and corrected without having to deal with the b...

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

...last time I did anything like this I ended > up having to boot into recovery mode from an install cd and do this by > hand. This is not an option in the present circumstance as the unit > is a headless server in a remote location. > > If I do this: > > echo '-c' > /fsckoptions > touch /forcefsck > shutdown -r now > > Will this repair the bad block and bring the system back up? If not > then what other options should I use? > > The bad block is located in an LV assigned to a libvirt pool > associated with a single vm. Can this be checked and corre...

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