Sponsored Content
Operating Systems Solaris How to mount a NetApp snapshoot to a Solaris server? Post 302967661 by Peasant on Friday 26th of February 2016 04:40:59 AM
Old 02-26-2016
You will rescan the fabric and use mount command or import the zpool once the old lun is visible to new OS.

Just be sure it is not mounted/imported on other host(s) at the same time, since you will corrupt that data.

Also, additional steps might be required if Solaris SVM was involved (you have not specified what have you used on the former server).

Hope that helps
Regards
Peasant.
 

9 More Discussions You Might Find Interesting

1. Solaris

Use DFM Netapp 3.01 R1 on Solaris 8

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

2. UNIX for Dummies Questions & Answers

can not get netapp to mount RPC Not registered error

getting "NFS mount: netapp : RPC: Program not registered" error searched the site but none of the fixes from previous threads are helping (2 Replies)
Discussion started by: calamine
2 Replies

3. Solaris

How can I mount a ufs filesystem on a solaris 10 sparc onto a Linux server

Hi there, I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server. *I have re-compiled the linux kernel t support ufs fstype with ro mount support. filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies

4. Solaris

Can't see Netapp LUN on Solaris using LPFC after reboot.

Hi, I've just edited this post. I found the solution for this. Thanks. (0 Replies)
Discussion started by: gwhelan
0 Replies

5. Solaris

Solaris 10 / NetApp volumes - Forbidden: You don't have permission to access...

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

6. Solaris

NFS lookup failed for server netapp

Hi When trying to mount a database from Solaris, we get the error: Feb 10 09:27:22 SUNTEST nfs: NFS lookup failed for server netapp: error 11 (RPC: Server can't decode arguments) Feb 10 09:27:27 SUNTEST nfs: NFS getattr failed for server netapp: error 11 (RPC: Server can't decode... (0 Replies)
Discussion started by: wbdevilliers
0 Replies

7. AIX

CIFS/SMB mount NetApp (Windows) fileshare

Hi guys, I'm trying to mount a windows share (hosted on a NetApp filer with clustered Ontap 8.3) and I have no luck doing it. This worked before when we used an old NetApp with Ontap 7.3. Seems there is an issue with ASCII/non-unicode support. I'm wondering if anybody here has mounted... (7 Replies)
Discussion started by: mikedavis
7 Replies

8. Red Hat

Unable to mount a clone file system (NetApp)

Hi I have the following difficulty: the NetApp admin has clone one file system from one red hatserver and presented this cloned LUN into another redhat server. I can see the LUN as: fdisk -l Disk /dev/sda: 64.4 GB, 64424509440 bytes 255 heads, 63 sectors/track, 7832 cylinders Units =... (1 Reply)
Discussion started by: fretagi
1 Replies

9. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies
mount(8)						      System Manager's Manual							  mount(8)

Name
       mount, umount - mount or unmount file systems

Syntax
       /etc/mount [ options ] [ device ] [ directory ]

       /etc/umount [ options ] [ device ] [ directory ]

Description
       This  is  a  general description of the command.  Additional descriptions are provided to define the syntax and options for the NFS and UFS
       file systems.

       Each invocation of the command announces to the system that a file system is present on the device device.  The file system may be local or
       remote.	File directory must exist as a directory file.	It becomes the name of the newly mounted file system root.

       If invoked without arguments, prints the list of mounted file systems.

       Physically write-protected disks and magnetic tape file systems must be mounted read-only or an error will occur at mount time.

       General users can only mount file systems with certain restrictions.  For example, the user, other than the superuser, performing the mount
       must own the directory directory.  Furthermore, no users other than the superuser can execute or programs on the mounted file systems.	In
       addition, users other than the superuser cannot access block or special character devices such as on the mounted file systems.

       The  command  announces	to the system that the removable file system previously mounted on the specified directory is to be removed.  Only
       the person who mounted a particular file system or the superuser can unmount the file system again.

Options
       -a	   Reads the file and mounts, or unmounts, all file systems listed there.

       -f	   Fast unmount.  The option has no meaning for local file systems and directories.  However, for remote file system  types  (such
		   as  NFS),  the  option  causes  the	client	to unmount the remotely mounted file systems and directories without notifying the
		   server.  This can avoid the delay of waiting for acknowledgment from a server that is down.

       -o options  Specifies a string that is passed to the kernel and used by the specific file system's mount routine in the kernel.	 For  spe-
		   cific options, refer to the file system-specific description, such as

       -r	   Indicates  that  the  file system is to be mounted read only. To share a disk, each host must mount the file system with the -r
		   option.

       -t type	   Specifies the type of file system is being mounted.	When used with the option, the option mounts all file systems of the given
		   type found in the file.  For specific file system types, refer to the file system-specific description, such as

       -v	   Tells what did or did not happen.  (Verbose flag)

       The options for are:

       -a	   Unmounts all mounted file systems.  It may be necessary to execute twice to accomplish unmounting of all mounted file systems.

       -v	   Tells what did or did not happen.  (Verbose flag)

Restrictions
       Mounting corrupted file systems will crash the system.

Files
       File systems information table

See Also
       getmnt(2), mount(2), fstab(5), fsck(8), mount(8nfs), mount(8ufs)

																	  mount(8)
All times are GMT -4. The time now is 03:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy