NetBSD Problem Report #9382
Received: (qmail 25017 invoked from network); 9 Feb 2000 21:24:01 -0000
Message-Id: <200002091930.UAA01392@rochebonne.antioche.eu.org>
Date: Wed, 9 Feb 2000 20:30:34 +0100 (MET)
From: Manuel Bouyer <bouyer@antioche.lip6.fr>
Reply-To: bouyer@antioche.lip6.fr
To: gnats-bugs@gnats.netbsd.org
Subject: LFS panics at file system full time
X-Send-Pr-Version: 3.95
>Number: 9382
>Category: kern
>Synopsis: LFS panics at file system full time
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: kern-bug-people
>State: closed
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Feb 09 13:27:01 +0000 2000
>Closed-Date: Sun Jul 10 21:59:22 +0000 2016
>Last-Modified: Sun Jul 10 21:59:22 +0000 2016
>Originator: Manuel Bouyer
>Release: -current as of yesterday
>Organization:
Mine
>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
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: kern-bug-people->perseant
Responsible-Changed-By: perseant
Responsible-Changed-When: Thu Jun 29 10:58:46 PDT 2000
Responsible-Changed-Why:
I am responsible for LFS problems right now.
Responsible-Changed-From-To: perseant->kern-bug-people
Responsible-Changed-By: perseant
Responsible-Changed-When: Thu Nov 20 20:02:04 UTC 2003
Responsible-Changed-Why:
Trying to be realistic
Responsible-Changed-From-To: kern-bug-people->go
Responsible-Changed-By: tls
Responsible-Changed-When: Wed Mar 31 06:41:57 UTC 2004
Responsible-Changed-Why:
Because Greg is working on a closely related problem and may be able to close
out this bug (which, I think, doesn't quite exist any more in this form)
very soon.
Responsible-Changed-From-To: go->oster
Responsible-Changed-By: tls
Responsible-Changed-When: Wed Mar 31 07:13:38 UTC 2004
Responsible-Changed-Why:
I was an idiot and got Greg's email address wrong.
State-Changed-From-To: open->feedback
State-Changed-By: xtraeme@netbsd.org
State-Changed-When: Sat, 29 Apr 2006 08:12:29 +0000
State-Changed-Why:
Do you have still same problem? I believe it was fixed long time ago.
From: Greg Oster <oster@cs.usask.ca>
To: gnats-bugs@netbsd.org
Cc:
Subject: Re: kern/9382 (LFS panics at file system full time)
Date: Sat, 29 Apr 2006 09:17:02 -0600
xtraeme@netbsd.org writes:
> Synopsis: LFS panics at file system full time
>
> State-Changed-From-To: open->feedback
> State-Changed-By: xtraeme@netbsd.org
> State-Changed-When: Sat, 29 Apr 2006 08:12:29 +0000
> State-Changed-Why:
> Do you have still same problem? I believe it was fixed long time ago.
The:
panic: lfs_nextseg: no clean segments
problem still exists in -current.
Later...
Greg Oster
Responsible-Changed-From-To: oster->kern-bug-people
Responsible-Changed-By: oster@narn.netbsd.org
Responsible-Changed-When: Fri, 25 Jan 2008 16:27:39 +0000
Responsible-Changed-Why:
I havn't been looking at LFS bits in ages.
State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 04 May 2008 02:51:10 +0000
State-Changed-Why:
feedback received.
State-Changed-From-To: open->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sun, 10 Jul 2016 21:59:22 +0000
State-Changed-Why:
This no longer happens, although there are still other problems (e.g. 51275)
>Unformatted:
(Contact us)
$NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007
The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.