Sponsored Content
Full Discussion: Read only error
Operating Systems Linux Red Hat Read only error Post 302410208 by ygemici on Monday 5th of April 2010 09:34:27 AM
Old 04-05-2010
hi
/usr/tmp can be separate mount from root filesystem?
and can be this read only mounted?
 

10 More Discussions You Might Find Interesting

1. Programming

Error closing read file

Every time I close a file that I opened for reading I get the following error: ”Memory fault(coredump)”. And, although it does not (I think) affect the overall process (I write another file based on the file I am reading); it is something I would rather not happen. I don't know why this is... (1 Reply)
Discussion started by: ALTRUNVRSOFLN
1 Replies

2. Programming

read/write socket error

I have client and server connected. client write and read from csock. server write and read from ssock suppose the server does : .... close(ssock); //send FIN to client othertask(); .... READ ERROR if after the server close() the client does: ... read(csock,...); ...... (2 Replies)
Discussion started by: gio
2 Replies

3. Solaris

Hard error on read, OS error = 32

Hi, I've some background programs who crash with a SIGNINT receive from anywhere and on the same time I've got the message "Hard error on read, OS error = 32" on my terminal. I don't have any experience on the level for troubelshooting. The problem can be come also from the version of oracle... (0 Replies)
Discussion started by: Franzlebord
0 Replies

4. UNIX for Dummies Questions & Answers

Error ^M not found while using read command

Hi guys, i have a script called readnametest.i had written like this # !/bin/ksh echo "enter your name please" read x; echo " your name is $x" i am getting an error like "readnametest.ksh: ^M: not found." while executing this one.Could any one please explain me on why this... (4 Replies)
Discussion started by: raoscb
4 Replies

5. Shell Programming and Scripting

Multiple files read error in Shell

Hi All, there is a script that reads multiple files in a directory starting with CTG_TMPxx where xx is an integer number. i have a problem in readin the last file. For example, if there are 10 files in that directory, 9 files are read and processed. but the 10th file, its saying as cannot read... (1 Reply)
Discussion started by: vkca
1 Replies

6. OS X (Apple)

Read-only file system error

My first post :) I deleted all the files within /system/library/startupitems to the trash bin. Now my mac snow leopard won't boot at all. All I got is the gray screen, apple logo and the spinning wheel...just spinning forever. I was able to boot in single-user mode. I'm trying to copy cp command... (14 Replies)
Discussion started by: haxum
14 Replies

7. Solaris

Error 25:Disk Read Error

Hi Guys, Wondering if anyone has seen/has a fix for this, when i try boot my system from CDROM at the solaris/ttya/ttyb selection menu i get stuck in a loop: kernel$ /boot/multiboot kernel/$isadir/unix -B install_media=cdrom,console=ttya loading "/boot/multiboot kernel/$isadir/unix -B... (0 Replies)
Discussion started by: A-Train
0 Replies

8. Solaris

How to read Encrypted Error?

Hi Experts, I have an error on my solaris 10. I would like to know how to find the root cause of error because the error like encrypted. Here is the error: Sep 28 21:02:49 eccprod SC:ci-rg:db-srv-rs: Fault monitor detected error INTERNAL_ERROR: 102 DEFAULT Action=NONE : Error in... (2 Replies)
Discussion started by: edydsuranta
2 Replies

9. Solaris

Unrecovered read error No retry

We encountered these error 2 times(e.g. Solaris 10 with NetWorker installed) with in the month of August, but we couldn't pin point the root cause, it might be bad sector, bad cable or software incompatibility? Do you experience these issue or please share your understanding about this? Thanks... (0 Replies)
Discussion started by: B@S
0 Replies

10. Shell Programming and Scripting

Read: no query process ERROR

Hi, With root user i set this in the .bashrc of user1 on machine 1 more .bashrc ./track.sh # .bashrc # Source global definitions if ; then . /etc/bashrc fi Content of track.sh are more track.sh read -p "Enter ID:" reason while ] # While string is different or empty...... (4 Replies)
Discussion started by: mohtashims
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 06:41 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy