Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 468
  • Last Modified:

102 Gigs ufs filesystem showing full around 81 G with i-nodes 4096

Hi,
As per Vendore we have to use inode parameter inodes in Solaris 8 ufs filesystem set at 4096, This filesystem has close to 151 Meg number of files when we run fsck, Total filesystem size is 102 Gigs, but running out of room around 81 Gigs.  WHats the best soloution, should I backup, re-create with 8192 inodes number, or do not use inodes flag at all, leave it as default, or should changing the block size to 2048 would help?
0
sshujaat
Asked:
sshujaat
  • 4
  • 3
  • 2
2 Solutions
 
omarfaridCommented:
You need to backup your file system and recreate it using newfs with the -i option with lower number (since it reflects the expected file size and hence give more inodes) then restore your backup. Please see:

http://docs.sun.com/app/docs/doc/806-0625/6j9vfilrf?a=view
0
 
SaranyakkaliCommented:
i had the same issue with svm file system, it solved after recrating with block size 2048 and the file system you must need to take a backup of full volume.

refer bellow:
http://www.experts-exchange.com/OS/Unix/Solaris/Q_23803967.html
0
 
sshujaatAuthor Commented:
I have tried re-creating file system with 2048 inode also, it is still having same problem, I am using following command to create file system:

newfs -m 1 /dev/md/rdsk/d50, setting minfree to 1%
when i run fsck I get following:
root@icms-uat-ts01 # fsck /local
** /dev/md/rdsk/d50
** Last Mounted on /local
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3a - Check Connectivity
** Phase 3b - Verify Shadows/ACLs
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cylinder Groups
5990775 files, 81104620 used, 23210778 free (23210778 frags, 0 blocks, 22.2% fragmentation)

Could it be 5990775 files causing it? Below is the output of filesystem size;
/dev/md/dsk/d50      104380942 81170166 22166967    79%    /local

I would really appreciate if someone could help me out.

0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
omarfaridCommented:
but you did not use the -i option with the newfs command!
0
 
SaranyakkaliCommented:
Today morning i had the same issue.. at my end.. i did as bellow..

/dev/md/dsk/d100       825G    64M   817G     1%    /mountx

which is 8G missing..

i used as bellow..

newfs -M 0 /dev/md/dsk/d100  

that's all
0
 
SaranyakkaliCommented:
Today morning i had the same issue.. at my end.. i did as bellow..

/dev/md/dsk/d100       825G    64M   817G     1%    /mountx

which is 8G missing..

i used as bellow..

newfs -m 0 /dev/md/dsk/d100  

that's all
0
 
SaranyakkaliCommented:
Hi sshujaat,

Did you tryed  to created with as "newfs -m 0 " ?

Old:
/dev/md/dsk/d100       825G    64M   817G     1%    /mountx
New:
/dev/md/dsk/d100       825G    64M   825G     1%    /test

are you facing any issues still ?

0
 
sshujaatAuthor Commented:
When I called sun, they Eng. found a doc, which says that if you have very large number of small number of files, and re-creation & re-storing still show fragmentattion, then you try tunning file system after re-creating it and before re-stogin as follows:
tunefs -o space <raw devie name>.
What it does is preserve the space taken by i-node block which is by default is 521K.  Rest, I did same as -m 1 -i 8192 while creation of filesystem.  Filesystem was at 22.2 fragmentation, after this it is at 1.3%.

0
 
sshujaatAuthor Commented:
I want to close this question
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 4
  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now