01-18-2012
RHEL and Centos VMs with IO failure on root
Hello,
I am running into this issues, few VMWare VM's that are running with RHEL 5.6 and Centos 5.7, are having read write errors on the root file system. This is noticed on all vm's. After looking to log files this what I noticed.
#touch test.txt
touch: cannot touch `test.txt': Read-only file system.
#
after this we have reboot the server, during booting up, fsck is fixing the issue, in one case we had to rebuild whole VM as did keep on panic, it did'nt as prompt for fsck.
some of the log message error that I noticed.
Jan 18 13:25:01 Hostname1 kernel: EXT3-fs warning (device dm-0): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
Jan 18 13:25:01 Hostname1 kernel: EXT3-fs warning (device dm-0): ext3_clear_journal_err: Marking fs in need of filesystem check.
Thanks,
10 More Discussions You Might Find Interesting
1. Virtualization and Cloud Computing
Hi
I would like to know how to do virtualization in Rhel 5.3 and Cent os 5.3, As i am new this Virtualization need guidence how to install and configure guest os in Rhel and Cent Os
can some one guide me step by step
Regards
Solaris8in (1 Reply)
Discussion started by: solaris8in
1 Replies
2. Red Hat
Hi, I have some questions about RHEL and CentOS download and installation.
(1) Is RHEL6.0 x86_64 beta downloaded from Red Hat site working fine?
(2) Where to download CentOS 5.5 DVD iso without using BitTorrent?
(3) What are the differences between these two images - CentOS 5.5 i386 and... (6 Replies)
Discussion started by: aixlover
6 Replies
3. Red Hat
Hi all, i have 3 nodes cluster (Centos 5 cluster suit) with out quorum disk,
node vote = 1,
the value of a quorum = 2,
when 2 nodes going offline, cluster services are destoys.
How i can save the cluster and all services(move all services to one alive node)
with out quorum disk when other... (3 Replies)
Discussion started by: Flomaster
3 Replies
4. Red Hat
Hello,
I was wondering if it would be possible to run two VMs one with services for IPv4 and the other one with services for IPv6. The main physical system would be connected to a IPv6 switch.
I think it should be fine but I would like to hear out your comments. (1 Reply)
Discussion started by: svalenciatech
1 Replies
5. Red Hat
Hi guys
I have CentOS installed on my server. I have also installed TFTP server, DHCP server. I am able to install CentOS on remote machines using PXE boot and kickstart cfg file.
I would like to install OpenSUSE using CentOS kickstart file. How do I do it ? I am also fine with any other... (2 Replies)
Discussion started by: msohail
2 Replies
6. Red Hat
Hello,
Can someone suggest me what I missing, I re-sized a root virtual disk to 30GB on the CentOS VM. After re-sizing the disk, I booted the OS and ran fdisk -list command I was able view the size of the disk as 30GB.
Paritions in the vm before I resize are:
/boot - Primary parition
/... (1 Reply)
Discussion started by: bobby320
1 Replies
7. UNIX for Dummies Questions & Answers
Came home the other day to a Napp-it Gui that would not load.
Login would appear but when i attempted I would get the following
Set default permissions and reading disk and pool parameter, please wait..
in case of problems, try a reboot after Power-Off or check disk and pool status at CLI.... (1 Reply)
Discussion started by: fastedd27
1 Replies
8. Red Hat
I was testing Networking Teaming (activebackup) with a VM hosted on VmWare Workstation and VirtualBox, and the result is, if the active interface is down, the system is not using the backup interface.
Tested on both CentOS / RHEL 7
Please find below the command I have used to configure teaming.... (0 Replies)
Discussion started by: atanubanerji
0 Replies
9. Red Hat
Hi All,
I have one logical volume with size as 900G and it is mounted as xfs file system.
Now I want to reduce this partition to 500G.
So I followed the below steps.
unmount the mount point /home
Reduced the volume using the command
Now I remounted the partition.
But the problem... (3 Replies)
Discussion started by: kalpeer
3 Replies
10. Red Hat
Hi!
One of our clients need RHEL 7 on PPC hardware for their R&D setup and they are particular about this being 'Little Endian'.
The problem is that Redhat doesn't have LE RHEL7 images below 7.1 while the latest toolkit (which is needed while reimaging an IBM LPAR) that IBM provides only... (0 Replies)
Discussion started by: satish51392111
0 Replies
LEARN ABOUT CENTOS
fsck.minix
FSCK(8) System Administration FSCK(8)
NAME
fsck.minix - check consistency of Minix filesystem
SYNOPSIS
fsck.minix [-larvsmf] device
DESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem. The current version supports the 14 character and 30 character
filename options.
The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writ-
ing to it (and remember that the kernel can write to it when it searches for files).
The device name will usually have the following form:
/dev/hda[1-63] (IDE disk 1)
/dev/hdb[1-63] (IDE disk 2)
/dev/sda[1-15] (SCSI disk 1)
/dev/sdb[1-15] (SCSI disk 2)
If the filesystem was changed (i.e., repaired), then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before
exiting. Since Linux does not currently have raw devices, there is no need to reboot at this time.
WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility
that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a
mounted filesystem (i.e., the root filesystem), make sure nothing is writing to the disk, and that no files are "zombies" waiting for dele-
tion.
OPTIONS
-l List all filenames.
-r Perform interactive repairs.
-a Perform automatic repairs. (This option implies -r and serves to answer all of the questions asked with the default.) Note that
this can be extremely dangerous in the case of extensive filesystem damage.
-v Be verbose.
-s Output super-block information.
-m Activate MINIX-like "mode not cleared" warnings.
-f Force a filesystem check even if the filesystem was marked as valid (this marking is done by the kernel when the filesystem is
unmounted).
SEE ALSO
fsck(8), fsck.ext2(8), mkfs(8), mkfs.minix(8), mkfs.ext2(8), reboot(8)
DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.
If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX filesystem,
fsck.minix will print "bad magic number in super-block".
EXIT CODES
The exit code returned by fsck.minix is the sum of the following:
0 No errors
3 Filesystem errors corrected, system should be rebooted if filesystem was mounted
4 Filesystem errors left uncorrected
7 Combination of exit codes 3 and 4
8 Operational error
16 Usage or syntax error
In point of fact, only 0, 3, 4, 7, 8, and 16 can ever be returned.
AUTHOR
Linus Torvalds (torvalds@cs.helsinki.fi)
Error code values by Rik Faith (faith@cs.unc.edu)
Added support for filesystem valid flag: Dr. Wettstein (greg%wind.uucp@plains.nodak.edu)
Check to prevent fsck of mounted filesystem added by Daniel Quinlan (quinlan@yggdrasil.com)
Minix v2 fs support by Andreas Schwab (schwab@issan.informatik.uni-dortmund.de), updated by Nicolai Langfeldt (janl@math.uio.no)
Portability patch by Russell King (rmk@ecs.soton.ac.uk).
AVAILABILITY
The fsck.minix command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/.
util-linux July 1996 FSCK(8)