On Wed, 21 Feb 2007, Dennis wrote:

Thanks again:


ufs
magic   11954   format  dynamic time    Wed Feb 21 14:28:15 2007
sblkno  16      cblkno  24      iblkno  32      dblkno  760
sbsize  2048    cgsize  8192    cgoffset 64     cgmask  0xffffffc0
ncg     93      size    4530330 blocks  4461120
bsize   8192    shift   13      mask    0xffffe000
fsize   1024    shift   10      mask    0xfffffc00
frag    8       shift   3       fsbtodb 1
minfree 1%      maxbpg  2048    optim   time
maxcontig 7     rotdelay 0ms    rps     60
csaddr  760     cssize  2048    shift   9       mask    0xfffffe00
ntrak   48      nsect   128     spc     6144    ncyl    1475
cpg     16      bpg     6144    fpg     49152   ipg     5824
nindir  2048    inopb   64      nspf    2
nbfree  0       ndir    15704   nifree  381641  nffree  135498
          ^                                               ^^^^^^

No blocks, only fragments free. Which means you can't create any more files. Fragmentation. There are ~130 megs in fragments but none in blocks.

There are multiple things that can lead to this. That's why I asked how many small files you have on the fs, and what the workload (wrt. to creating and deleting such small files) is.

The only way to completely prevent fragmentation is to possibly waste space - make frag/blocksize equal at creation time and you can be sure that the "df" output really reflects what's possible. Otherwise, it accounts for fragmented space. But then, fragsize == blocksize may waste space. Should you consider doing this ? Well - it depends ...

cgrotor 52      fmod    0       ronly   0       logbno  1568
rolled  2       si      1       flags   0
version 2
fs_reclaim FS_RECLAIM
Dateisystem-Status gültig,
fsclean ist -3
Blöcke verfügbar in jeder Drehposition

Localization sometimes does funny things ...

FrankH.



This message posted from opensolaris.org
_______________________________________________
ufs-discuss mailing list
[email protected]

_______________________________________________
ufs-discuss mailing list
[email protected]

Reply via email to