Sponsored Content
Full Discussion: dev/sda1 100% full
Top Forums UNIX for Dummies Questions & Answers dev/sda1 100% full Post 302450685 by ruisof on Friday 3rd of September 2010 12:26:59 PM
Old 09-03-2010
dev/sda1 100% full

Hi!

I have a problem with my disk, it is full as you can see
Code:
[root@moodle ~]# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1             64380356  63125180         0 100% /
none                   3116000         0   3116000   0% /dev/shm
/dev/sdb1            282015652 179367500  88322592  68% /opt
//10.14.0.200/Moodle 1465122816 585728000 879394816  40% /mnt/CI_BACKUPS

i already use the command
Code:
[root@moodle /]# du -sh * 5.3M    bin
17M     boot
168K    dev
59M     etc
0       forcefsk
4.4M    home
8.0K    initrd
199M    lib
16K     lost+found
16K     media
8.0K    misc
160G    mnt
171G    opt
du: `proc/27382/task': No such file or directory
du: `proc/27382/fd': No such file or directory
du: `proc/28980': No such file or directory
du: `proc/28981': No such file or directory
du: `proc/28982': No such file or directory
du: `proc/28983': No such file or directory
du: `proc/28984': No such file or directory
900M    proc
282M    root
16M     sbin
8.0K    selinux
8.0K    srv
0       sys
4.0M    tmp
2.9G    usr
4.5G    var

and from here i can see the problem, but the fact is that my /dev/sda1 is saying that is full.
i have mysql and clamav instaled and because of this they don't work and people can acess the data in the pc.

i detect, when i try to put files in /var/spool that there is no space, but i tried to cut some files and paste again and give me the same error, i don't understand what is happening and where is the problem,can anyone give a help i'am new in this, this system was mounted by another person and he is unaviable.

thanks in advance

Last edited by pludi; 09-03-2010 at 02:17 PM.. Reason: code tags, please...
 

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
chroot(8)						      System Manager's Manual							 chroot(8)

NAME
chroot - Changes the root directory of a command SYNOPSIS
/usr/sbin/chroot directory command DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in effect, directory is relative to the current root of the running process. Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file system and the relevant pathnames for the files map correctly in the new root file system. For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and /etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on description files produced by the ctab command may also fail if the required description files are not present in the new root file system. The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe- cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new root file system in the appropriate locations. EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec- ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among others) on the new root file system. Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial root file system. To create a file relative to the original root rather than the new one, use this syntax and enter: chroot directory command > file CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite the file system. FILES
Specifies the command path. RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1) Functions: chdir(2), chroot(2) exec(2) delim off chroot(8)
All times are GMT -4. The time now is 04:34 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy