Sponsored Content
Operating Systems AIX /dev/hd9var/ /var what should i do. Post 302135996 by simka on Friday 14th of September 2007 02:39:21 AM
Old 09-14-2007
/dev/hd9var/ /var what should i do.

Hello

my df -k show me that the /var used 93%

Filesystem 1024-blocks Free %Used Iused %Iused Mounted on
/dev/hd4 196608 33920 83% 2253 3% /
/dev/hd2 1310720 352732 74% 25266 8% /usr
/dev/hd9var 262144 18724 93%Smilie 781 2% /var
/dev/hd3 196608 88772 55% 383 1% /tmp
/dev/hd1 196608 95496 52% 727 2% /home
/proc - - - - - /proc
/dev/hd10opt 65536 54988 17% 389 3% /opt

How ever, of i check using du command. show that /var having only 76721Kbytes.

#du -sk /varSmilie
76721 /var

Any help is really appreaciated. Thank you
Cheers.
 

10 More Discussions You Might Find Interesting

1. 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

2. 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

3. AIX

hd9var full

i have deleted qf's and df's in my /var/spool/mqueue and my /var still remains at 99% full. when i check users i get this: # fuser -xuc /var /var: 8072c(root) 18404(root) 19420c(root) 23558c(root) 24276(root) 24770(root) 25284c(svcagent) 27102c(svcagent) 30242c(root) ... (3 Replies)
Discussion started by: freeman
3 Replies

4. 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

5. 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

6. 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

7. Shell Programming and Scripting

Csh , how to set var value into new var, in short string concatenation

i try to find way to make string concatenation in csh ( sorry this is what i have ) so i found out i can't do : set string_buff = "" foreach line("`cat $source_dir/$f`") $string_buff = string_buff $line end how can i do string concatenation? (1 Reply)
Discussion started by: umen
1 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. 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

10. HP-UX

Dev/urandom and dev/random missing in HP-UX

Hi, In our HP-UX B.11.11. I could not find dev/urandom and dev/random Are all pseudo-devices implemented as device drivers, or in need to run /configure some package to install the package to have dev/urandom. Please help (4 Replies)
Discussion started by: rashi
4 Replies
GEOM_MAP(4)						   BSD Kernel Interfaces Manual 					       GEOM_MAP(4)

NAME
geom_map -- GEOM module that maps defined items as separate partitions SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file: device geom_map DESCRIPTION
The geom_map framework provides support for mapping defined parts of the media. Basically it is helpful for embedded devices where in the one continuous flash are loader, kernel and rootfs parts. geom_map allows making them available as separate parts and protects the loader from being overwritten. At boot time geom_map partitions are listed (only with bootverbose) as: MAP: 0x30000, data=0x30000 "/dev/map/bootloader" MAP: 30000x10000, data=0x10000 "/dev/map/factory" MAP: 40000x7a0000, data=0x7a0000 "/dev/map/upgrade" MAP: search key ".!/bin/sh" from 0x100000, step 0x10000 MAP: 40000x110000, data=0x110000 "/dev/map/kernel" MAP: search key ".!/bin/sh" from 0x100000, step 0x10000 MAP: 150000x690000, data=0x690000 "/dev/map/rootfs" MAP: 7e0000x20000, data=0x20000 "/dev/map/config" The current geom_map configuration can be accessed with the following sysctl(8) nodes: kern.geom.conftxt, kern.geom.confxml, and kern.geom.confdot or by using ``geom map list''. # sysctl -n kern.geom.conftxt 0 MD md0 10485760 512 u 0 s 512 f 0 fs 0 l 10485760 t malloc 0 DISK cfid0 8388608 4 hd 0 sc 0 1 MAP map/config 131072 4 i 5 o 8257536 entry 0 dsize 131072 1 MAP map/rootfs 6881280 4 i 4 o 1376256 entry 0 dsize 6881280 2 UNCOMPRESS map/rootfs.uncompress 18677760 512 1 MAP map/kernel 1114112 4 i 3 o 262144 entry 0 dsize 1114112 1 MAP map/upgrade 7995392 4 i 2 o 262144 entry 0 dsize 7995392 1 MAP map/factory 65536 4 i 1 o 196608 entry 0 dsize 65536 1 MAP map/bootloader 196608 4 i 0 o 0 entry 0 dsize 196608 Driver configuration can be done in device.hints(5). List of used parameters: at select media to attach name name of partition (will create device /dev/map/that_name) start offset from the beginning of the parent media to start of the mapped partition. This field can also have a special value "search:searchstart:searchstep:searchkey", where: searchstart offset from the beginning of the parent media where search will be started searchstep value of the increment used while searching for the partition boundary markers searchkey key which will be used to find partition boundary markers. The wildcard '.' can be used to match any character on that posi- tion end offset from the beginning of the parent media to the end of the mapped partition. This field can also have the special value "search:searchstart:searchstep:searchkey", as described above. offset offset where the data of the mapped partition begins Each record contains the start address (in bytes) from the media begin, size (in bytes), offset where the data of mapped partition begins, and the name of new device. MAP: 150000x690000, data=0x690000 "/dev/map/rootfs" 00150000 - start address 00690000 - size 00000000 - data begin from zero offset 00690000 - data size "map/rootfs" - new media will be accessible via /dev/map/rootfs dev. EXAMPLES
If we need to implement layout shown above, we need to define the following hints: hint.map.0.at="cfid0" hint.map.0.start=0x00000000 hint.map.0.end=0x00030000 hint.map.0.name="bootloader" hint.map.0.readonly=1 This defines /dev/map/bootloader at disk cfid0 starting at 0x00000000 and ending at 0x00030000, it is also marked as readonly. hint.map.1.at="cfid0" hint.map.1.start=0x00030000 hint.map.1.end=0x00040000 hint.map.1.name="factory" hint.map.2.at="cfid0" hint.map.2.start=0x00040000 hint.map.2.end=0x007e0000 hint.map.2.name="upgrade" hint.map.3.at="cfid0" hint.map.3.name="kernel" hint.map.3.start=0x00040000 hint.map.3.end="search:0x00100000:0x10000:.!/bin/sh" This defines /dev/map/kernel at disk cfid0 starting at 0x00040000, but the end position must be searched by finding the key ``.!/bin/sh'', from offset 0x00100000 to the end of media with step 0x10000. The real marker in this case is ``#!/bin/sh'', but '#' terminates the line when the hints file is parsed, so we need to use wildcard '.' instead of '#'. hint.map.4.at="cfid0" hint.map.4.name="rootfs" hint.map.4.start="search:0x00100000:0x10000:.!/bin/sh" hint.map.4.end=0x007e0000 hint.map.5.at="cfid0" hint.map.5.start=0x007e0000 hint.map.5.end=0x00800000 hint.map.5.name="config" SEE ALSO
geom(4), geom(8), sysctl(8) AUTHORS
The geom_map driver was written by Aleksandr Rybalko <ray@ddteam.net>. BSD
May 17, 2011 BSD
All times are GMT -4. The time now is 12:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy