Volume Groups and the SAN Post: 302199704

10 More Discussions You Might Find Interesting

1. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the...

2. Linux

Howto clone/migrate a volume in the SAN

Dear Srs, I have a Linux server (linux01) booting from SAN with a volume in a Nexsan SATAbeast storage array (san01). The disk/volume has four ext3 partitions, total size is near to 400GB, but only 20-30GB are in use. I need to move this disk/volume to another Nexsan SATAbeast storage array...

3. Red Hat

how to mount SAN volume with its increased size

Hi, We have 200GB SAN volume mounted on Redhat EL 5. which is working fine. As my SAN supports dynamic resizing of volumes, i unmounted the volume and resized the SAN Volume to 300 GB successfully. Then i mounted again but it shows 200GB only but data is intact. Now, my requirement is to let...

4. Solaris

Ldom OS on SAN based zfs volume

Is it possible to use zvol from SAN LUN to install LDOM OS ? I 'm using following VDS from my service domain VDS NAME LDOM VOLUME DEVICE primary-vds0 primary iso sol-10-u6-ga1-sparc-dvd.iso cdrom ...

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

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

hdisk status in sdd volume groups

hi all we recently upgraded our san switches. after that, i found i got many hdisks showing in lsdev with status "Defined" and "Available". the number of "Defined" is equal to "Available". the time stamp shows all "Available" disks created at our downtime night. "datapath query device"...

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

9. Red Hat

Volume group not activated at boot after SAN migration

I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew...

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

LEARN ABOUT OSF1

reboot

reboot(8)						      System Manager's Manual							 reboot(8)

NAME

       reboot - Restarts the machine

SYNOPSIS

       /usr/sbin/reboot [-dlnq]

DESCRIPTION

       When  the  system  is running and multiple users are logged in, use the shutdown -r command to perform a reboot operation.  If no users are
       logged in, use the reboot command.

       The reboot command normally stops all running processes, syncs the disks, logs the reboot,  and	writes	a  shutdown  entry  in	the  login
       accounting file, /var/adm/wtmp.

       The  reboot command uses the sync call to synchronize the disks, and to perform other shutdown activities such as resynchronizing the hard-
       ware time-of-day clock.	After these activities, the system reboots.  By default, the system starts and the file systems are  automatically
       checked.  If the start-up activities are successful, the system comes up in the default run-level.

       You must have root privileges to use this command.  Using the -n flag can result in file system damage.

FLAGS

       Generates  a  crash  dump  of the system before halting it.  Can be used with any of the other flags.  Does not log the reboot using syslog
       Does not sync the disks or log the reboot using syslog Performs a quick reboot without first shutting down running processes; does not  log
       the reboot using syslog

EXAMPLES

       To  enable  the	default reboot action, enter: reboot This command causes the system to stop all running processes, sync the disks, log the
       shutdown, and perform other routine shutdown and reboot activities.  To shut down the system without logging the reboot, enter:	reboot	-l
       This  command  shuts  down  the	system and performs all shutdown and reboot activities, except logging the shutdown.  To reboot the system
       abruptly, enter: reboot -q This command reboots the system abruptly without shutting down running processes.

FILES

       Specifies the command path Specifies the login accounting file Specifies the path of the syslog daemon

RELATED INFORMATION

       Commands:  fsck(8), halt(8), init(8), savecore(8) shutdown(8), syslogd(8)

       Functions:  reboot(2), sync(2), syslog(3) delim off

																	 reboot(8)