9 More Discussions You Might Find Interesting
1. Linux
Hi
I need to identify a newly attached LUN from NetApp on a linuxserver running uname -o
GNU/Linux
I have first run the df -h and got the following:
df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_outsystemdb-lv_root
50G 2.7G 45G ... (3 Replies)
Discussion started by: fretagi
3 Replies
2. Solaris
Hi
I have NetApp lun, that was mounted on server as a file system that failed, and that server is no longer in use, but I would like to use that file system on another server. The NetApp Admin, told me he can present that lun to my other system, but my problem is how to mount it? Because that... (8 Replies)
Discussion started by: fretagi
8 Replies
3. Solaris
So,
We have a Netapp storage solution. We have Sparc T4-4s running with LDOMS and client zones in the LDOMS, We are using FC for storage comms. So here's the basic setup
FC luns are exported to the primary on the Sparc box. using LDM they are then exported to the LDOM using vdisk. at the... (4 Replies)
Discussion started by: os2mac
4 Replies
4. AIX
Hi,
I have aix 6.1 box. I want to configure iscsi luns from netapp storage. I tried in google but not getting proper solution for that. i m not getting the proper iqn name.
Please share me the steps to complete this requirements.
Thanks in advance. (1 Reply)
Discussion started by: sunnybee
1 Replies
5. UNIX for Advanced & Expert Users
I have seen a few threads / posts on the forum's but nothing specific to what Iam after. So Iam hoping you can help.
Issue : Iam hoping to remove unused emc luns from my solaris servers , T2000 (5.10 Generic_142900-02). I have a list of the process I have followed for the removal of the luns.... (3 Replies)
Discussion started by: furby
3 Replies
6. Solaris
Hi all
We have a couple of solaris zones running a jboss app in a cluster. Each zone has a shared netapp volume mounted to /app/xxx with everything under that subdir apart from jboss which is local to each zone in /app/jboss-3.2.5
There is a symlink in /app/xxx/jboss-3.2.5 which points to... (0 Replies)
Discussion started by: skewbie
0 Replies
7. Solaris
Hi,
I'm connecting a Solaris 10 server to a Netapp filer with two single port Emulex (Sun StorageTek PCI-X Enterprise 4GB FC HBA) HBAs. After physically installing both these HBAs what do I ned to do within Solaris 10 to enable them and configure them with persistent bindings.
Do I need... (6 Replies)
Discussion started by: gwhelan
6 Replies
8. Solaris
Hi,
I need to increase a veritas filesystem I have currently mounted on a Solaris 10 server. We can resize the LUN on the NetApp filer no problem. What I need to know is what do I do next on the Solaris 10 server I have so that it will see the increase in size. Do I run 'devfsadm' to... (3 Replies)
Discussion started by: gwhelan
3 Replies
9. Solaris
I have this problem when i integrate a new san switch in DFM 3.01 R1 :
dfm fcswitch add switchname1
Error: Host switchname2 (11197) already exists.
switchname2 is a similar san switch but in another fabric, switchname2 is already integrated in DFM database.
Bests Regards
Olivier (2 Replies)
Discussion started by: omainfroy
2 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - reboot the system immediately
SYNOPSIS
reboot [-f]
DESCRIPTION
Reboot can be used to reboot the system after installing a new kernel. It does not inform the users, but does log it's actions in
/usr/adm/wtmp and /usr/adm/authlog. The system is then rebooted with the reboot(2) systemcall.
If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call.
If the wtmp file exists, reboot logs itself as if it were a shutdown. This is done to prevent last(1) from talking about system-crashes.
Reboot is registered as is in the authlog file.
Reboot can only be executed by the super-user. Any other caller will be refused, either by reboot(8) or by reboot(2).
SEE ALSO
reboot(2), shutdown(8), halt(8), boot(8).
BUGS
The error message's given by reboot are not always useful. There are several routines that can fail, but which are not fatal for the pro-
gram.
AUTHOR
Edvard Tuinder (v892231@si.hhs.NL)
REBOOT(8)