Sponsored Content
Full Discussion: filesystem in solaris 8
Operating Systems Solaris filesystem in solaris 8 Post 302211879 by DukeNuke2 on Saturday 5th of July 2008 02:59:37 AM
Old 07-05-2008
/var/run is the same filesystem as swap. if you need bigger /var/run, you need to increase swap filesystem.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

solaris filesystem

Dear all can we create more than one file system in single slice? I am using solaris 8 ultra spark machine. regards S.Balu. (2 Replies)
Discussion started by: sbaloo
2 Replies

2. Filesystems, Disks and Memory

Filesystem for Linux - Solaris

Do you know how I can find detailed information on filesystems on Linux and Solaris. And I mean not only for the OS but and how it(the OS) uses the hard drives! Thank you in advance!! Solid Snake;) ;) (3 Replies)
Discussion started by: SolidSnake
3 Replies

3. Solaris

What is the command to increase filesystem on solaris

I wanted to know what is the process or command to increase a filesystem on solaris. For example the /tmp directory. (3 Replies)
Discussion started by: strikelit
3 Replies

4. Solaris

[help] filesystem error on solaris 10

Hi All, please help me about filesystem error on sun fire 245 sparc solaris 10, i have installed solaris 10 os on sun fire 245 and done with mirroring disk. but after reboot the server i having this error below shown by system : checking ufs filesystems /dev/md/rdsk/d60: is logging.... (4 Replies)
Discussion started by: bucci
4 Replies

5. Solaris

The filesystem is still full - Solaris 10!

Good morning, sir! I've a problem with FileSystem, the problem is FileSystem is full First time, I've already read carefully the sticky thread FileSystem full - What to lock for https://www.unix.com/sun-solaris/25840-filesystem-full-what-look.html And then, I will post some information of... (4 Replies)
Discussion started by: trantuananh24hg
4 Replies

6. Filesystems, Disks and Memory

mounting filesystem twice on Solaris

Hello, In a shared storage environment is their anything to stop being able to mount the same filesystem on two hosts by accident, a flag being set or something on the storage? If it did happen would one of the hosts panic? (2 Replies)
Discussion started by: Actuator
2 Replies

7. UNIX for Dummies Questions & Answers

resize a filesystem in solaris 10

i am facing a problem, i would like to resize a file system called /pcard04 i am not useing any voulme manager and we have a NETAPP center storge. what i did is root@cms-dev # df -h | grep /pcard04 /dev/dsk/c4t60A9800043346C35636F2D6D4F354743d0s0 5.2G 4.0G 1.0G 80% /pcard04 then... (1 Reply)
Discussion started by: q8devilish
1 Replies

8. Solaris

Need on Veritas filesystem, solaris

Hello Folks, Was wondering if you can help me make the following disk back online, Disk_22 auto - - error I am using Solaris 9 and veritas version 4. Anep (6 Replies)
Discussion started by: jaapar
6 Replies

9. Solaris

Solaris Filesystem

Hi, Is there a command that list the unmounted filesystems ? Thank you (4 Replies)
Discussion started by: anwesh
4 Replies

10. Solaris

Solaris Filesystem vs. Windows FileSystem

Hi guys! Could you tell me what's the difference of filesystem of Solaris to filesystem of Windows? I need to compare both. I have read some over the net but it's so much technical. Could you explain it in a more simpler term? I am new to Solaris. Hope you help me guys. Thanks! (4 Replies)
Discussion started by: arah
4 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 04:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy