11-12-2002
Quote:
Originally posted by Kelam_Magnus
Out of inodes means that you can't create any new files in that directory.
It would help if you posted some info about the filesystem in question. Like, How it was created? what file type it is? etc... .
Generally, if you must define inodes when the filesystem is created, the only way that I know to fix it is to save your data, blow away the filesytem and recreate and increase the # of inodes by 2x.
That's what i problably end up doing i was trying to aviod that but in this case i guess i dont have another choice.
thanks a lot i really Appreciate your help.
Thanks Jose
9 More Discussions You Might Find Interesting
1. Solaris
hi
i need to find all the files that r linked to the current file as i need to delete the file as well as few of its links :confused:
thnx in advance (1 Reply)
Discussion started by: livemyway
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. 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
4. 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
5. 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
6. Solaris
Hi Guys,
I have recently started reciving below Error message
Failed HTTPS transfer to https://supportfiles.sun.com/curl
whenever I run
/usr/local/bin/sudo /opt/SUNWexplo/bin/explorer -P -q -v
from all Servers.
Looks like the SSL certificate as Expired.
Whenever I type... (4 Replies)
Discussion started by: manalisharmabe
4 Replies
7. 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
8. Red Hat
Hi,
Please suggest steps to change grub from /dev/sda to /dev/sdb, (1 Reply)
Discussion started by: manoj.solaris
1 Replies
9. 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
LEARN ABOUT REDHAT
e2image
E2IMAGE(8) System Manager's Manual E2IMAGE(8)
NAME
e2image - Save critical ext2 filesystem data to a file
SYNOPSIS
e2image [ -r ] device image-file
DESCRIPTION
The e2image program will save critical filesystem data on the ext2 filesystem located on device to a file specified by image-file. The
image file may be examined by dumpe2fs and debugfs, by using the -i option to those programs. This can be used by an expert in assisting
the recovery of catastrophically corrupted filesystems. In the future, e2fsck will be enhanced to be able to use the image file to help
recover a badly damaged filesystem.
If image-file is -, then the output of e2image will be sent to standard output.
The -r option will create a raw image file instead of a normal image file. A raw image file differs from a normal image file in two ways.
First, the filesystem metadata is placed in the proper position so that e2fsck, dumpe2fs, debugfs, etc. can be run directly on the raw
image file. In order to minimize the amount of disk space consumed by a raw image file, the file is created as a sparse file. (Beware of
copying or compressing/decompressing this file with utilities that don't understand how to create sparse files; the file will become as
large as the filesystem itself!) Secondly, the raw image file also includes indirect blocks and data blocks, which the current image file
does not have, although this may change in the future.
It is a very good idea to periodically (at boot time and every week or so) to create image files for all of filesystems on a system, as
well as saving the partition layout (which can be generated using the using fdisk -l command). Ideally the image file should be stored on
some filesystem other that the filesystem whose data it contains, to ensure that its data is accessible in the case where the filesystem
has been badly damaged.
To save disk space, e2image creates the image file as a sparse file. Hence, if the image file needs to be copied to another location, it
should either be compressed first or copied using the --sparse=always option to GNU version of cp.
The size of an ext2 image file depends primarily on the size of the filesystems and how many inodes are in use. For a typical 10 gigabyte
filesystem, with 200,000 inodes in use out of 1.2 million inodes, the image file be approximately 35 megabytes; a 4 gigabyte filesystem
with 15,000 inodes in use out of 550,000 inodes will result in a 3 megabyte image file. Image files tend to be quite compressible; an
image file taking up 32 megabytes of space on disk will generally compress down to 3 or 4 megabytes.
AUTHOR
e2image was written by Theodore Ts'o (tytso@mit.edu).
AVAILABILITY
e2image is part of the e2fsprogs package and is available from anonymous http://e2fsprogs.sourceforge.net.
SEE ALSO
dumpe2fs(8), debugfs(8)
E2fsprogs version 1.32 November 2002 E2IMAGE(8)