Edgar, not necessarily. All directories start at 512 kb, and grow dynamically if they're used (but I'll check this when I get to work!). I'd say it's unusual for lost+found to be > 512 kb and have only experienced that scenario when an application or other sub-system has been misbehaving.
Maista,
lost+found is created by newfs... It is a root access only directory that holds lost inodes. Are you sure the disk partition is mounted to the mount point where you expect to see the lost+found directory.
you are right on linux ore aix i would not have this problem.
"mklost+found"
but on solaris i do not know how to solve this problem cause this command do not work on solaris.
mkdir lost+found
chmod/chown as appropriate
populate the lost+found directory with a few files to make it 'large' enough for fsck's use and;
delete the files it's created to leave it empty.
# (#)mklost+found.sh 5.1 (Berkeley) 5/28/85
#
PATH=/usr/bin:/usr/sbin:/etc
mkdir lost+found
cd lost+found
echo creating slots...
for i in 1 2 3 4 5 6 7 8 9 0 a b c d e f
do
cat </dev/null >$iXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
done
echo removing dummy files...
for i in 1 2 3 4 5 6 7 8 9 0 a b c d e f
do
rm $iX*
done
cd ..
echo done
ls -ld `pwd`/lost+found
As I thought. haven't tested it with Solaris though!!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.