Sponsored Content
Full Discussion: dev/sda1 100% full
Top Forums UNIX for Dummies Questions & Answers dev/sda1 100% full Post 302450714 by Ikon on Friday 3rd of September 2010 02:20:29 PM
Old 09-03-2010
/mnt is a directory under /.

anything in /mnt/CI_BACKUPS does NOT takeup space on /, but anything in /mnt does take up space.

Post the output of:
Code:
 du -h --max-depth=1 --exclude=/mnt/CI_BACKUPS /mnt

 

10 More Discussions You Might Find Interesting

1. Solaris

pls help - /dev/dsk 100% full

I use the following command dk -k and get the following output: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 1587078 56546 1482920 4% / /dev/dsk/c0t0d0s6 1984230 926199 998505 49% /usr /proc 0 0 0 ... (1 Reply)
Discussion started by: indianboy08
1 Replies

2. Solaris

What is /dev/tty /dev/null and /dev/console

Hi, Anyone can help My solaris 8 system has the following /dev/null , /dev/tty and /dev/console All permission are lrwxrwxrwx Can this be change to a non-world write ?? any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies

3. AIX

/dev/hd9var full

/dev/hd9var 819200 1928 100% 12101 12% /var the filesystem is full my self being new to aix what do i do to create space (1 Reply)
Discussion started by: freeman
1 Replies

4. Filesystems, Disks and Memory

Cant' mount usb drive, /dev/sda1 not showing up

Hi, I'm trying to mount a usb drive but the path /dev/sda1 does not show up under /dev when I plug in the usb device. In fact I see no differences under /dev before and after I plugin my usb drive. Any ideas why the system is not recognizing the usb drive and how to fix? This is on a... (3 Replies)
Discussion started by: orahi001
3 Replies

5. Solaris

Lun remove, stuck in /dev/dsk and /dev/rdsk

So, we removed a LUN from the SAN and the system is refusing to remove the references to it in the /dev folder. I've done the following: devfsadm -Cv powermt -q luxadm -e offline <drive path> luxadm probe All those commands failed to remove the path. The drive stills shows up as <drive... (13 Replies)
Discussion started by: DustinT
13 Replies

6. AIX

Difference between /dev/hdisk and /dev/rhdisk

Hi, How can i check that i am using RAW devices for storage in my AIX machine... Also after adding a LUN from storage to a aix host, when i check /dev in the host, i can see both rhdisk and hdisk with same number eg: dcback1(root):/dev>ls -lrt | grep disk12 crw------- 1 root ... (4 Replies)
Discussion started by: jibujacob
4 Replies

7. AIX

Problem in /dev/hd1 and /dev/hd9var

Hello AIXians, I can't boot my AIX, it hangs and stops at the code error: 0518 After searching google, I knew the problem is due to problems in File Systems. So the solution is booting from any bootable media, then run these commands in maintenance mode: #fsck -y /dev/hd4 #fsck -y... (3 Replies)
Discussion started by: Mohannad
3 Replies

8. Shell Programming and Scripting

Automating partitioning setup of /dev/sda on /dev/sdc

Objective: To recreate the partitioning setup of /dev/sda on /dev/sdc How would I parse the below information and initialize variables (an array?) that can be used to build sgdisk commands in a script, regardless of the number of partitions? Something along the lines of: sgdisk -n... (12 Replies)
Discussion started by: RogerBaran
12 Replies

9. AIX

100% Inode full with only 67% FS full.

AIX Version 6.1 and 7.1. I understand that when the OS initially creates the FS and inodes, its pretty strict, but not always tuned to a 1:1 ratio. I see the same thing when adding a whole disk LV to a separate device. It seems that when we expand a filesystem the inodes don't get tuned... (5 Replies)
Discussion started by: mrmurdock
5 Replies

10. Red Hat

Changing grub from /dev/sda to /dev/sdb

Hi, Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
CPU(1)							      General Commands Manual							    CPU(1)

NAME
cpu - connection to cpu server SYNOPSIS
cpu [ -h server ] [ -c cmd args ... ] DESCRIPTION
Cpu starts an rc(1) running on the server machine, or the machine named in the $cpu environment variable if there is no -h option. Rc's standard input, output, and error files will be /dev/cons in the name space where the cpu command was invoked. Normally, cpu is run in an 81/2(1) window on a terminal, so rc output goes to that window, and input comes from the keyboard when that window is current. Rc's cur- rent directory is the working directory of the cpu command itself. The name space for the new rc is an analogue of the name space where the cpu command was invoked: it is the same except for architecture- dependent bindings such as /bin and the use of fast paths to file servers, if available. If a -c argument is present, the remainder of the command line is executed by rc on the server, and then cpu exits. The name space is built by running /usr/$user/lib/profile with the root of the invoking name space bound to /mnt/term. The service envi- ronment variable is set to cpu; the cputype and objtype environment variables reflect the server's architecture. FILES
The name space of the terminal side of the cpu command is mounted on the CPU side on directory /mnt/term. SOURCE
/sys/src/cmd/cpu.c SEE ALSO
rc(1), 81/2(1) BUGS
Binds and mounts done after the terminal lib/profile is run are not reflected in the new name space. CPU(1)
All times are GMT -4. The time now is 10:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy