09-03-2010
Quote:
Originally Posted by
Ikon
If a process is filling the drive and not releasing the space Rebooting the server should clear the problem.
Since the remote drive is mounted in /mnt/CI_BACKUPS make sure there are no large files in /mnt. If someone put a file in /mnt and that is taking the space rebooting will not fix the problem, and may make it hard to even login to the system after reboot.
Hi! thanks for reply
I already reboot the system, but the problem persists. The remote drive is a PC where i put the backup of data from /opt/sdb1. I don't understand the relation betwen the / and the /mnt, Are you saying that they depend one another?And is true there are large files in /mnt/CI_BACKUPS.
Thanks
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
LEARN ABOUT FREEBSD
mqueuefs
MQUEUEFS(5) BSD File Formats Manual MQUEUEFS(5)
NAME
mqueuefs -- POSIX message queue file system
SYNOPSIS
To link into kernel:
options P1003_1B_MQUEUE
To load as a kernel loadable module:
kldload mqueuefs
DESCRIPTION
The mqueuefs module will permit the FreeBSD kernel to support POSIX message queue. The module contains system calls to manipulate POSIX mes-
sage queues. It also contains a file system to implement a view for all message queues of the system. This helps users to keep track of
their message queues and make it more easily usable without having to invent additional tools.
The most common usage is as follows:
mount -t mqueuefs null /mnt/mqueue
where /mnt/mqueue is a mount point.
It is possible to define an entry in /etc/fstab that looks similar to:
null /mnt/mqueue mqueuefs rw 0 0
This will mount mqueuefs at the /mnt/mqueue mount point during system boot. Using /mnt/mqueue as a permanent mount point is not advised as
its intention has always been to be a temporary mount point. See hier(7) for more information on FreeBSD directory layout.
Some common tools can be used on the file system, e.g.: cat(1), chmod(1), chown(8), ls(1), rm(1), etc. To use only the message queue system
calls, it is not necessary for user to mount the file system, just load the module or compile it into the kernel. Manually creating a file,
for example, ``touch /mnt/mqueue/myqueue'', will create a message queue named myqueue in the kernel, default message queue attributes will be
applied to the queue. It is not advised to use this method to create a queue; it is better to use the mq_open(2) system call to create a
queue as it allows the user to specify different attributes.
To see the queue's attributes, just read the file:
cat /mnt/mqueue/myqueue
SEE ALSO
mq_open(2), nmount(2), unmount(2), mount(8), umount(8)
AUTHORS
This manual page was written by David Xu <davidxu@FreeBSD.org>.
BSD
November 30, 2005 BSD