Subject: kern/9382: LFS panics at file system full time
To: None <gnats-bugs@gnats.netbsd.org>
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
List: netbsd-bugs
Date: 02/09/2000 13:31:57
>Number: 9382
>Category: kern
>Synopsis: LFS panics at file system full time
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Feb 9 13:27:01 2000
>Last-Modified:
>Originator: Manuel Bouyer
>Organization:
Mine
>Release: -current as of yesterday
>Environment:
System: NetBSD rochebonne.antioche.eu.org 1.4R NetBSD 1.4R (ROCHEBONNE) #1: Tue Feb 8 22:17:43 MET 2000 bouyer@rochebonne.antioche.eu.org:/usr/src/1.4R/src/sys/arch/i386/compile/ROCHEBONNE i386
>Description:
While testing a IDE drive I build a LFS on it and filled it with
'dd if=/dev/zero of=/lfs/toto bs=64k' (as root). The filesystem
filled up and then the kernel printed:
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 200)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 0)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 244)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 492)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 308)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 551)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 180)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 161)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 141)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 220)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 239)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 121)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 373)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 328)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 284)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 303)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 367)
lfs_bmapv: inode 4 inlocked
lfs_fastvget: ino 4 inlocked by pid 34
lfs_markv: lfs_fastvget failed with 35 (ino 4, segment 348)
panic: lfs_nextseg: no clean segments
The 'dd' never got back any write error.
>How-To-Repeat:
dd if=/dev/zero of=toto on a LFS
>Fix:
unknown
>Audit-Trail:
>Unformatted: