Deleting logfiles usually makes the situation worse -- they're probably still in use so won't be deleted, and will exist on disk until the logger closes them. But they're no longer in the directory after you delete them, preventing you from doing anything to them!
Try restarting your logger to release the deleted files, and don't delete logfiles thereafter -- truncate them. Having it open won't let the logger stop you from doing that.
Can anyone tell me how would I troubleshoot when /var becomes full with inodes? This is on HP11.11 system. Where used is 92%, ifree is 1891 iuse is 88%. Thanks. (3 Replies)
Hi Everyone,
I think I've filled up one of the partitions on my drive. I suspect that one of the applications I've been running has been spitting out junk files to this partition - most of which can be deleted. The problem is that I have no idea how to go look at what's on that partition and... (2 Replies)
Hi
If You were the systems administrator of a mail server that services approximately 3,000 users. 2,000
users access their email via a POP-3 service, while the remaining 1,000 users access their email via a
Unix mail reader. Recently users have complained about speed of disk access, so a new 10... (1 Reply)
I am currently running DesktopBSD as a live-CD and need to have a large /var partition because it is currently too small. I have a USB stick which is BSD formatted, and would like to have the /var partition moved over to it. How can this be done? Could I for instance use a symlink? (1 Reply)
hi, im new in aix administration.. months ago, I received mails, everytime a cron was executed. but now, I don't receive these mails.. and the /var/spool/squeue, gets full frequently. i'd like to know more information about this, what can i do?? sendmail is up, because, I executed ps -ef |grep... (5 Replies)
This is my first time working with ZFS on Solaris 10. I am trying to set up /var in a separate partition from /.
During the installation, I came across the ZFS settings where I selected disks 0 and 1 to be mirrored with ZFS. Next was the option to have /var and / on separate datasets.
Is... (3 Replies)
In my company ,there is a mail server that services approximately 3,000 users. 2,000 users access their email via a POP-3 service, while the remaining 1,000 users access their email via a Unix mail reader. Recently users have complained about speed of disk access, so a new 10 gigabyte
disk has... (1 Reply)
Hi,
I have Solaris-10 (having multiple non global zones running on it). Its /var is getting full to 100% and I can see, there are files getting added to /var/audit. There are large in number, so even if I clearing them, it is filling /var. In past 24 hours, there are 53000 files are added. I am... (1 Reply)
Discussion started by: solaris_1977
1 Replies
LEARN ABOUT MINIX
fdisk
FDISK(8) System Manager's Manual FDISK(8)NAME
fdisk - partition a hard disk [IBM]
SYNOPSIS
fdisk [-hm] [-sn] [file]
OPTIONS -h Number of disk heads is m
-s Number of sectors per track is n
EXAMPLES
fdisk /dev/hd0 # Examine disk partitions
fdisk -h9 /dev/hd0 # Examine disk with 9 heads
DESCRIPTION
When fdisk starts up, it reads in the partition table and displays it. It then presents a menu to allow the user to modify partitions,
store the partition table on a file, or load it from a file. Partitions can be marked as MINIX, DOS or other, as well as active or not.
Using fdisk is self-explanatory. However, be aware that repartitioning a disk will cause information on it to be lost. Rebooting the sys-
tem immediately is mandatory after changing partition sizes and parameters. MINIX, XENIX, PC-IX, and MS-DOS all have different partition
numbering schemes. Thus when using multiple systems on the same disk, be careful.
Note that MINIX, unlike MS-DOS , cannot access the last sector in a partition with an odd number of sectors. The reason that odd partition
sizes do not cause a problem with MS-DOS is that MS-DOS allocates disk space in units of 512-byte sectors, whereas MINIX uses 1K blocks.
Fdisk has a variety of other features that can be seen by typing h.
Fdisk normally knows the geometry of the device by asking the driver. You can use the -h and -s options to override the numbers found.
SEE ALSO part(8).
FDISK(8)