Sponsored Content
Full Discussion: mount points
Top Forums UNIX for Advanced & Expert Users mount points Post 20584 by thehoghunter on Monday 29th of April 2002 03:11:12 PM
Old 04-29-2002
It doesn't seem like Solaris has that problem. I tried and mounted 18 different partitions on a normally built Solaris server - with no problem. And we have systems with over 30 different partitions (DiskSuite and Veritas involved which is why I tested just normal UFS mounts).

..SUN's answer to the question "the limit (if any) of how many mount points are possible?" -

Since a mountpoint is just a directory, I will explain this in terms of
directories. The maximum number of directories allowed on Solaris is limited by
the LINK_MAX parameter.

This parameter is defined as 32767 in the /usr/include/limits.h header file and
it cannot be changed.

In general, you would be hard pressed to exceed the total number of directories
you can have on a filesystem unless you are trying to make more than 32767 in
any one directory.

Since the root filesystem is treated as a directory itself, you are limited to
32767 directories off of root. Each subdirectory is also limited to 32767
subdirectories.

Since each directory can have 32k, and you can nest this as far as you like,
there is no pro-forma limit to the number of files and directories you can have,
other than the number of inodes in your file system. The number of inodes is
an unsigned long and that is 4 billion on a 32-bit system; this means for
example, that you would have to have 128,000 directories (not in any one
subdirectory) with maximum entries of 32k in them (to reach this limit). By
default you get one inode per 2kb of file system space (which is, incidently far
more than you'll ever use on just about any system).

--------------------------------------

And just for completeness, here's the entry from /usr/include/limits.h:

#define LINK_MAX 32767 /* max # of links to a single
file */

So, the 4 billion plus number is 2^32-1 or 4294967295 - the absolute maximum on
a 32-bit system - this is not negotiable as an unsigned long is 32 bits.
Regardless, you'll never exceed (or come close) to this limit as your system
will grind to a halt.
thehoghunter
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

tar using mount points

hi i tried to tar a directory in my server but it show ensufficient space. therefore i tried to save it to a mount point using tar /mountpoint/newfilename file2btar but it gives me permission denied. i am using the root account to do this. is it possible to tar files and put it to mounted... (3 Replies)
Discussion started by: legato
3 Replies

2. UNIX for Dummies Questions & Answers

Mount Points at reboot

How do I make a mount point reconnect at boot without editing /etc/fstab? Is there an option (or switch) to make this persistent when issuing the mount command from a client? (1 Reply)
Discussion started by: AIXdumb455
1 Replies

3. UNIX for Dummies Questions & Answers

NFS Mount Points

Hi Solaris 10 On server A, there is a directory called data with 10 files. This data directory has a further 3 subdirectories, gl, pay, contract (for example) On server B, I want to see the server A data directory commands used: on server A, share -F nfs -o ro -d "<description">... (1 Reply)
Discussion started by: davidra
1 Replies

4. HP-UX

Cannot unmount mount points??

When taking a snap, I have a script that stops any active snap. When running the script, I'm getting a message that u02 and u04 are already mounted. How can I find out what process(es) is/are latching on the these mount points? Thank you for your time. (1 Reply)
Discussion started by: genzbeat
1 Replies

5. UNIX for Dummies Questions & Answers

mount points are already mounted

Hi, I have some issue with the mounting/unmounting on my sun solaris box. Actually their is one script that mount the file system take the backup of databases and unmount the file system.Last week this script failed to mount the file system with the below error message: + echo fs_check.sh:... (1 Reply)
Discussion started by: biju.mp
1 Replies

6. UNIX for Advanced & Expert Users

mount points

hi, I believe a mount point does not have to be a physical disk, but rather a logical one? Is this correct? if so, how can I find out if my mount points are on different physical disks? thanks (9 Replies)
Discussion started by: JamesByars
9 Replies

7. AIX

AIX mount points (SAN)

I have a mount point that I would like to have RW on one server and RO on 2 other servers. The issue that I have is that it does not seem to update on the RO servers when I make changes on the server that is RW. Lets say I have /oracle/clone mounted RW on serverA. I am able to mount /oracle/clone... (2 Replies)
Discussion started by: seacros
2 Replies

8. Shell Programming and Scripting

Shell Script to see the mount points.

Hi all, First of all I dont even know the ABC of scripting .. But now I want a Script to see the mount points of the file systems Can any body help plsssssssss :o (1 Reply)
Discussion started by: priky
1 Replies

9. Red Hat

Mount Points? How?

Hi folks, I have been asked to performed the following: Add the following new moint points systemA:/avp and SystemB:/usr/sap/trans to be the new linux server ZZZ How can I add those mount points and how those mount points can become another linuz server?:wall::wall::wall: (2 Replies)
Discussion started by: 300zxmuro
2 Replies

10. Red Hat

Types of mount points

Hi, What are the types of mount points available in Linux machine and how to find what type of mount point is configured in my linux machine? Is mount point otherwise called as file system or do they have different meaning ? Regards, Maddy (4 Replies)
Discussion started by: Maddy123
4 Replies
lofs(7FS)							   File Systems 							 lofs(7FS)

NAME
lofs - loopback virtual file system SYNOPSIS
#include <sys/param.h> #include <sys/mount.h> int mount (const char* dir, const char* virtual, int mflag, lofs, NULL, 0); DESCRIPTION
The loopback file system device allows new, virtual file systems to be created, which provide access to existing files using alternate pathnames. Once the virtual file system is created, other file systems can be mounted within it, without affecting the original file sys- tem. However, file systems which are subsequently mounted onto the original file system are visible to the virtual file system, unless or until the corresponding mount point in the virtual file system is covered by a file system mounted there. virtual is the mount point for the virtual file system. dir is the pathname of the existing file system. mflag specifies the mount options; the MS_DATA bit in mflag must be set. If the MS_RDONLY bit in mflag is not set, accesses to the loop back file system are the same as for the underlying file system. Otherwise, all accesses in the loopback file system will be read-only. All other mount(2) options are inherited from the underlying file systems. A loopback mount of '/' onto /tmp/newroot allows the entire file system hierarchy to appear as if it were duplicated under /tmp/newroot, including any file systems mounted from remote NFS servers. All files would then be accessible either from a pathname relative to '/' or from a pathname relative to /tmp/newroot until such time as a file system is mounted in /tmp/newroot, or any of its subdirectories. Loopback mounts of '/' can be performed in conjunction with the chroot(2) system call, to provide a complete virtual file system to a process or family of processes. Recursive traversal of loopback mount points is not allowed. After the loopback mount of /tmp/newroot, the file /tmp/newroot/tmp/newroot does not contain yet another file system hierarchy; rather, it appears just as /tmp/newroot did before the loopback mount was performed (for example, as an empty directory). Examples lofs file systems are mounted using: mount -F lofs /tmp /mnt SEE ALSO
lofiadm(1M), mount(1M), chroot(2), mount(2), sysfs(2), vfstab(4), lofi(7D) WARNINGS
Loopback mounts must be used with care; the potential for confusing users and applications is enormous. A loopback mount entry in /etc/vfstab must be placed after the mount points of both directories it depends on. This is most easily accomplished by making the loop- back mount entry the last in /etc/vfstab. SunOS 5.10 10 Apr 2001 lofs(7FS)
All times are GMT -4. The time now is 09:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy