Sponsored Content
Operating Systems Solaris Allocating space to ufs /usr by using ZFS in solaris Post 302497639 by jlliagre on Thursday 17th of February 2011 05:13:12 PM
Old 02-17-2011
Beware that relocating the whole /usr to a zfs filesystem might possibly make your system unbootable.
Relocating parts of /usr using symbolic links (outside /usr/local which isn't part of Solaris) would likely render your system un-patchable, un-upgradeable and of certainly unsupported.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Re-allocating hard drive space

Hi, Is their an easy way to realloate hard drive space on Solaris 10. For example : /c20td0 10G /space 90 G I would like to move some of the hard-drive space from "/space" and add it to "/c20td0". In Windows this can be easily done using Partition magic, anything similar for UNIX? (4 Replies)
Discussion started by: annointed3
4 Replies

2. UNIX for Advanced & Expert Users

allocating swap space on solaris 9

Hi, I have a solaris 9-sparc box, which after bouncing is giving swap space related error messages(that swap space is not enough). could it be possible that there was some command issued or setting made before bouncing, which was lost after bouncing? please let me know how i can add swap space... (1 Reply)
Discussion started by: 0ktalmagik
1 Replies

3. Solaris

Installing ZFS on an existing Solaris 10 install (UFS)

Hello, I am new to Solaris so i apologize upfront if my questions seem trivial. I am trying to install a ZFS file system on a Solaris 10 machine with UFS already installed on it. I want to run: # zpool create pool_zfs c0t0d0 then: # zfs create pool_zfs/fs My question is more to... (3 Replies)
Discussion started by: mcdef
3 Replies

4. Linux

Allocating available space to file system

have a VMWARE machine, I have extended it from 20GB to 30GB for Linux box. The linux box shows this for df -hal: Filesystem Size Used Avail Use% Mounted on -dev-mapper-VolGroup00-LogVol00 19G 5.9G 12G 34% - proc 0 0 0 - -proc sysfs 0 0 0 - -sys devpts 0 0 0 - -dev-pts -dev-sda1 99M 13M... (1 Reply)
Discussion started by: mackman
1 Replies

5. Solaris

Convert root UFS to ZFS on x86 solaris 10/09

Hello All, Good Morning, We are trying to convert the UFS root in to ZFS. Am getting below error. Any one help me out on this ? bash-3.00# zpool list NAME SIZE USED AVAIL CAP HEALTH ALTROOT guru 5.95G 483M 5.48G 7% ONLINE - bash-3.00# zpool create rpool c2t10d0p0... (4 Replies)
Discussion started by: gowthamakanthan
4 Replies

6. UNIX for Dummies Questions & Answers

allocating space for samba users

I have installed samba by cmd yup install samba -a and configured my samba server.But i want my samba users to lo-gin from windows users and contain allocated amount of space. plz help me............ (1 Reply)
Discussion started by: yashwanthguru
1 Replies

7. UNIX for Advanced & Expert Users

Solaris 10 & 11 ZFS Space Monitoring

Hi Folks! Its been a while since I worked with ZFS but basically, I need to monitor free space for Solaris 10 & 11 systems (with & without zones) I am hoping that any space commands only need to be run from the global zone (to simplify matters) However, I'm not not sure if there are exceptions... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
SYSTEMD-FSTAB-GENERATOR(8)                                    systemd-fstab-generator                                   SYSTEMD-FSTAB-GENERATOR(8)

NAME
systemd-fstab-generator - Unit generator for /etc/fstab SYNOPSIS
/lib/systemd/system-generators/systemd-fstab-generator DESCRIPTION
systemd-fstab-generator is a generator that translates /etc/fstab (see fstab(5) for details) into native systemd units early at boot and when configuration of the system manager is reloaded. This will instantiate mount and swap units as necessary. The passno field is treated like a simple boolean, and the ordering information is discarded. However, if the root file system is checked, it is checked before all the other file systems. See systemd.mount(5) and systemd.swap(5) for more information about special /etc/fstab mount options this generator understands. One special topic is handling of symbolic links. Historical init implementations supported symlinks in /etc/fstab. Because mount units will refuse mounts where the target is a symbolic link, this generator will resolve any symlinks as far as possible when processing /etc/fstab in order to enhance backwards compatibility. If a symlink target does not exist at the time that this generator runs, it is assumed that the symlink target is the final target of the mount. systemd-fstab-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-fstab-generator understands the following kernel command line parameters: fstab=, rd.fstab= Takes a boolean argument. Defaults to "yes". If "no", causes the generator to ignore any mounts or swap devices configured in /etc/fstab. rd.fstab= is honored only by the initial RAM disk (initrd) while fstab= is honored by both the main system and the initrd. root= Takes the root filesystem to mount in the initrd. root= is honored by the initrd. rootfstype= Takes the root filesystem type that will be passed to the mount command. rootfstype= is honored by the initrd. rootflags= Takes the root filesystem mount options to use. rootflags= is honored by the initrd. mount.usr= Takes the /usr filesystem to be mounted by the initrd. If mount.usrfstype= or mount.usrflags= is set, then mount.usr= will default to the value set in root=. Otherwise, this parameter defaults to the /usr entry found in /etc/fstab on the root filesystem. mount.usr= is honored by the initrd. mount.usrfstype= Takes the /usr filesystem type that will be passed to the mount command. If mount.usr= or mount.usrflags= is set, then mount.usrfstype= will default to the value set in rootfstype=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrfstype= is honored by the initrd. mount.usrflags= Takes the /usr filesystem mount options to use. If mount.usr= or mount.usrfstype= is set, then mount.usrflags= will default to the value set in rootflags=. Otherwise, this value will be read from the /usr entry in /etc/fstab on the root filesystem. mount.usrflags= is honored by the initrd. systemd.volatile= Controls whether the system shall boot up in volatile mode. Takes a boolean argument or the special value state. If false (the default), this generator makes no changes to the mount tree and the system is booted up in normal mode. If true the generator ensures systemd-volatile-root.service(8) is run as part of the initial RAM disk ("initrd"). This service changes the mount table before transitioning to the host system, so that a volatile memory file system ("tmpfs") is used as root directory, with only /usr mounted into it from the configured root file system, in read-only mode. This way the system operates in fully stateless mode, with all configuration and state reset at boot and lost at shutdown, as /etc and /var will be served from the (initially unpopulated) volatile memory file system. If set to state the generator will leave the root directory mount point unaltered, however will mount a "tmpfs" file system to /var. In this mode the normal system configuration (i.e. the contents of "/etc") is in effect (and may be modified during system runtime), however the system state (i.e. the contents of "/var") is reset at boot and lost at shutdown. Note that in none of these modes the root directory, /etc, /var or any other resources stored in the root file system are physically removed. It's thus safe to boot a system that is normally operated in non-volatile mode temporarily into volatile mode, without losing data. Note that enabling this setting will only work correctly on operating systems that can boot up with only /usr mounted, and are able to automatically populate /etc, and also /var in case of "systemd.volatile=yes". SEE ALSO
systemd(1), fstab(5), systemd.mount(5), systemd.swap(5), systemd-cryptsetup-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-FSTAB-GENERATOR(8)
All times are GMT -4. The time now is 02:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy