04-04-2013
before to try the varyonvg, could you check if lspv shows the same content in both nodes
I not have experience in XIV, but in another Storage Copies (EMC, HDS), probably you need clean the reservations that the original system put in the physical devices.
I think tyhat you need heck that the attributes on same nodes are the same, use lsattr -El hdiskX to review these, in special the reservation policy values.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
Strange problem on p5 520 server. I've created two volume groups, filesystems, etc.. Everything working fine, without any problem. After some tests with a DS4300 unit I wanted to remove the volume groups, change the DS4300 configuration, and re-create a new volumegroup. However, I'm... (0 Replies)
Discussion started by: EricBE
0 Replies
2. UNIX for Dummies Questions & Answers
I am trying to move a file that is in the root directory. I suspect it is an old file created by someone when the system was installed. I am testing accessing the file by doing a copy but the command does not find the file.
I am operating as root. We are HP-UX B.11.23
I do long listing and... (3 Replies)
Discussion started by: phcorn
3 Replies
3. AIX
Good evening,
Thanks a lot for your help, we appreciate it a bunch. Heres basically a summary of what we have (sorry Im adding some extra history as well):
We have 2 Ibm Servers (Hag and Aki) that are running AIX Version 5. Each connect to a SAN device via 2 separate fiber paths. Hag seems to... (9 Replies)
Discussion started by: aix-olympics
9 Replies
4. AIX
Hi all.
I'm new to AIX, so... We are running a BCV process between two AIX 5 machines attached to EMC Clariion SAN. During the varyonvg portion of the BCV process, we experienced a failure due to the physical volume is marked missing (PVMISSING). What diagnostics can I run to see the missing... (2 Replies)
Discussion started by: KSFlyer
2 Replies
5. AIX
Hello,
On Aix 5.3, during importvg, the varyonvg fails:
importvg -y vgtest hdisk20
0516-013 varyonvg: The volume group cannot be varied on because
there are no good copies of the descriptor area.
When i use manually the command varyonvg -u -b -t vgtest to force, the vg can... (3 Replies)
Discussion started by: dantares
3 Replies
6. Solaris
Hi,
I'm learning for my Solaris 10 sys-admin part 2. I'm now trying to get nis working because for the exercise. I run in to a problem.
Setup:
Three Systems
solaris101 (client)
Nothing wrong here havent made any config changes yet.
solaris102 (master server)
Interfaces
... (1 Reply)
Discussion started by: jld
1 Replies
7. Solaris
Hi guys,
I had a solaris box, with veritas controled disk.
1 disc is showing soft errors, how can I repair the soft errors?
Please help.
Cheers; (4 Replies)
Discussion started by: Mujakol
4 Replies
8. Shell Programming and Scripting
I am trying to move content of a folder usingls /backup/db_backups/INCREMENTAL/|while read file ; do
mv $file /backup_LOCAL/db_backups/INCREMENTAL/
done...but when I run this command using a bash script I'm getting this error ./test.sh
mv: cannot stat... (6 Replies)
Discussion started by: rocking77
6 Replies
9. AIX
Iam new to AIX
I am unable varyonvg on the vios,some of the disk are reported as harware failure.
I am going to replace the disk,Please tell me how to remove the disk without any corruption in the VG
lspv -l hdiskx also didn't work (0 Replies)
Discussion started by: roayaix
0 Replies
10. AIX
Hi there,
I am trying to determine if a specific XIV LUN on AIX is in OPEN or CLOSED state. I would like tthe same info as I can get from pcmpath command on v7000 LUN-s. I would need this info to find out if I can safely delete a LUN or not.
I tried fuser command, but no luck. It did not... (6 Replies)
Discussion started by: trifo75
6 Replies
devfs(7FS) File Systems devfs(7FS)
NAME
devfs - Devices file system
DESCRIPTION
The devfs filesystem manages a name space of all devices under the Solaris operating environment and is mounted during boot on the /devices
name space.
The /devices name space is dynamic and reflects the current state of accessible devices under the Solaris operating environment. The names
of all attached device instances are present under /devices.
The content under /devices is under the exclusive control of the devfs filesystem and cannot be changed.
The system may be configured to include a device in one of two ways:
By means of dynamic reconfiguration (DR), using, for example, cfgadm(1M).
For devices driven by driver.conf(4) enumeration, edit the driver.conf file to add a new entry, then use update_drv(1M) to cause
the system to re-read the driver.conf file and thereby enumerate the instance.
The device may be attached through a number of system calls and programs, including open(2), stat(2) and ls(1). During device attach, the
device driver typically creates minor nodes corresponding to the device via ddi_create_minor_node(9F). If the attach is successful, one or
more minor nodes referring to the device are created under /devices.
Operations like mknod(2), mkdir(2) and creat(2) are not supported in /devices.
FILES
/devices Mount point for devfs file system
SEE ALSO
devfsadm(1M), vfstab(4), attach(9E)
NOTES
The /devices name space cannot be unmounted.
All content at or below the /devices name space is an implementation artifact and subject to incompatible change or removal without notifi-
cation.
SunOS 5.10 26 Oct 2004 devfs(7FS)