Sponsored Content
Full Discussion: Quorum and hdisk issue
Operating Systems AIX Quorum and hdisk issue Post 302827029 by bakunin on Thursday 27th of June 2013 06:23:30 PM
Old 06-27-2013
The system told you to issue a "varyoffvg" and then a "varyonvg". Have you done that? What was the outcome? Were there any error messages?

Which disk (if a disk at all) has maybe caused a possible problem i can't tell from here, because my line of sight to Bangalore is blocked and my crystal ball is in repair.

I suggest you start advanced troubleshooting instead, by applying your reading skills to the OS output. Your data are as safe as they can be, given the circumstances, because an inactive VG with only unaccessible filesystems can't get any worse than it already is: either you can revive it or the data on it is already lost.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. AIX

vpath to an hdisk

Is there a simply way for me to map a vpath to an hdisk on AIX 5.2? (5 Replies)
Discussion started by: 2dumb
5 Replies

2. AIX

Check quorum for volume group

Hi all, I would like to ensure that a volume group has an effective quorum setting of 1 (or off). I know you can change the quorum setting using the chvg -Q command but want to know if the setting has been changed before the vg was varied on or a reboot. In other words how can I ensure that... (3 Replies)
Discussion started by: backslash
3 Replies

3. Emergency UNIX and Linux Support

AIX APPVG - QUORUM LOST, VOLUME GROUP CLOSING

Hi, I am running AIX 5.3 TL8. After a disk failure, one of my mirrored application volumegroups went down. Unfortunately we have quorum switched on on this VG and the defective disk holds the majority. I have set MISSINGPV_VARYON to TRUE and tried a forced varyon but it's still failing. I... (3 Replies)
Discussion started by: zxmaus
3 Replies

4. AIX

Dummy hdisk in AIX 6.1

How do you create a dummy hdisk with AIX 6.1? In previous versions, I've used this and works, but now I get this error. hostname:/:# mkdev -l hdisk57 -c disk -t osdisk -s scsi -p fscsi0 -w 0,10 -d Method error (/etc/methods/define): 0514-022 The specified connection is not valid. Any... (2 Replies)
Discussion started by: kah00na
2 Replies

5. AIX

LVM - Quorum

Hi all Just a question about quorum. I am running AIX 5.3 Rootvg has 2 PV - not mirrored. quorum is switched on. What happens when one disk fails?, can i replace the disk and bring the entire VG back up. with all the data intact. knowing that the VG will be unavailable until i replace the... (3 Replies)
Discussion started by: Andre54
3 Replies

6. AIX

Quorum in lsvg output

Hi there, I have three servers and I'm puzzled by the oputput I get from lsvg rootvg. Server 1 : QUORUM: 2 (Enabled) Server 2 : QUORUM: 1 (Disabled) Server 3 : QUORUM: 1 All VG are build on 2 PV and are mirroring. What could cause the number to be different?... (2 Replies)
Discussion started by: petervg
2 Replies

7. AIX

Flashcopy, ghost hdisk ??

Hi all, I'm getting some errors on AIX regarding Flashcopy and volume group hard disks. The script that activates flashcopy showed this errors: Recreating Flashcopy for lun01_A1 Performing syntax check... Syntax check complete. Executing script... Script execution complete. SMcli... (1 Reply)
Discussion started by: enux
1 Replies

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

9. AIX

How can I map hdisk# to rhdisk#?

Some storage/disks have been added to an existing AIX 6.1 server. The admin sent me the list of hdisk#'s for the new disks, but I need the corresponding rhdisk# for the same hdisk. (I know from past experience that the rhdisk that maps to an hdisk is not always the same number. For instance,... (5 Replies)
Discussion started by: sbrower
5 Replies

10. Solaris

Precaution during Quorum Server Reboot

Hi I need to know what are the precaution we should take during quorum server reboot as this quorum server is providing quorum devices to five different solaris two node clusters. Also let me know do I have to follow below procedure as well before and after reboot of quorum server Do I... (3 Replies)
Discussion started by: sb200
3 Replies
SYNC(2) 						      BSD System Calls Manual							   SYNC(2)

NAME
sync -- synchronize disk block in-core status with that on disk LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <unistd.h> void sync(void); DESCRIPTION
The sync() function forces a write of dirty (modified) buffers in the block buffer cache out to disk. The kernel keeps this information in core to reduce the number of disk I/O transfers required by the system. As information in the cache is lost after a system crash, kernel thread ioflush ensures that dirty buffers are synced to disk eventually. By default, a dirty buffer is synced after 30 seconds, but some filesystems exploit ioflush features to sync directory data and metadata faster (after 15 and 10 seconds, respectively). The function fsync(2) may be used to synchronize individual file descriptor attributes. CAUTIONS
Many modern disks contain write-back caches. In theory sync() flushes these. In practice there are many possible ways for this mechanism to go astray. It is prudent (where possible) to allow a few seconds after syncing for everything to settle before e.g. turning off the power. It may also be desirable to use dkctl(8) or scsictl(8) to disable the write-back cache entirely. SEE ALSO
fsync(2), dkctl(8), scsictl(8), sync(8) HISTORY
A sync() function call appeared in Version 6 AT&T UNIX. Historically, sync() would schedule buffers for writing but not actually wait for the writes to finish. It was necessary to issue a second or sometimes a third call to ensure that all buffers had in fact been written out. In NetBSD, sync() does not return until all buffers have been written. BSD
March 25, 2009 BSD
All times are GMT -4. The time now is 06:53 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy