hdisk status in sdd volume groups

10 More Discussions You Might Find Interesting

1. Red Hat

No space in volume group. How to create a file system using existing logical volume

Hello Guys, I want to create a file system dedicated for an application installation. But there is no space in volume group to create a new logical volume. There is enough space in other logical volume which is being mounted on /var. I know we can use that logical volume and create a virtual...

2. AIX

Check status of a volume group

Hi huys, Sorry for my bad english, i'm french :o . I've got a little question : is there a way to check status of a VG on aix 6.1 ? I want to know if a VG is locked or not... I can do a "lsvg -Ll rootvg" for example, but if this VG is already locked, the process waits without gives me the...

3. UNIX for Dummies Questions & Answers

Confusion Regarding Physical Volume,Volume Group,Logical Volume,Physical partition

Hi, I am new to unix. I am working on Red Hat Linux and side by side on AIX also. After reading the concepts of Storage, I am now really confused regarding the terminologies 1)Physical Volume 2)Volume Group 3)Logical Volume 4)Physical Partition Please help me to understand these concepts.

4. UNIX for Advanced & Expert Users

prtdiag -v problem :Memory Module Groups status not Showing

Hi Friends, I need a help from you all. In my machine which is on Solaris 9. the command prtdiag -v shows the complete output but it doesn't show "Memory Module Groups status" status. I have tried restarting the picl daemon, but still it doesn't work. Memory Module Groups:...

5. AIX

AIX SDD

I have sdd driver installed correctly but when I run the command: datapath query adapter No device file found what does it mean.. it is not using vpath or whats wrong?

6. Solaris

Volume groups

Do we have concepts of volume groups in solaris like we have in Linux(command: vgdiplay) and AIX(command: lsvg). If yes, then what commands/ files can give details for same.

7. UNIX for Advanced & Expert Users

volume groups

Do we have concepts of volume groups in solaris like we have in Linux(command: vgdiplay) and AIX(command: lsvg). If yes, then what commands/ files can give details for same.

8. AIX

Basic Filesystem / Physical Volume / Logical Volume Check

Hi! Can anyone help me on how I can do a basic check on the Unix filesystems / physical volumes and logical volumes? What items should I check, like where do I look at in smit? Or are there commands that I should execute? I need to do this as I was informed by IBM that there seems to be...

9. AIX

Volume Groups and the SAN

Hello all. I have a perplexing problem I have an AIX 5.1 system on an EMC SAN. This system had been on a CX400 SAN for several years. The system was migrated to a CX700 just over a week ago. The migration consisted of utilizing on of the HBAs in the system and connecting to both SANs ...

10. Solaris

How to resize mirror volume in veritas volume manager 3.5 on Solaris 9 OE

Hi all, I have a problem with vxvm volume which is mirror with two disks. when i am try to increase file system, it is throwing an ERROR: can not allocate 5083938 blocks, ERROR: can not able to run vxassist on this volume. Please find a sutable solutions. Thanks and Regards B. Nageswar...

LEARN ABOUT SUSE

lsdev

LSDEV(8)							Linux System Manual							  LSDEV(8)

NAME

       lsdev - display information about installed hardware

SYNOPSIS

       lsdev

DESCRIPTION

       lsdev  gathers information about your computer's installed hardware from the interrupts, ioports and dma files in the /proc directory, thus
       giving you a quick overview of which hardware uses what I/O addresses and what IRQ and DMA channels.

OPTIONS

       None.

FILES

       /proc/interrupts
	      IRQ channels.

       /proc/ioports
	      I/O memory addresses.

       /proc/dma
	      DMA channels.

BUGS

       lsdev can't always figure out which lines in the three examined files refer to one and the same device, because these files  sometimes  use
       different  names  for the same piece of hardware. For example, in some kernels the keyboard is referred to as `kbd' in /proc/ioports and as
       `keyboard' in /proc/interrupts.	This should be fixed in the kernel, not in lsdev (as has indeed happened for this particular example).

       The program does however try to match lines by stripping anything after a space or open	parenthesis  from  the	name,  so  that  e.g.  the
       `serial'  lines	from /proc/interrupts match the `serial(set)' lines from /proc/ioports.  This attempt at DWIM might be considered a bug in
       itself.

       This program only shows the kernel's idea of what hardware is present, not what's actually physically available.

SEE ALSO

       procinfo(8).

AUTHOR

       Sander van Malssen <svm@kozmix.cistron.nl>

3rd Release							    1998-05-31								  LSDEV(8)

AIX