Sponsored Content
Full Discussion: Rootvg in read only state
Homework and Emergencies Emergency UNIX and Linux Support Rootvg in read only state Post 302762335 by zazzybob on Monday 28th of January 2013 10:41:58 AM
Old 01-28-2013
No - something lower-level is happening if the device entires do not exist - no manner of changes within /etc/fstab will help that. noatime stops access time being updated within inodes and is a performance boon (sometimes) - it will not delay the mounting of anything.

Does the PowerPath software log anything?
 

9 More Discussions You Might Find Interesting

1. AIX

Cloned Rootvg

New Question: The purpose of an alternate disk install is in my opinion to have a ready-to-use-backup and i've read that it is possible to install filesets or software on the cloned disk for testing purposal while the normal system is still running. The question is: how do you tell AIX (5.2... (5 Replies)
Discussion started by: kvanelshocht
5 Replies

2. AIX

mirror rootvg

Hello I have a question I have a box with Aix 5.3 with rootvg on mirror. I deleted a filesystem and I create a new one to install some software but when I type lsvg -l rootvg all my filesystems has mirror unless the new one. My question is I can mirror this fs only ??? or I have to... (9 Replies)
Discussion started by: lo-lp-kl
9 Replies

3. AIX

Anyone know how to access rootvg?

I'm trying to troubleshoot an issue with an AIX system here. I have no experience with system administration of IBM stuff. Our local admin is ... um ... not available at this time. I found something online that said enter service mode - How the heck do I do that??? Why is IBM stuff lack proper... (2 Replies)
Discussion started by: bbbngowc
2 Replies

4. AIX

extendvg and rootvg

When attempting to extend rootvg to a new physical disk I received the following message: 0516-1162 extendvg: Warning, The Physical Partition Size of 64 requires the creation of 1093 partitions for hdisk5. The limitation for volume group rootvg is 1016 physical partitions... (4 Replies)
Discussion started by: jyoung
4 Replies

5. AIX

mirroring rootvg

I would like to konw wheather below steps are sufficient for mirroring rootvg. extendvg rootvg hdisk1 mirrorvg rootvg bootlist -m normal hdisk0 hdisk1 bosboot -ad hdisk0 bosboot -ad hdisk1 or anything needs to be added. (7 Replies)
Discussion started by: manoj.solaris
7 Replies

6. Solaris

Solaris rootvg backup

Guy's how can we take rootvg bakup in soraris .. Please let me know the command Pls advice . (5 Replies)
Discussion started by: Mr.AIX
5 Replies

7. AIX

rootvg mirrored

I want to increase the size of /tmp by 1GB I know that the command is chfs -a size=+1G /tmp But the rootvg is mirrored and when I do a lsvg -p rootvg, I could see 2 disks. Will there be any impact if I increase the size of /tmp when the rootvg is mirrored ? Please advise. (1 Reply)
Discussion started by: newtoaixos
1 Replies

8. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

9. AIX

Reducing / on rootvg

The root filesystem was mirrored, someone/something stopped mirroring, and increased / and /home to ridiculous values (/ got increased to 102gb and its only using 4.3gb, so 98gb is free). Can I reduce the / (/dev/hd4) filesytem down WITHOUT corrupting the the OS? I would do a: chfs -a size=10g... (6 Replies)
Discussion started by: mrmurdock
6 Replies
SYSTEMD.MOUNT(5)						   systemd.mount						  SYSTEMD.MOUNT(5)

NAME
systemd.mount - systemd mount configuration files SYNOPSIS
systemd.mount DESCRIPTION
A unit configuration file whose name ends in .mount encodes information about a file system mount point controlled and supervised by systemd. This man page lists the configuration options specific to this unit type. See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic [Unit] and [Install] sections. The mount specific configuration options are configured in the [Mount] section. Additional options are listed in systemd.exec(5), which define the execution environment the mount(8) binary is executed in. Mount units must be named after the mount point directories they control. Example: the mount point /home/lennart must be configured in a unit file home-lennart.mount. For details about the escaping logic used to convert a file system path to a unit name see systemd.unit(5). Optionally, a mount unit may be accompanied by an automount unit, to allow on-demand or parallelized mounting. See systemd.automount(5). If an mount point is beneath another mount point in the file system hierarchy, a dependency between both units is created automatically. Mount points created at runtime independent on unit files or /etc/fstab will be monitored by systemd and appear like any other mount unit in systemd. /ETC/FSTAB Mount units may either be configured via unit files, or via /etc/fstab (see fstab(5) for details). When reading /etc/fstab a few special mount options are understood by systemd which influence how dependencies are created for mount points from /etc/fstab. If MountAuto=yes is set in system.conf (which is the default), or if comment=systemd.mount is specified as mount option, then systemd will create a dependency of type Wants from either local-fs.target or remote-fs.target, depending whether the file system is local or remote. If comment=systemd.automount is set, an automount unit will be created for the file system. See systemd.automount(5) for details. If x-systemd-device-timeout= is specified it may be used to configure how long systemd should wait for a device to show up before giving up on an entry from /etc/fstab. Specify a time in seconds or explicitly specifiy a unit as s, min, h, ms. If a mount point is configured in both /etc/fstab and a unit file, the configuration in the latter takes precedence. OPTIONS
Mount files must include a [Mount] section, which carries information about the file system mount points it supervises. A number of options that may be used in this section are shared with other unit types. These options are documented in systemd.exec(5). The options specific to the [Mount] section of mount units are the following: What= Takes an absolute path of a device node, file or other resource to mount. See mount(8) for details. If this refers to a device node, a dependency on the respective device unit is automatically created. (See systemd.device(5) for more information.) This option is mandatory. Where= Takes an absolute path of a directory of the mount point. If the mount point is not existing at time of mounting, it is created. This string must be reflected in the unit file name. (See above.) This option is mandatory. Type= Takes a string for the filesystem type. See mount(8) for details. This setting is optional. Options= Mount options to use when mounting. This takes a comma separated list of options. This setting is optional. DirectoryMode= Directories of mount points (and any parent directories) are automatically created if needed. This option specifies the file system access mode used when creating these directories. Takes an access mode in octal notation. Defaults to 0755. TimeoutSec= Configures the time to wait for the mount command to finish. If a command does not exit within the configured time the mount will be considered failed and be shut down again. All commands still running will be terminated forcibly via SIGTERM, and after another delay of this time with SIGKILL. (See KillMode= below.) Takes a unit-less value in seconds, or a time span value such as "5min 20s". Pass 0 to disable the timeout logic. Defaults to 90s. KillMode= Specifies how processes of this mount shall be killed. One of control-group, process, none. This option is mostly equivalent to the KillMode= option of service files. See systemd.service(5) for details. KillSignal= Specifies which signal to use when killing a process of this mount. Defaults to SIGTERM. SendSIGKILL= Specifies whether to send SIGKILL to remaining processes after a timeout, if the normal shutdown procedure left processes of the mount around. Takes a boolean value. Defaults to "yes". SEE ALSO
systemd(1), systemctl(8), systemd.unit(5), systemd.exec(5), systemd.device(5), mount(8) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer systemd 10/07/2013 SYSTEMD.MOUNT(5)
All times are GMT -4. The time now is 04:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy