Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

no inodes free on root?

244 views
Skip to first unread message

Louis Bertrand

unread,
Apr 18, 1999, 3:00:00 AM4/18/99
to
Help!

When I try to create a file, dir or symlink on / (root), I always get the
same error message:
"/: create/symlink failed, no inodes free"

I did a fresh install of 2.5 April 16 i386 snapshot using the floppy to
boot
and ftp from a local server. This disk previously was used in my pentium
OpenBSD box, but the controller is different (AIC-7770). The machine is a
intel 486 vesa-localbus.

I su to root to try all these:
# cd /
# touch junk
# mkdir junk
# ln -s /home/louis junk

Users attempting programs like chpass also get the same error.
I have no problem with other partitions on the same disk, or the other
disk.

I can't get the Adaptec controller (AIC-7770) to give me the CHS for the
disk, so I a going to try another fdisk (2.4, FreeBSD or M$) to see what
they say, in case this is a BIOS f-up.

Scary details below.

Thanks
--Louis

Louis Bertrand, Bowmanville, ON, Canada <lo...@signalpath.on.ca>
OpenBSD: Secure open-source operating system http://www.OpenBSD.org/


# mount
/dev/sd0a on / type ffs (local)

# df -k
/dev/sd0a 31521 14474 15471 48% /

# cat /etc/fstab
/dev/sd0a / ffs rw 1 1

# disklabel sd0
# using MBR partition 3: type A6 off 32 (0x20) size 1064928 (0x103fe0)
# /dev/rsd0c:
type: SCSI
disk: SCSI disk
label: CP30540 545MB !
flags:
bytes/sector: 512
sectors/track: 79
tracks/cylinder: 6
sectors/cylinder: 474
cylinders: 2242
total sectors: 1065912
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

16 partitions:
# size offset fstype [fsize bsize cpg]
a: 65380 32 4.2BSD 1024 8192 16 # (Cyl. 0*- 137)
b: 131298 65412 swap # (Cyl. 138 - 414)
c: 1065912 0 unused 0 0 # (Cyl. 0 - 2248*)
d: 164004 196710 4.2BSD 1024 8192 16 # (Cyl. 415 - 760)
e: 511920 360714 4.2BSD 1024 8192 16 # (Cyl. 761 - 1840)
f: 193278 872634 4.2BSD 1024 8192 16 # (Cyl. 1841 - 2248*)

#fdisk sd0
Disk: sd0 geometry: 520/64/32 [1064960 sectors]
Offset: 0 Signatures: 0xAA55,0x0
Starting Ending
#: id cyl hd sec - cyl hd sec [ start - size]
-------------------------------------------------------------------------
0: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
1: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
2: 00 0 0 0 - 0 0 0 [ 0 - 0] unused
*3: A6 0 1 1 - 519 63 32 [ 32 - 1064928] OpenBSD

# dmesg
OpenBSD 2.5 (GENERIC) #243: Fri Apr 16 09:16:34 MDT 1999
der...@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: Intel 486DX (486-class)
BIOS mem = 655360 conventional, 49283072 extended
real mem = 49938432
avail mem = 43032576
using 635 buffers containing 2600960 bytes of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(bc) BIOS, date 11/21/94
bios0: diskinfo 0xf049d00c cksumlen 1 memmap 0xf049d0a8
isa0 at mainbus0
isadma0 at isa0
wdc0 at isa0 port 0x1f0-0x1f7 irq 14
atapibus0 at wdc0
acd0 at atapibus0 drive 0: <NEC CD-ROM DRIVE:272, 4.15> ATAPI 5/cdrom removable
acd0: 689Kb/sec, 256Kb cache, audio play, 256 volume levels
ie1 at isa0 port 0x300-0x30f iomem 0xd0000-0xd7fff irq 10: address 00:aa:00:b7:ec:db, type EtherExpress 16 R1
pcppi0 at isa0 port 0x61
midi0 at pcppi0: <PC speaker>
sysbeep0 at pcppi0
lpt0 at isa0 port 0x378-0x37b irq 7
npx0 at isa0 port 0xf0-0xff: using exception 16
pccom0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, 16 byte fifo
pcvt: doreset() - got KEYB_R_RESEND response ... [one time only msg]
pcvt: doreset() - Caution - no PC keyboard detected!
vt0 at isa0 port 0x60-0x6f irq 1: ET4000, 80/132 col, color, 8 scr, unknown kbd
fdc0 at isa0 port 0x3f0-0x3f5 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
ahc0 at isa0 port 0x1c00-0x1cff irq 11: Adaptec AHA-284x SCSI (BIOS enabled)
ahc0: aic7770 >= Rev E, Single Channel, SCSI Id=7, 4 SCBs
scsibus0 at ahc0: 8 targets
ahc0: target 5 synchronous at 10.0MHz, offset = 0xf
sd0 at scsibus0 targ 5 lun 0: <IBM, CP30540 545MB !Q, ADB7> SCSI2 0/direct fixed
sd0: 520MB, 2242 cyl, 6 head, 79 sec, 512 bytes/sec, 1065912 sec total
ahc0: target 6 synchronous at 10.0MHz, offset = 0x8
sd1 at scsibus0 targ 6 lun 0: <QUANTUM, LPS340S, 020B> SCSI2 0/direct fixed
sd1: 327MB, 2337 cyl, 4 head, 71 sec, 512 bytes/sec, 670506 sec total
biomask 4840 netmask 4c40 ttymask 4cc2
root on sd0a
pctr: no performance counters in CPU
dkcsum: sd0 matched BIOS disk 80
dkcsum: sd1 matched BIOS disk 81
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
uid 0 on /: out of inodes
uid 0 on /: out of inodes
uid 0 on /: out of inodes
uid 0 on /: out of inodes
uid 0 on /: out of inodes
uid 0 on /: out of inodes
uid 0 on /: out of inodes
uid 0 on /: out of inodes


Tobias Weingartner

unread,
Apr 18, 1999, 3:00:00 AM4/18/99
to
On Sunday, April 18, Louis Bertrand wrote:
> Help!
>
> When I try to create a file, dir or symlink on / (root), I always get the
> same error message:
> "/: create/symlink failed, no inodes free"
>
> I can't get the Adaptec controller (AIC-7770) to give me the CHS for the
> disk, so I a going to try another fdisk (2.4, FreeBSD or M$) to see what
> they say, in case this is a BIOS f-up.

Inodes and fdisk have little, maybe even nothing to do with each other.
Your problem is almost certainly due to the fact that your / partition
has too many files on it.

> root on sd0a
> pctr: no performance counters in CPU
> dkcsum: sd0 matched BIOS disk 80
> dkcsum: sd1 matched BIOS disk 81
> rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
> uid 0 on /: out of inodes

Try 'df -i', and see what your "%iused" field is saying for "/". chances are
that you have /tmp, or even /var/tmp on "/", making it run out of inodes.

--Toby.
*----------------------------------------------------------------------------*
| Tobias Weingartner | Email: wein...@Wolfram.com | Wolfram Research Inc. |
| Apt B 7707-110 St. |-----------------------------| 100 Tradecenter Drive |
| Edmonton, AB | Unix Guru, Admin, Sys-Prgmr | Champaign, IL |
|----------------------------------------------------------------------------|
| %SYSTEM-F-ANARCHISM, The operating system has been overthrown |
*----------------------------------------------------------------------------*

Louis Bertrand

unread,
Apr 18, 1999, 3:00:00 AM4/18/99
to
On Sun, 18 Apr 1999, Tobias Weingartner wrote:

> Inodes and fdisk have little, maybe even nothing to do with each other.
> Your problem is almost certainly due to the fact that your / partition
> has too many files on it.
>

[...snip...]


>
> Try 'df -i', and see what your "%iused" field is saying for "/". chances are
> that you have /tmp, or even /var/tmp on "/", making it run out of inodes.
>

I don't use / for much other than system stuff, /etc and mount points:

beastie# df -i
Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on
/dev/sd0a 31521 14474 15471 48% 1232 6830 15% /
/dev/sd0d 79169 1 75210 0% 1 19709 0% /tmp
/dev/sd0e 247238 2918 231959 1% 436 60490 1% /var
/dev/sd0f 93294 16 88614 0% 16 23278 0% /home
/dev/sd1a 259159 137743 108459 56% 22086 46456 32% /usr

With the system set up this way I was able to get and unpack the ports
tree and build ssh, so the system isn't crippled...

Thanks
--Louis

PS: Wim, note new .sig.

--


Louis Bertrand, Bowmanville, ON, Canada

<lo...@signalpath.on.ca> or <lo...@odel.on.ca>

Louis Bertrand

unread,
Apr 18, 1999, 3:00:00 AM4/18/99
to
On Sun, 18 Apr 1999, Louis Bertrand wrote:

> I don't use / for much other than system stuff, /etc and mount points:
>
> beastie# df -i
> Filesystem 1K-blocks Used Avail Capacity iused ifree %iused Mounted on
> /dev/sd0a 31521 14474 15471 48% 1232 6830 15% /
> /dev/sd0d 79169 1 75210 0% 1 19709 0% /tmp
> /dev/sd0e 247238 2918 231959 1% 436 60490 1% /var
> /dev/sd0f 93294 16 88614 0% 16 23278 0% /home
> /dev/sd1a 259159 137743 108459 56% 22086 46456 32% /usr
>

Don't know what happened...
I booted off the install floppy and ran fsck_ffs -f (the file system was
marked clean). fsck coughed on phase 5, free count wrong in superblock.
I answered yes and it's fixed. I rebooted and it's OK now.

The question is: how did the filesystem get broken on a fresh install?
I'll try another machine tomorrow to convince myself it was a fluke...

Thanks
--Louis

0 new messages