Sponsored Content
Homework and Emergencies Emergency UNIX and Linux Support RHEL and Centos VMs with IO failure on root Post 302591840 by sds9985 on Saturday 21st of January 2012 12:10:17 AM
Old 01-21-2012
Linux is the victim here, not the culprit. Ext3 will remount a filesystem as read-only whenever it considers I/O to that device to be unreliable, in order to protect the data (as best it can). The fact that this problem is impacting more than one VM indicates an underlying problem with the storage being shared by the ESX hosts. I don't know if this is SAN storage or iSCSI or NAS shares, but whatever it is, it's in trouble at the ESX level. Look in the VMware console for the device that's being used for the root filesystems of the problem VM's and fix it. Once that's fixed, the error messages at the guest level will disappear after the guests are rebooted. This is also what's causing the errors from the LVM commands like pvcreate.

Last edited by sds9985; 01-21-2012 at 01:31 AM..
 

10 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

virtualization in RHEL 5.3 & Centos 5.3

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

Questions About RHEL 6, CentOS 5.5 download and install

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

Centos/rhel 5 cluster 3 nodes with out Quorum

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

IPv4 and IPv6 Related Question to CentOS VMs

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

OpenSUSE installation using RHEL / CentOS Kickstart

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

Resizing root virtual disk on the CentOS

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

[Solved] Boot Failure - Openindiana w/ Napp-it - Full Root?

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

Network Teaming not working in RHEL/CentOS 7

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

How to reduce the LVM Size in RHEL/Centos 7 ?

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

Need RHEL/CentOS 7 'Little Endian' ISO for PowerPC

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
TARGETS(5)						      BSD File Formats Manual							TARGETS(5)

NAME
targets -- configuration file for iSCSI targets SYNOPSIS
targets DESCRIPTION
The targets file describes the iSCSI storage which is presented to iSCSI initiators by the iscsi-target(8) service. A description of the iSCSI protocol can be found in Internet Small Computer Systems Interface RFC 3720. Each line in the file (other than comment lines that begin with a '#') specifies an extent, a device (made up of extents or other devices), or a target to present to the initiator. Each definition, an extent, a device, and a target, is specified on a single whitespace delimited line. The extent definition specifies a piece of storage that will be used as storage, and presented to initiators. It is the basic definition for an iSCSI target. Each target must contain at least one extent definition. The first field in the definition is the extent name, which must begin with the word ``extent'' and be followed by a number. The next field is the file or NetBSD device which will be used as persistent storage. The next field is the offset (in bytes) of the start of the extent. This field is usually 0. The fourth field in the definition is the size of the extent. The basic unit is bytes, and the shorthand KB, MB, GB, and TB can be used for kilobytes (1024 bytes), megabytes (1024 kilobytes), gigabytes (1024 megabytes), and terabytes (1024 gigabytes) respectively. It is possible to use the word ``size'' to use the full size of the pre-existing regular file given in the extent name. The device definition specifies a LUN or device, and is made up of extents and other devices. It is possible to create hierarchies of devices using the device definition. The first field in the definition is the device name, which must begin with the word ``device'' and be followed by a number. The next field is the type of resilience that is to be provided by the device. For simple devices, RAID0 suffices. Greater resilience can be gained by using the RAID1 resilience field. Following the resilience field is a list of extents or other devices. Large devices can be created by using multiple RAID0 extents, in which case each extent will be concatenated. Resilient devices can be cre- ated by using multiple RAID1 devices or extents, in which case data will be written to each of the devices or extents in turn. If RAID1 resilience is used, all the extents or sub-devices must be the same size. Please note that RAID1 recovery is not yet supported by the iscsi-target(8) utility. An extent or sub-device may only be used once. The target definition specifies an iSCSI target, which is presented to the iSCSI initiator. Multiple targets can be specified. The first field in the definition is the target name, which must begin with either of the words ``target'' or ``lun'' and be followed by a number. Optionally, if a target is followed by an ``='' sign and some text, the text is taken to be that of the iSCSI Qualified Name of the target. This IQN is used by the initiator to connect to the appropriate target. The next field is a selector for whether the storage should be pre- sented as writable, or merely as read-only storage. The field of ``rw'' denotes read-write storage, whilst ``ro'' denotes read-only storage. The next field is the device or extent name that will be used as persistent storage for this target. The fourth field is a slash-notation netmask which will be used, during the discovery phase, to control the network addresses to which targets will be presented. The magic val- ues ``any'' and ``all'' will expand to be the same as ``0/0''. If an attempt is made to discover a target which is not allowed by the net- mask, a warning will be issued using syslog(3) to make administrators aware of this attempt. The administrator can still use tcp wrapper functionality, as found in hosts_access(5) and hosts.deny(5) to allow or deny discovery attempts from initiators as well as using the inbuilt netmask functionality. FILES
/etc/iscsi/targets the list of exported storage targets SEE ALSO
syslog(3), hosts.deny(5), hosts_access(5), iscsi-target(8) HISTORY
The targets file first appeared in NetBSD 4.0. BSD
December 18, 2007 BSD
All times are GMT -4. The time now is 09:03 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy