Subject: Re: Negative inodes in filesystem
To: David Laight <david@l8s.co.uk>
From: Neil Booth <neil@daikokuya.co.uk>
List: current-users
Date: 04/14/2004 21:42:20
David Laight wrote:-
> On Sun, Apr 11, 2004 at 10:50:41AM +0100, Neil Booth wrote:
> > For one of my filesystems, df -i gives:
> >
> > Filesystem Size Used Avail Capacity iused ifree %iused
> > Mounted on
> > /dev/wd1a 36G 33M 36G 0% -514 9439744 45501%
> > /backup
> >
> > How can this be negative? The filesystem mounts cleanly.
>
> Does the filesystem have a blocksize of 64k ?
> The FFSv2 support caused the kernel (and fsck) to get very confused
> between the superblock and first alternate.
8K by the looks of it:
bash-2.05b$ sudo dumpfs -s /dev/wd1a
file system: /dev/wd1a
endian little-endian
magic 11954 (UFS1) time Wed Apr 14 06:55:56 2004
superblock location 8192 id [ 401c2b0c 226f6487 ]
cylgrp dynamic inodes 4.4BSD sblock FFSv2 fslevel 4
nbfree 4733239 ndir 3 nifree 9440387 nffree -615
ncg 838 size 39082648 blocks 37889306
bsize 8192 shift 13 mask 0xffffe000
fsize 1024 shift 10 mask 0xfffffc00
frag 8 shift 3 fsbtodb 1
bpg 5830 fpg 46640 ipg 11264
minfree 0% optim space maxcontig 8 maxbpg 2048
symlinklen 60 contigsumsize 8
maxfilesize 0x0000400801017fff
nindir 2048 inopb 64
avgfilesize 16384 avgfpdir 64
sblkno 16 cblkno 24 iblkno 32 dblkno 1440
sbsize 2048 cgsize 8192
csaddr 1440 cssize 14336
cgrotor 0 fmod 0 ronly 0 clean 0x01
flags none
fsmnt /backup
volname swuid 0
The filesystem was almost certainly created by a userland of
about 8 months ago. I believe that is during the time that
the kernel had its superblock issues?
Neil.