[ASK] clarify some concerns regarding filesystems Post: 303031908

Sponsored Content

Operating Systems AIX [ASK] clarify some concerns regarding filesystems Post 303031908 by Phat on Thursday 7th of March 2019 07:15:56 AM

03-07-2019

Registered User

[ASK] clarify some concerns regarding filesystems

Hello,

I look at my /etc/filesystems and see these stanzas

Code:

/SUM:
        dev             = /dev/lv_sum
        vfs             = jfs2
        log             = /dev/loglv00
        mount           = true
        options         = rw
        account         = false

/var:
        dev             = /dev/hd9var
        vfs             = jfs2
        log             = /dev/hd8
        mount           = automatic
        check           = false
        type            = bootfs
        vol             = /var
        free            = false
        quota           = no

As I know, mount = true means the mountpoint will be mounted at boot time, and false mean opposite to true. But what is the meaning of automatic here? The same with true?

Assuming I have created a new volume and mount it manually to somewhere. If I want to add it to /etc/filesystem, which log I will specify like below

Code:

/dev/loglv00

is it mandatory for all the volumes? In case the NFS do we need this?

As observed in my environment, the NFS is added to /etc/filesystems without log volume.

Last edited by joeyg; 03-07-2019 at 11:48 AM..

Phat

View Public Profile for Phat

Find all posts by Phat

7 More Discussions You Might Find Interesting

1. Linux

Linux Concerns....need your help

Hi, user has an existing Server (DL380G4) with STK L80 Tapelibrary running on RHAS3 and uses NetBackup 5.1 for EBS. The user decided to add new tape library EML103e.... What are the proceedure to be followed when adding new tapelibrary? What are the things that needs to be considered?...

2. Programming

Clarify me.

Dear all, I know the use of fprintf and typecasting. But, in the following function call what is the use? why that is type casted to void? (void) fprintf(stderr, "Enter key: ");

3. Filesystems, Disks and Memory

Creating /boot partition & MBR concerns

I have 40GB HD with mepis8, swap, MBR and under flags word boot. I also have a 160 GB external with a few Linux OS, no swaps, no extended etc. I am total Linux no MS I would feel more secure by resizing that sda1 partition and creating a /boot partition with the MBR housed there. Is that a...

4. Solaris

Difference between Zones and Virtual Box-Please clarify

I am learning Solaris Zones and I have the following doubts: 1.Sun has developed both Zones concept as well as Virtual Box concept. To work in Solaris if zones method is there, what is the need for virtual box? From my little knowledge, I feel virtual box and the whole root zone are same...

5. Shell Programming and Scripting

Clarify doubt ... plz Urgent

Hi friends, I am new to UNIX. I going to transfer files using SFTP. I am writing a script and using mget . If i am using mget * means, if all the files and their sub directories are transferred or not? If suppose , the local system dose not have the sub directory then what will...

6. Linux

RPC Services Security Concerns

Hi there, I am trying to understand the how is it possible to enumerate RPC services and the common RPC services and the most-commonly found RPC vulnerability.

7. UNIX for Beginners Questions & Answers

R* Service and Security Concerns

Hi there, I would like to ask about /etc/hosts.equiv and .rhosts) and the trust relations. And the impact of poorly-configured trusted relationship.

LEARN ABOUT MOJAVE

umount

UMOUNT(8)						    BSD System Manager's Manual 						 UMOUNT(8)

NAME

     umount -- unmount filesystems

SYNOPSIS

     umount [-fv] special | node
     umount -a | -A [-fv] [-h host] [-t type]

DESCRIPTION

     The umount command calls the unmount(2) system call to remove a special device or the remote node (rhost:path) from the filesystem tree at
     the point node.  If either special or node are not provided, the appropriate information is taken from the list of filesystems provided by
     getfsent(3).

     The options are as follows:

     -a      All the filesystems described via getfsent(3) are unmounted.

     -A      All the currently mounted filesystems except the root are unmounted.

     -f      The filesystem is forcibly unmounted.  Active special devices continue to work, but all other files return errors if further accesses
	     are attempted.  The root filesystem cannot be forcibly unmounted.

     -h host
	     Only filesystems mounted from the specified host will be unmounted.  This option implies the -A option and, unless otherwise speci-
	     fied with the -t option, will only unmount NFS filesystems.

     -t type
	     Is used to indicate the actions should only be taken on filesystems of the specified type.  More than one type may be specified in a
	     comma separated list.  The list of filesystem types can be prefixed with ``no'' to specify the filesystem types for which action
	     should not be taken.  For example, the umount command:

		   umount -A -t nfs,hfs

	     umounts all currently-mounted filesystems of the type NFS and HFS.  (The -a option only unmounts entries in the /etc/fstab list.)

     -v      Verbose, additional information is printed out as each filesystem is unmounted.

NOTES

     Due to the complex and interwoven nature of Mac OS X, umount may fail often.  It is recommended that diskutil(1) (as in, ``diskutil unmount
     /mnt'') be used instead.

SEE ALSO

     unmount(2), getfsent(3), mount(8), diskutil(1)

HISTORY

     A umount command appeared in Version 6 AT&T UNIX.

4th Berkeley Distribution					    May 8, 1995 					 4th Berkeley Distribution