Sponsored Content
Operating Systems Solaris Cannot tell what is filling up root (/) partition on Sol10 Post 302711265 by jlliagre on Friday 5th of October 2012 04:18:32 PM
Old 10-05-2012
Post these command output:
Code:
du -dhs /*
zfs list -t all

 

10 More Discussions You Might Find Interesting

1. Solaris

Reinstall root partition

I had Solaris 8 installed on a Ultra 10 machine but during a shutdown the root partition got corrupted. I have 3 other partitions on the drive (var, swap, home). Is there a way to reinstall the root partition without effecting the other partitions? Also, when I run format from single user mode I... (4 Replies)
Discussion started by: jbestor
4 Replies

2. UNIX for Advanced & Expert Users

freebsd /usr partition filling up, but du shows low usage

I have a freebsd email server which is running out of space on /usr. du doesn't show any large directories, but df confirms that the partition is running out of space. Is there a way to find out if there is an idle process tying up disk space. Also, what happens when /usr is full, will... (0 Replies)
Discussion started by: jjamd64
0 Replies

3. AIX

how to find whats filling up Root Directory

Hi guys I am running AIX 5.3 and a newbie to it. And I am getting reports telling me that the Root Directory is reaching almost max capacity, can someone give m some advice to find out what files are causing it to grow? , or how I can identify the growing files? Thanks (6 Replies)
Discussion started by: ryanbsc@gmail.c
6 Replies

4. Solaris

changing user password as root on LDAP client SOl10/u7

I'm fairly inexperienced with LDAP and DSEE so to build my skills I installed directory server in the global zone of my Sol 10/u7 machine and created a zone to use as a client. For some reason when I try to change a users password as root (in the client zone) with passwd -r ldap I am prompted for... (1 Reply)
Discussion started by: ilikecows
1 Replies

5. UNIX for Dummies Questions & Answers

Root filesystem filling up!

Hi all. New to the forum and new to Unix admin... / filesystem filled up and I can't find where the large files are. Any help will be apppreciated: # df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 8063580 7941745 41200 100% / /proc ... (4 Replies)
Discussion started by: jamie_collins
4 Replies

6. Solaris

increasing root / partition

Dear all, I have a root partition which is 20 G in size. I have var and /tmp as seperate file systems. But this 20 G of root is not sufficeint. I want to increase the size of the / partition. Is there any way to increase with out down time. my df -k output is Filesystem ... (4 Replies)
Discussion started by: jegaraman
4 Replies

7. Red Hat

increase root partition

i am using redhat 5.4 and my root size shows 98 %, how can i increase root size # df -h Filesystem Size Used Avail Use% Mounted on /dev/sda2 77G 16G 75G 98% / /dev/sda1 2.4G 82M 2.2G 4% /boot tmpfs 3.8G 0 3.8G 0%... (8 Replies)
Discussion started by: reply.ravi
8 Replies

8. Solaris

Root partition filling up

I have a T1000 Sparc server that has a relatively small root partition which is 24Gb and a larger partition dedicated to /export/home that is approximately 100 Gb. We have a lot of data going to /var/audit and to /var/core/corefiles. Is there any non-destructive way to redirect files from... (4 Replies)
Discussion started by: goose25
4 Replies

9. Solaris

Need to partition root

Hello guys, I am using Solaris 10 x86 OS. While installing OS i have allocated entire 10 GB space to the root. Now i am not able to create new partition it says me "out of range" or "<cylinder number> not expected". Can someone please help me to allocated a default recommended space i.e 8GB or... (2 Replies)
Discussion started by: bhargav90
2 Replies

10. SCO

Resize root partition

I have SCO Openserver 5.0.5 Root partition is 96% full and I would like to make it bigger. How can this be done? 1) Can I use 'dd' to backup 'root' and then backup '/u' to a third hard disk, then divvy the primary hard disk to have a larger 'root' filesystem (i.e. previous root + u) 2) ... (5 Replies)
Discussion started by: grips03
5 Replies
SYSTEMD-VERITYSETUP-GENERATOR(8)			   systemd-veritysetup-generator			  SYSTEMD-VERITYSETUP-GENERATOR(8)

NAME
systemd-veritysetup-generator - Unit generator for integrity protected block devices SYNOPSIS
/lib/systemd/system-generators/systemd-veritysetup-generator DESCRIPTION
systemd-veritysetup-generator is a generator that translates kernel command line options configuring integrity protected block devices (verity) into native systemd units early at boot and when configuration of the system manager is reloaded. This will create systemd- veritysetup@.service(8) units as necessary. Currently, only a single verity device may be se up with this generator, backing the root file system of the OS. systemd-veritysetup-generator implements systemd.generator(7). KERNEL COMMAND LINE
systemd-veritysetup-generator understands the following kernel command line parameters: systemd.verity=, rd.systemd.verity= Takes a boolean argument. Defaults to "yes". If "no", disables the generator entirely. rd.systemd.verity= is honored only by the initial RAM disk (initrd) while systemd.verity= is honored by both the host system and the initrd. roothash= Takes a root hash value for the root file system. Expects a hash value formatted in hexadecimal characters, of the appropriate length (i.e. most likely 256 bit/64 characters, or longer). If not specified via systemd.verity_root_data= and systemd.verity_root_hash=, the hash and data devices to use are automatically derived from the specified hash value. Specifically, the data partition device is looked for under a GPT partition UUID derived from the first 128bit of the root hash, the hash partition device is looked for under a GPT partition UUID derived from the last 128bit of the root hash. Hence it is usually sufficient to specify the root hash to boot from an integrity protected root file system, as device paths are automatically determined from it -- as long as the partition table is properly set up. systemd.verity_root_data=, systemd.verity_root_hash= These two settings take block device paths as arguments, and may be use to explicitly configure the data partition and hash partition to use for setting up the integrity protection for the root file system. If not specified, these paths are automatically derived from the roothash= argument (see above). SEE ALSO
systemd(1), systemd-veritysetup@.service(8), veritysetup(8), systemd-fstab-generator(8) systemd 237 SYSTEMD-VERITYSETUP-GENERATOR(8)
All times are GMT -4. The time now is 12:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy