Bug 132597 - [tmpfs] [panic] tmpfs-related panic while interrupting a port build on tmpfs WRKDIR
Summary: [tmpfs] [panic] tmpfs-related panic while interrupting a port build on tmpfs ...
Status: Closed FIXED
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: Jaakko Heinonen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-13 08:20 UTC by bf
Modified: 2010-01-27 16:48 UTC (History)
0 users

See Also:

Attachments
textdump.tar.0 (115.00 KB, application/octet-stream)
2009-03-13 08:28 UTC, bf 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description bf 2009-03-13 08:20:01 UTC 
A panic induced by ^C during a port build in a tmpfs /tmp; textdump to follow.
Comment 1 bf 2009-03-13 08:28:40 UTC 
The associated textdump.
Comment 2 bf 2009-03-13 11:23:41 UTC 
I should mention that this may be related to the problem
noted in:

kern/122038: [tmpfs] [panic] tmpfs: panic: tmpfs_alloc_vp: type 0xc7d2fab0 0

Regards,
          b.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2009-03-13 20:05:22 UTC 
Responsible Changed
From-To: freebsd-bugs->freebsd-fs

Over to maintainer(s).
Comment 4 ota 2009-03-14 04:42:58 UTC 
Which ports were you compiling when panic happened?

Hiro
Comment 5 bf 2009-03-14 17:31:07 UTC 
--- On Sat, 3/14/09, Yoshihiro Ota <ota@j.email.ne.jp> wrote:

> From: Yoshihiro Ota <ota@j.email.ne.jp>
> Subject: Re: kern/132597: [tmpfs] [panic] tmpfs-related panic while interrupting a port build on tmpfs WRKDIR
> To: bug-followup@FreeBSD.org
> Cc: bf2006a@yahoo.com
> Date: Saturday, March 14, 2009, 12:42 AM
> Which ports were you compiling when panic happened?
> 
> Hiro

I see now that I confused your response with my other related
PR, which I had just filed before I received your message.  I
had been building a number of ports, so I do not now recall
which one it was, sorry.  I will say that a panic of this kind,
despite the other recent serious problems with tmpfs, is rare: I
have only seen one such panic in about a year of heavy use of a
tmpfs /tmp for building ports.  That is why I didn't use a
higher priority when filing the PR.

Regards,
           b.
Comment 6 Jaakko Heinonen freebsd_committer freebsd_triage 2010-01-20 19:43:57 UTC 
State Changed
From-To: open->feedback

This looks like a duplicate of kern/122038 which has been patched. 
Can you still reproduce this after r197953?
Comment 7 Jaakko Heinonen freebsd_committer freebsd_triage 2010-01-20 19:43:57 UTC 
Responsible Changed
From-To: freebsd-fs->jh

Track.
Comment 8 Jaakko Heinonen freebsd_committer freebsd_triage 2010-01-27 16:42:37 UTC 
State Changed
From-To: feedback->closed

Submitter can't reproduce. Probably a duplicate of kern/122038.