Sponsored Content
Full Discussion: Problem with /app
Operating Systems Solaris Problem with /app Post 302725469 by hergp on Friday 2nd of November 2012 08:45:11 AM
Old 11-02-2012
If /app is a part of rpool, then mounting it in a different location won't help you. If I understand you right, your rpool is running out if space from time to time.

What you can do, is set a reservation on the root filesystem. For example:
Code:
# zfs set reservation=15g rpool/ROOT/opensolaris

After this, the root Filesystem may grow up to 15G without interference from other datasets in the same pool.

You must find out the dataset name of the root filesystem for this:
Code:
# zfs list /
NAME                     USED  AVAIL  REFER  MOUNTPOINT
rpool/ROOT/opensolaris  6,90G   123G  6,78G  /

 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mail problem (NOT Mail or Mail.app)

When I try to use the CLI mail, I get the following error. What's wrong? Welcome to Darwin! % mail root Subject: test test . EOT % /etc/mail/sendmail.cf: line 81: fileclass: cannot open /etc/mail/local-host-names: Group writable directory Do I just need to change the... (1 Reply)
Discussion started by: chenly
1 Replies

2. Programming

Deadlocked App

Hello All - We have a legacy C program running non stop on one of our servers, with several instances often running at once. Fairly regularly, one of the instances while stop outputting to the log file and will just deadlock/hang. They must be then 'kill'ed by myself. When I gdb into one of... (3 Replies)
Discussion started by: markanderson
3 Replies

3. UNIX for Advanced & Expert Users

Cygwin <--> CMD App Problem (Terminal Type?)

I'm not sure if this is the right place to post this, but here it is. We have a nightly process that runs on an HP-UX box to stop our application and backend database servers, unmount their SAN hosted file systems, and then snapshot the SAN LUNs for backup and refresh of data on "report" and... (1 Reply)
Discussion started by: deckard
1 Replies

4. Red Hat

userid with nothing to do on the os/app

Hi All, I got this userid apache with the same userid and groupid and /sbin/nologin and the /www/a home folder is empty. Can I just delete this userid? How can I investigate if userid have something to do with the application? Thanks for any comment you may add. (1 Reply)
Discussion started by: itik
1 Replies

5. Solaris

Problem building app

trying to run IPERF and i've downloaded and installed and screwed around with my path to get compilers and such available... log in as myself, go to /iperf-2.0.4 switch to su run ./configure seems to go fine, couple of no's but based on previous runs it seems to be ok... do make it goes... (3 Replies)
Discussion started by: jrich523
3 Replies

6. Programming

Wuhan Coronavirus Status App for China - Rapid Prototype using MQTT and the IoT OnOff IOS App

With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here: ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages The result turned out nice, I think. I like the look and... (10 Replies)
Discussion started by: Neo
10 Replies
SYSTEMD-VOLATILE-ROOT.SERVICE(8)                           systemd-volatile-root.service                          SYSTEMD-VOLATILE-ROOT.SERVICE(8)

NAME
systemd-volatile-root.service, systemd-volatile-root - Make the root file system volatile SYNOPSIS
systemd-volatile-root.service /lib/systemd/systemd-volatile-root DESCRIPTION
systemd-volatile-root.service is a service that replaces the root directory with a volatile memory file system ("tmpfs"), mounting the original (non-volatile) /usr inside it read-only. This way, vendor data from /usr is available as usual, but all configuration data in /etc, all state data in /var and all other resources stored directly under the root directory are reset on boot and lost at shutdown, enabling fully stateless systems. This service is only enabled if full volatile mode is selected, for example by specifying "systemd.volatile=yes" on the kernel command line. This service runs only in the initial RAM disk ("initrd"), before the system transitions to the host's root directory. Note that this service is not used if "systemd.volatile=state" is used, as in that mode the root directory is non-volatile. SEE ALSO
systemd(1), systemd-fstab-generator(8), kernel-command-line(7) systemd 237 SYSTEMD-VOLATILE-ROOT.SERVICE(8)
All times are GMT -4. The time now is 07:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy