09-03-2010
This is why you put / (root) in a separate partition or logical volume.
You need to delete some old logs from /var/logs/
---------- Post updated at 12:52 PM ---------- Previous update was at 12:39 PM ----------
It also looks like there is a program, probably a log, that is taking up space but hasnt released the space on the drive.
since you have a 60GB drive for sda1 but I dont count 60GB being used on it, since /opt is on sdb1 and /mnt is on a remote pc.
10 More Discussions You Might Find Interesting
1. Solaris
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
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 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
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
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
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
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
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
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
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
CFDISK(8) GNU fdisk Manual CFDISK(8)
NAME
GNU fdisk, lfdisk, gfdisk - manipulate partition tables on a hard drive
SYNOPSIS
fdisk [options] [device]
DESCRIPTION
fdisk is a disk partition manipulation program, which allows you to create, destroy, resize, move and copy partitions on a hard drive using
a menu-driven interface. It is useful for organising the disk space on a new drive, reorganising an old drive, creating space for new oper-
ating systems, and copying data to new hard disks. For a list of the supported partition types, see the --list-partition-types option
below.
It comes in two variants, gfdisk and lfdisk. Lfdisk aims to resemble Linux fdisk 2.12, while gfdisk supports more advanced disk operations,
like resizing the filesystem, moving and copying partitions. When starting fdisk, the default is to run gfdisk.
OPTIONS
-h, --help
displays a help message.
-v, --version
displays the program's version.
-L, --linux-fdisk
turns on Linux fdisk compatibility mode. This is the same as running lfdisk.
-G, --gnu-fdisk
turns off Linux fdisk compatibility mode.
-i, --interactive
where necessary, prompts for user intervention.
-p, --script
never prompts for user intervention.
-l, --list
lists the partition table on the specified device and exits. If there is no device specified, lists the partition tables on all
detected devices.
-r, --raw-list
displays a hex dump of the partition table of the disk, similar to the way Linux fdisk displays the raw data in the partition table.
-u, --sector-units
use sectors, instead of cylinders for a default unit.
-s, --size=DEVICE
prints the size of the partition on DEVICE is printed on the standard output.
-t, --list-partition-types
displays a list of supported partition types and features.
The following options are available only to lfdisk.
-b, --sector-size=SIZE
Specify the sector size of the disk. Valid values are 512, 1024 and 2048. Should be used only on older kernels, which don't guess
the correct sector size.
-C, --cylinders=CYLINDERS
Specify the number of cylinders of the disk. Currently does nothing, it is left for Linux fdisk compatibility.
-H, --heads=HEADS
Specify the number of heads of the disk. Reasonable values are 255 or 16.
-S, --sectors=SECTORS
Specify the number of sectors per track. A reasonable value is 63.
BUGS
Before editing a BSD disklabel, the partition with the disklabel should already exist on the disk and be detected by the OS. If you have
created a BSD-type partition, you need to write the changes to the disk. If fdisk fails to notify the OS about the changes in partition ta-
ble, you need to restart your computer. As fdisk tries to guess the device holding the BSD disklabel, it might fail to edit it at all, even
if the OS has detected it. In this case you are adviced to simply open the device with fdisk directly. It is possible that it doesn't work
on some operating systems.
Getting the size of a partition with -s might fail, if fdisk fails to guess the disk device, for the same reasons as with the previous bug.
SEE ALSO
mkfs(8), cfdisk(8), parted(8) The fdisk program is fully documented in the info(1) format GNU fdisk User Manual manual.
fdisk 18 August, 2006 CFDISK(8)