Sponsored Content
Special Forums Hardware Filesystems, Disks and Memory mounting filesystem twice on Solaris Post 302324054 by achenle on Tuesday 9th of June 2009 07:30:48 PM
Old 06-09-2009
ZFS will complain if you try and mount a file system twice.

UFS won't put out any messages if multiple hosts mount the same file system, and I assume it could panic your host if more than one host were to write to it at the same time.

If you're concerned about multiple hosts accessing your file systems, you could mask LUNs on your at the switch (as noted above) or at the storage itself, depending on your configuration.
 

10 More Discussions You Might Find Interesting

1. BSD

mounting filesystem error

I get error that I have to rund fsck manually on my filesystem, but when I go to run fsck on filesystem ad1s1e I get an error that says can't open device not configured so fsck won't rund on that filesystem. I am only booting up in single user mode. I noticed when I look in the fstab file the... (1 Reply)
Discussion started by: rbizzell
1 Replies

2. Red Hat

Mounting NTFS filesystem

I'm currently running dual boot Linux & Windows. Linux is Fedora core 3. I've downloaded and installed the rmp that was needed so that I could mount a NTFS filesystem. But when I go to mount the filesystem I'm still getting error's stating it does not support the NTFS filesystem. Also the... (9 Replies)
Discussion started by: woofie
9 Replies

3. Solaris

filesystem mounting

Hi all, I have a question regarding filesystem mounting. I have one Sun box(V240) and a NAS on a network. Sun machine shows the following output of df -k command. # df -k Filesystem kbytes used avail capacity Mounted on /dev/md/dsk/d0 11094316 8509226 2474147 78% ... (2 Replies)
Discussion started by: prashantchavan
2 Replies

4. Shell Programming and Scripting

Looking for a way to have a portable filesystem (or mounting without root)

I have a free software project I'm working on that provides portable versions of Linux applications capable of being carried around on removable media, with settings and documents traveling along. While developing the portable launcher, I fell into a problem: FAT32 partitions do not support... (2 Replies)
Discussion started by: dkulchenko
2 Replies

5. Red Hat

Mounting Windows Filesystem

i am new to linux i want to know how to create ntfs partition and mount all windows drives in linux please help me (2 Replies)
Discussion started by: arunkmohan18
2 Replies

6. Solaris

Need help on filesystem mounting

Hi techies, I am pretty new to Solaris. So the qstn might be a silly one. I had a local disk with Solaris installed. I have done ufsdump to a SAN disk and after that s3 and s7 slices are giving the following error : "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY." I had the following... (4 Replies)
Discussion started by: manojsomanath
4 Replies

7. Solaris

Problem mounting iscsi filesystem

Hi, I have a strange problem with iscsi. My vfstab entry looks like this: /dev/md/dsk/d100 /dev/md/rdsk/d100 /zones/ssapp0895v01 ufs 2 iscsi - After rebooting, the filesystem gets mounted with the option "nosetuid". I believe the default should be "suid" /zones/ssapp0895v01 on... (0 Replies)
Discussion started by: alvaro66
0 Replies

8. Shell Programming and Scripting

Mounting filesystem

Could anyone help me please as I am stuck up. I want to mount /home/dun/maitree location of server A in server B to location /home/dun/tibco .Both server A and server B are Linux machine .The problem is that /home/dun/tibco of server B has some files and directory in it so after doing this... (1 Reply)
Discussion started by: maitree
1 Replies

9. UNIX for Dummies Questions & Answers

Mounting NFS filesystem

Hi All, I need to mount an nfs filesystem as below. xxx.xx.xx.xxx:/media/nss/Rocky Catherine/logs For the above as there is space in between the name, hoping it will not mount, if i give it with double quotes as below will it work? mount "xxx.xx.xx.xxx:/media/nss/Rocky... (2 Replies)
Discussion started by: Rockyc3400
2 Replies

10. AIX

Mounting a directory in a filesystem

Hi All, Recently I came to know my / root file system is getting full because of application directory /siebel/ I have one option. 1) Down the application , take full backup 2)change the filesystem ownership 2)copy the contents into that filesystem cp -pr /siebel/* /siebelfs/* 3)Inform... (9 Replies)
Discussion started by: Thala
9 Replies
mount.diod(8)							       diod							     mount.diod(8)

NAME
mount.diod - mount diod file systems SYNOPSIS
mount.diod [OPTIONS] host[:aname] dir [-o options] DESCRIPTION
mount.diod is the mount utility for the distributed I/O daemon, which is an I/O forwarding service for Linux clusters built upon the Linux 9p file system. mount.diod performs two main tasks: 1) connect and authenticate to the diod server, and 2) issue the mount(2) system call with appropriate mount options. Authentication with the diod server takes place in user space. The connected (and authenticated) file descriptor is passed as a mount option to the kernel 9p file system This command requires root to execute the mount(2) system call. The 9p file system must support the 9P2000.L protocol variant, e.g. kernel 2.6.38 or above. The host portion of the mount spec may optionally be supplied in hostlist format, e.g. host1,host2,host3:aname or host[1-3]:aname, in which case hosts are tried in order until a successful connection is obtained. Post-connect mount errors are immediately fatal. If the host portion of the mount spec begins with a forward-slash (/), it refers to the path to a UNIX domain socket. COMMAND LINE OPTIONS
-f, --fake-mount Do everything except the mount system call. -n, --no-mtab Do not update the system mtab. -v, --verbose Set verbose mode. -o, --options opt[,opt,...] Set mount options (see below). MOUNT OPTIONS
The following file system specific mount options are handled by mount.diod. aname=name The aname is the path of the exported file system on the server. It can be specified in the mount spec in host:aname format like NFS, or it can be specified with this option. diod will not allow an attach to an empty aname. diod has a built-in synthetic con- trol file system that can be mounted with aname of ctl. uname=name The user name to authenticate to the diod server. The default is uname=root. access=mode Select the access mode. access=user (default) causes the mount to support multiple users, and requires root authentication. access=<uid> restricts access at the client to only the specified user. port=n Connect to the diod server on the specified port. The default is the IANA-assigned 9pfs port 564. trans=name Select a transport. mount.diod only supports trans=fd because of its strategy for authentication. rfdno=n,wfdno=n The file descriptor for reading and writing with trans=fd. If set, mount.diod assumes this file descriptor is already connected to a diod server and ignores host in the device specification, and the port=n option. msize=n The msize is the max 9P packet payload size. The default is 65512 (65536-24) version=name Select 9P protocol version. diod only supports 9p2000.L. cache=mode Specify a caching policy. By default, no caches are used. If cache=loose, no attempts are made at consistency. This mode is intended for exclusive, read-only mounts. If cache=fscache, use FS-Cache for a persistent, read-only cache backend. cachetag In the context of cache=fscache, select the cache tag to use for this session. Cache tags for existing cache sessions are listed in /sys/fs/9p/caches. nodevmap Do not map special files. Represent them as normal files. This can be used to share devices/named pipes/sockets between hosts. debug=n Specifies debug level for the kernel 9p module. The debug level is a bitmask. 0x01 = display verbose error messages 0x02 = developer debug (DEBUG_CURRENT) 0x04 = display 9p trace 0x08 = display VFS trace 0x10 = display Marshalling debug 0x20 = display RPC debug 0x40 = display transport debug 0x80 = display allocation debug 0x100 = display protocol message debug 0x200 = display Fid debug 0x400 = display packet debug 0x800 = display fscache tracing debug The debug level is global, i.e. it applies to all 9P file systems and it remains set after the file system is unmounted. The default is debug=0. SEE ALSO
diod (8) diod-1.0.13 2012-05-22 mount.diod(8)
All times are GMT -4. The time now is 01:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy