A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » General Hardware & Peripherals » Storage & Hardrives
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

VxVM objects under change of disk device name



 
 
Thread Tools Display Modes
  #1  
Old April 19th 08, 02:13 PM posted to comp.unix.solaris,comp.sys.sun.admin,comp.arch.storage
Sunny Suen
external usenet poster
 
Posts: 2
Default VxVM objects under change of disk device name

A quick one, albeit likely to have been flogged to death in this
group:

If the the device file of a disk change as result of access through a
new HBA, relocation to a new SAN or whatever, what would happen to the
VxVM objects configured earlier on the disk?

For example, suppose the device name of a disk changes from c4t5d6 to
c7t8d9. Are we still allowed to access the VxVM disk, volumes and
friends that were constructed earlier on the same disk using the name
c4t5d6?
  #2  
Old April 21st 08, 05:57 PM posted to comp.unix.solaris,comp.sys.sun.admin,comp.arch.storage
Darren Dunham
external usenet poster
 
Posts: 1
Default VxVM objects under change of disk device name

In comp.unix.solaris Sunny Suen wrote:
A quick one, albeit likely to have been flogged to death in this
group:

If the the device file of a disk change as result of access through a
new HBA, relocation to a new SAN or whatever, what would happen to the
VxVM objects configured earlier on the disk?


Nothing. VxVM tracks disks via a unique identifier written in the
private region. The disks can be moved to any new location, but as long
as it is still visible, VxVM will import it and use it correctly.

For example, suppose the device name of a disk changes from c4t5d6 to
c7t8d9. Are we still allowed to access the VxVM disk, volumes and
friends that were constructed earlier on the same disk using the name
c4t5d6?


Yes.

--
Darren Dunham
Senior Technical Consultant TAOS
http://www.taos.com/
Got some Dr Pepper? San Francisco, CA bay area
This line left intentionally blank to confuse you.
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
VxVM import hardware snapshot Stunster Storage & Hardrives 0 July 6th 06 08:12 AM
Boot Device Change rigadon General 14 February 28th 06 09:03 AM
VxVM-3.5 "vxplex" question [email protected] Storage & Hardrives 1 April 4th 05 05:24 AM
Scanning objects Nomenluni Scanners 2 June 16th 04 10:04 PM
EMC Power Volume vx VxVM Schmuck Storage & Hardrives 0 April 28th 04 05:26 PM


All times are GMT +1. The time now is 12:23 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 HardwareBanter.
The comments are property of their posters.