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
Old 03-07-2019
[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..
 

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?... (0 Replies)
Discussion started by: renobal
0 Replies

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: "); (1 Reply)
Discussion started by: nagalenoj
1 Replies

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... (1 Reply)
Discussion started by: worthamtx
1 Replies

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... (4 Replies)
Discussion started by: saagar
4 Replies

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... (1 Reply)
Discussion started by: punitha
1 Replies

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. (1 Reply)
Discussion started by: alvinoo
1 Replies

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. (2 Replies)
Discussion started by: alvinoo
2 Replies
fd(4)							     Kernel Interfaces Manual							     fd(4)

NAME
fd - file descriptor files DESCRIPTION
The /dev/fd file system is a pseudo-file system layered beneath the Virtual File System (VFS). The file descriptor files (fd*) are those files that are accessible through file descriptors. The file descriptors use the naming convention /dev/fd/0, /dev/fd/1, /dev/fd/2 and so on up to any number. To make the /dev/fd file system known to the operating system, you must create the directory with the correct privileges, then you must mount the file system. The following steps describe how to create the directory, mount the file system both manually and automatically, and how to dismount the file system: Create the directory using the mkdir and chmod commands: mkdir /dev/fd; chmod 777 /dev/fd Mount the file system manually using the mount command: mount -t fdfs /dev/fd /dev/fd Mount the file system automatically by editing either the /etc/fstab file or the /sbin/bcheckrc file. Add the following entry to the /etc/fstab file: /dev/fd /dev/fd fdfs rw 0 0 This entry mounts the pseudodevice /dev/fd on the /dev/fd directory with read/write privileges. The file system type is fdfs and the zeros (0) in the remaining fields specify that the file system is not to be backed up nor can file system checks be performed by the fsck command as this is a virtual file system. Add the following entry to the /sbin/bcheckrc file: # # mount fdfs # echo 'Mounting /dev/fd filesystem' /sbin/mount -a -v -t fdfs Again, the /dev/fd file system should not be mounted in this manner if an entire system is to be backed up starting from the root directory. Dismount the file system using the umount command: umount /dev/fd For correct truncate() behavior on fd files, you must load your program using the -lsys5 flag. RESTRICTIONS
The /dev/fd file descriptors should not be exported. EXAMPLES
The following example show how the open and dup functions have the same effect if file descriptor n is opened: fd = open("/dev/fd/n", mode); fd = dup(n); In the above example, the open function is equal to the creat function and mode is ignored. Using the dup function, subsequent reads or writes on the fd file descriptor files fail unless the original file descriptor enables the operation. ERRORS
The following error condition exists: The file descriptor is not valid. RELATED INFORMATION
Commands: chmod(1), mkdir(1), mount(8). Functions: creat(2), dup(2), open(2). delim off fd(4)
All times are GMT -4. The time now is 06:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy