I see suddenly server down,i check everything ok but server down.When i restart server its working fine,but mail server down.I check inodes full 100 %
Please i cant do this perform.anyone know how to inodes 100 % full resolve this issue.
Last edited by Don Cragun; 04-22-2014 at 04:07 AM..
Reason: Add CODE tags.
Dear experts
My / directory shows 100% full. What should I do???
What is normal size and
how can I prevent it.
I am using Solaris 8 on an Ultra 60.
Thanks for your advises.
Reza (6 Replies)
Just a quick question ....as per my df -k below, I have a file system marked at 100% full, why does it say there is 44,240 kb available ??
Filesystem kbytes used avail capacity Mounted on
/dev/dsk/c0t0d0s0 2055463 1753694 240106 88% /
/proc 0 ... (1 Reply)
Hey Guys,
I need your help.
My NIS server filesystem is 100%, the NIS is running under solaris 10.
I am affraid if the server stops, it wont come up again.
Please help. (4 Replies)
I need to pull down a good bit of files for another support team for an upgrade project. I have a server.list with all of the server names.
I need to do two parts:
FIRST:
I have this example, but it does not list the server name in front of each line.
#! /bin/bash
for server in $(<... (10 Replies)
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
LEARN ABOUT SUSE
o2image
o2image(8) OCFS2 Manual Pages o2image(8)NAME
o2image - Copy or restore OCFS2 file system meta-data
SYNOPSIS
o2image [-r] [-I] device image-file
DESCRIPTION
o2image copies the OCFS2 file system meta-data from the device to the specified image-file. This image file contains the file system
skeleton that includes the inodes, directory names and file names. It does not include any file data.
This image file can be useful to debug certain problems that are not reproducible otherwise. Like on-disk corruptions. It could also be
used to analyse the file system layout in an aging file system with an eye towards improving performance.
As the image-file contains a copy of all the meta-data blocks, it can be a large file. By default, it is created in a packed format, in
which all meta-data blocks are written back-to-back. With the -r option, the user could choose to have the file in the raw (or sparse) for-
mat, in which the blocks are written to the same offset as they are on the device.
debugfs.ocfs2 understands both formats.
o2image also has the option, -I, to restore the meta-data from the image file onto the device. This option will rarely be useful to end-
users and has been written specifically for developers and testers.
OPTIONS -r Copies the meta-data to the image-file in the raw format. Use this option only if the destination file system supports sparse files.
If unsure, do not use this option and let the tool create the image-file in the packed format.
-I Restores meta-data from the image-file onto the device. CAUTION: This option could corrupt the file system.
EXAMPLES
[root@node1 ~]# o2image /dev/sda1 sda1.out
Copies metadata blocks from /dev/sda1 device to sda1.out file
[root@node1 ~] o2image -I /dev/sda1 sda1.out
Use with CAUTION. Copies meta-data blocks from sda1.out onto the /dev/sda1 device.
SEE ALSO debugfs.ocfs2(8)fsck.ocfs2(8)AUTHORS
Oracle Corporation
COPYRIGHT
Copyright (C) 2007, 2010 Oracle. All rights reserved.
Version 1.4.3 February 2010 o2image(8)