Mount options

We have a filesystem mounted via NFS on 2 systems, both are automounted. When we run a bdf command de filesystem doesnt appear, but if we try to access to the filesystem we can. We would like to know if theres any recommendation about the mount options for filesystems.

The directory is mounted by autmount when you access that directory.
This is exact automount functionaility.
This is why you cannot see in the output of "df" command when you are not using.
The recommended NFS mount option could be ...
if you use NetApp filer as NFS server,
this techinical white paper could be helpful.
http://www.netapp.com/us/library/technical-reports/tr_3442.html
-<snip>-
Correct NFS mount options are important to provide optimal performance and system stability.
Linux®: rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,vers=3,suid,timeo=600
Solaris: rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,vers=3,suid,[forcdirectio or llock]
AIX, HP/UX rw,bg,hard,nointr,rsize=32768,wsize=32768,proto=tcp,vers=3,suid

Similar Messages

QFS mount options not getting noticed.

Hi I have a small issue it seems that none of my QFS directives are getting noticed im not sure if this is true or not but this is what I have tried and i am unable to verify that these mount options are actually taking effect..
This is QFS Version 4 revision 4.0.26FA
in my /etc/opt/SUNWsamfs/samfs.cmd I have the following options
fs = qfs1
nosuid
sync_meta = 0
qwrite
readahead = 4096
writebehind = 1024
after mounting my file system why are these options not listed in mnttab
qfs1 /qfs1 samfs dev=1d80036 1048280993
using dd/time to write data to this file system im getting the exact same performance no matter what options I set. another reason why I think these options are being ignored is the following
if I set for example fs = qfs1 and high = 70 low = 30 when I check samu [m] option I dont see those values reflected in the m output so what im asking is there anyway to verifty that my mount options are being set occordinly ?
Yes I did use mount -o nosuid,qwrite,etc.. /qfs1 still no difference and even placing the options in vfstab seems to not make any difference.
last but not lease if i do a samtrace -V while mounting my /qfs1 filesystem I see the following
00100000 readahead (1048576) <<--- still seems to use the default values 1024
00080000 writebehind (524288) <<-- 512 look @ my samfs.cmd file this should but not the value.
Any assistance would be nice.

Hi There! Sorry, it took so long to get back to you. This should help:
The samu N display shows all the mount options. You can also use the samfsinfo command to see file system build information. If the samfs.cmd options are not being picked up, make sure the file is formatted correctly (no odd characters) and is in the proper location, /etc/opt/SUNWsamfs/samfs.cmd . Then "pkill -HUP sam-fsd" to assure the daemon has picked up the file's contents, and then mount the file system.

WARNING:Expected NFS mount options: rsize =32768,wsize =32768,hard,

While using "dbua" I encountered a problem on the screen saying "cannot open the specified control file" and I was directed to see the new alert log.
The alert log has several lines with messages like:
WARNING:NFS mount of file <PATH>control01.ctl on filesystem <FS_NAME> done with incorrect options
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,
WARNING:NFS mount of file <PATH>control02.ctl on filesystem <FS_NAME> done with incorrect options
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,
WARNING:NFS mount of file <PATH>/control03.ctl on filesystem <FS_NAME> done with incorrect options
WARNING:Expected NFS mount options: rsize>=32768,wsize>=32768,hard,
ORA-00210: cannot open the specified control file
ORA-00202: control file: '<PATH>/control03.ctl'
ORA-27054: NFS file system where the file is created or resides is not mounted with correct options
The file system is actually mounted with these options: "nfs - yes rsize=4096,wsize=4096,hard,intr,vers-3".
Would someone please help to identify what is wrong ?
Thanks

Thanks for your reply.
OS is Solaris on x86-64. and we use NetApps and NFS.
I followed the instruction specified in Oracle Support DocID 781349.1 and as it turned out the order is significant.
The document specifies these mount options using this order.
rw,bg,rsize=32768,wsize=32768,hard,vers=3,nointr,timeo=600,proto=tcp,suid 0 0
** This fixed the problem
FYI, we had these options (and order):
rw,bg,hard,rsize=32768,wsize=32768,vers=3,nointr,timeo=600,proto=tcp,suid

Oracle VM Server 2.2.1 - Extra mount options for /OVS

Hi,
we would like to know how to add extra mount options (rw,hard,intr,tcp,rsize=32768,wsize=32768,timeo=600) to /OVS in Oracle VM 2.2.1.
In version 2.1.5 and lower it was possible by adding those options together with the UUID in /etc/ovs/repositories.options
How to manage mount options in Oracle VM 2.2.1? I've tried the same and no success.
Best regards and thanks in advance,
Marc Caubet

Marc Caubet wrote:
Since we have seen some I/O problems which causes high CPU Wait for some VM (those which contain postgres databases with high I/O activity) we finally decided to apply those NFS options to see if it solves the problem. If it doesn't work we will analize which options can improve the performance.Marc, why not just use the OVS' NFS mount for the system/root partition and mount an NFS volume from within the guest itself? That way, you can set all the parameters you need. Also, the netfront drivers (I'm told) are slightly more efficient that the blockfront drivers, so you could even see a performance improvement.

USB mount options in kde

Is it possible to use custom mount options for removable (usb) drives in kde4?
I'm mostly interested in -o flush option. So the actual write on the disk ocurs when copying, but not when I unmout the device.
P.S. editing fstab is not a solution! May be there is a way to amoid hal and automount using udev?

http://wiki.archlinux.org/index.php/Ude … SB_devices

Mount options for ZFS filesystem on Solaris 10

Do you know some recomendation
about mount options for SAP on Oracle
with data on ZFS filesystem?
Also recomended block size required.
We assume that file system with datafiles has 8kb block size
and offline redologs has default (128kB).
But what about ONLINE REDOLOGS?
Best regards
Andy

SUN Czech installed new production HW for one Czech customer with ZFS filesystem on data-, redo- and archivelog files.
Now we have performance problem and currently there is no SAP recomendation
for ZFS file system.
The HW which are by benchmark about tvice power has worst responses than
old hardware.
a) There is bug in Solaris 10 - ZFS buffers once allocated are not released
(generally we do not want to use buffering due to prevence of double
buffering)
b) ZFS buffers takes about 20GB (32GB total) of memory on DB server
and we are not able to define huge shared pool and db cache. (it may be possible
to set special parameter in /etc/system to reduce maximum size of ZFS buffers to e.g. 4GB )
c) We are looking for proven mount option for ZFS to enable asynchronious/concurent io for database filesystems
d) There is no proven clear answer for support of ZFS/SOLARIS/Oracle/SAP.
SAP says It is Oracle problem, Oracle does not certify filesystems from Jan2007
any more and says ask your OS provider and SUN looks happy, but performance
goes down and it is not so funny for system with 1TG DB with over 30GB grow
per month.
Andy

Readonly filesystem mount options in fstab

I am noticed when I try to use
defaults,noatime,data=writeback,nouser_xattr
as mount options in fstab for my ext4 os partition, it seems to be mounted as readonly, it works for my data partition tho so far. Why is that? I got that from a blog article somewhere on optimizing ext partitions

Um, the "defaults" option includes "rw".
https://wiki.archlinux.org/index.php/Fs … efinitions
You NEED "ro" on the APPEND line in syslinux.conf (here's why), while GRUB2 adds it automatically when you re-generate the .cfg.
https://wiki.archlinux.org/index.php/Sy … sic_Config
Last edited by DSpider (2012-08-06 14:22:42)

How to make autofs to pick up new NFS mount option?

Hi,
I've added a new mount option to an existing map auto_*. I've tried:
svcadm -v restart svc:/system/filesystem/autofs:default
svcadm -v refresh svc:/system/filesystem/autofs:default
but when checking via "mount," it still shows it's mounted before the service restart/refresh and the newly added option is not shown in the output. /etc/mnttab does not show either.
Also this is within a non-global Solaris zone if it makes a difference.
How do I make sure automount picks up the new mount options right away?
Thanks,
Edited by: ACORCL on Feb 12, 2013 4:52 PM

Yes. I restarted/refresh autofs after making a change to auto_* file (adding "llock" option to an existing mount).
I just ran "automount -v" and its output shows that mount point is remounted. However, "mount" output shows
mount_point on NFS_share list_of_options_here on Tue Feb 12 08:47:32 2013 <== which is still 9 hours ago
From where I cannot find the "llock" mount option I added in auto_* file in the "list_of_options_here" above.
If you have any suggestions, please let me know.
Thanks,

[HAL] Mount options for removable devices

I need my USB drives automounted with noatime mount options. Following the guidelines at http://wiki.archlinux.org/index.php/HAL, I created a file /usr/share/hal/fdi/policy/10osvendor/10-custom-mount-options.fdi with the following content:
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="block.is_volume" bool="true">
<match key="@block.storage_device:storage.hotpluggable" bool="true">
<merge key="volume.policy.mount_option.noatime" type="bool">true</merge>
</match>
<match key="@block.storage_device:storage.removable" bool="true">
<merge key="volume.policy.mount_option.noatime" type="bool">true</merge>
</match>
</match>
</device>
</deviceinfo>
And then restarted HAL. Even tried reboot. But my drives still won't mount with noatime. Any help is much appreciated?

[:bump:]

Best NFS mount options from Linux to Xsan?

So we are adding Linux clients to our network and I'm looking to learn the best NFS mount options to put in the fstab file. Right now they are set "defaults 0 0" and we are having problems. I assume because they are hard mounting. This is from the /proc/mounts file for one of the clients connecting to the Xsan:
10.X.X.X:/snet /snet nfs rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600, retrans=2,sec=sys,mountaddr=10.X.X.X,mountvers=3,mountport=706,mountproto=udp,ad dr=10.X.X.X 0 0
Xsan 2.2, 2 MDCs running 10.6.4, Promise Array.

So we have finally solved this. It turns out that the defaults work just fine. Our issues were solved by changing which MDC was hosting the export, dividing up the workload a bit, our primary was running out of RAM.
Secondly, I added intr and soft to the NFS options, the smoothed things out further.

Effective NFS mount options

My computer is running Mac OS X 10.7.5. I have a question regarding NFS mount options.
The following mount options are defined in /etc/nfs.conf
didymus:~ service$ cat /etc/nfs.conf
nfs.client.mount.options = tcp,rw,nfc,intr,async,rdirplus,rsize=65536,wsize=65536
nfs.client.allow_async=1
If I run the mount command, I see the following:
10.72.6.11:/ on /Volumes/10.72.6.11 (nfs, asynchronous, nodev, nosuid, mounted by service)
How do I verify the other mount options specified, intr, rsize, wsize, etc. have taken affect? I presume there is some mechanism for validating this.

Nevermind, appear to have located it: nfsstat -m appears to do the trick.

BTRFS : Subvolumes, mount options

Hello,
I took a look at btrfs, read the wiki, some guides and I have a few questions :
1) In every guide I read, even on the official wiki, the root and home subvolumes are created separately. I don't understand why since the two are "linked" it would make more sense to create the home subvolume inside the root subvolume. From what I understand it wouldn't make the snapshots harder because the subvolume children are ignored when snapshotting. Moreover since subvolume children are automatically mounted we can mount the all system in one command only, so only one line in fstab to mount everything. So why not create the subvolumes directly in the root subvolume ? The only drawback I can see is that you can't set different mounting options for the children.
2) Same goes for autodefrag option, wherever I read about btrfs and SSDs the autodefrag option is always there. I understand defragmentation for a spinning device but fail to see the usefulness on SSDs. Moreover defragmentation is really bad for SSDs as it shortens their lifespan. So the way I see it defragmentation and autodefrag only has drawbacks for SSDs. What am I missing ?
3) For the same SSD lifespan concerns I plan to not use inode_cache and space_cache by using the nospace_cache option. So my options would be :
rw,noatime,compress=lzo,ssd,discard,nospace_cache
Does that seem optimal ?
Thanks in advance,
Nolhian
Last edited by Nolhian (2014-04-29 16:36:37)

If /home is nested it may lead to confusion if you later want to mount home-snapshot-1 to /home. Keeping things separate, while not required, is still a good idea.
My mount options for my ssd-based root subvolume are: "defaults,noatime,discard,ssd,subvolid=0". I don't know where you've seen autodefrag as a standard ssd option, like you say, it doesn't make much sense for ssds.
Can't comment on the caches. There's a few threads on the mailing list that may be of interest to you though (not read them myself).
http://www.mail-archive.com/linux-btrfs … 24827.html
http://www.mail-archive.com/linux-btrfs … 30739.html
http://www.mail-archive.com/linux-btrfs … 07498.html
There's a lot more.

Strange default mount options

As I installed the basic bootstrap system, the mount options set into /etc/fstab by the pac-bootstrapper were "rw,relatime,data=ordered". Booting with those caused falling back to some emergency shell with nothing mounted. Replacing those mount options by "defaults" got things working better.
Maybe the default set "rw,relatime,data=ordered" should be checked by someone "in the know" ?
(Thanks if you bothered.)

Hi,
Thanks for your replies and info requests.
- "pac-bootstrapper" meant basically "the bootstrap program whose name begins with pac-something"... The exact name is "pacstrap". Sorry, I was a little careless there
- The file system is ext4. fstab contains two entries:
/dev/sda1 / ext4 defaults 0 1
/dev/sdb1 none swap defaults 0 1
At boot time, the system complains that the root filesystem was not configured to be mounted read-write... or approximately so, as the boot text goes by quickly. It also complained that the swap thing could not be configured.
A complaint about not being for read-write also appeared when "rw,relatime,data=ordered" was there instead of "defaults" for /dev/sda1. Not sure about the swap thing then.
I think I created the files system on /dev/sda1 using command "mkfs.ext4 -m 0 /dev/sda1".
Regards,
Vesa

Upgradinin to OES 11 sp1 ,Mount options of root

Hi
Got a Ques about
"Changing the Mount Options Before an Upgrade"
in "Preparing the Server You Are Upgrading"
I sazs
I should change to "mount by Device ID or PATH"
My partitions are
dev/sda = 200 MB boot ( = no problems to change to Device boot)
dev/sdb = 20 GB Linux LVM
made as a VG01
containing a swap volume on 1,5 GB + the rest as 18,5GB root volume
Here I cant Change anything ....in the SDB and volumes are the "device/path" options greyed out, Is this OK
It still warns me about "upgrading"
Please advice

Originally Posted by KBOYLE
Landersson wrote:
>
> Hi
> Got a Ques about
> "Changing the Mount Options Before an Upgrade"
> in "Preparing the Server You Are Upgrading"
If you only have one hard drive, I wouldn't worry about it. With two
hard drives, for example, sdb could appear as sda and vise versa.
With multiple hard drives or multiple paths to your storage device the
device name can change depending upon which one SLES encounters first.
By assigning permanent names (mount by Device ID or PATH) that won't
happen.
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
Thanks for Your anwser ,
I Doo got a serie of servers tha needs update,
all got SDA1 as boot =20 MB and the rest as LVM (SDB) Swap and root ,,, LVM just to be able to expand. all ext3
I still don't get how and where to "change"
Sorry for my extreme sluggish mind
Well My fstab looks like
/dev/VG00/swap swap swap defaults 0 0
/dev/VG00/root / ext3 acl,user_xattr 1 1
/dev/sda1 /boot ext3 acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
And
menu.lst
# Modified by YaST2. Last modification on Tue Jul 2 14:03:41 CEST 2013
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,0)/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 11 SP1 - 2.6.32.12-0.7
root (hd0,0)
kernel /vmlinuz-2.6.32.12-0.7-default root=/dev/VG00/root resume=/dev/VG00/swap
splash=silent crashkernel=128M-:64M showopts vga=0x317
initrd /initrd-2.6.32.12-0.7-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Server 11 SP1 - 2.6.32.12-0.7
root (hd0,0)
kernel /vmlinuz-2.6.32.12-0.7-default root=/dev/VG00/root showopts ide=nodma apm=off
noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset
x11failsafe vga=0x317
initrd /initrd-2.6.32.12-0.7-default
###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (fd0)
chainloader +1
devpts /dev/pts devpts mode=0620,gid=5 0 0
And bootloader
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: list(grub,lilo,none)
## Default: grub
LOADER_TYPE="grub"
DEFAULT_NAME="SUSE Linux Enterprise Server 11 SP1 - 2.6.32.12-0.7"
DEFAULT_APPEND="resume=/dev/VG00/swap splash=silent crashkernel=128M-:64M showopts"
DEFAULT_VGA="0x317"
FAILSAFE_APPEND="showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off
highres=off processor.max_cstate=1 nomodeset x11failsafe"
FAILSAFE_VGA="0x317"
XEN_KERNEL_APPEND="resume=/dev/VG00/swap splash=silent showopts"
XEN_APPEND=""
XEN_VGA="0x317"
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: yesno
## Default: no
# Should the boot cycle detection be used to
# avoid unconditional reboot cycles of not
# supervised system.
CYCLE_DETECTION="no"
## Type: integer(0:)
## Default: 1
# The number of the entry in grub's menu.lst
# which should be used on the next reboot cycle.
# Note that the first entry has the number 0.
CYCLE_NEXT_ENTRY="1"
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: list(floppy,mbr,root,boot,custom,none)
## Default: mbr
# Location of boot loader.
# For making the change effect run bootloader configuration tool
LOADER_LOCATION=""
'xxxxxxxxxxxxxxxxxxxxx
And https://www.novell.com/documentation...a/bv6uejh.html section 5.4.1 doesnt make any sense for mee

Linux RHEL 6 Oracle 11.2.0.3 RAC NFS Mount Options

Hi
Does anyone have any details as to what the mount options should be for the following please.
Oracle RAC 11.2.0.3
RHEL 6.3
NFS being used
I need to determine the mount options for both BINARIES and DATABASE FILES (temp, control, data, redo)
I know there must be a document out there that does not involve making the process as complicated as possible
Thanks FORUM

Hi,
Please check Oracle Support note 359515.1 for detail.
Cheers,
SAM L.

Mount options

Similar Messages

Maybe you are looking for