Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 06 Jun 2003 18:32:34 -0300
From:      "Daniel C. Sobral" <dcs@tcoip.com.br>
To:        Robert Watson <rwatson@FreeBSD.ORG>
Cc:        CURRENT <freebsd-current@FreeBSD.ORG>
Subject:   Re: PANIC: FreeBSD dislikes temps (panic when mounting /tmp)
Message-ID:  <3EE10872.4060404@tcoip.com.br>
In-Reply-To: <Pine.NEB.3.96L.1030606171203.32995C-100000@fledge.watson.org>
References:  <Pine.NEB.3.96L.1030606171203.32995C-100000@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote:
> On Fri, 6 Jun 2003, Daniel C. Sobral wrote:
> 
> 
>>Robert, I cc'ed you because you are usually guilty anyway... (besides,
>>there's a ea thingy there :) 
> 
> 
> I probably am, actually :-).  Is the file system in question UFS or UFS2?

[1] dcs@dcs:/opt/home/dcs$ sudo dumpfs /dev/ad0s2f
magic   19540119 (UFS2) time    Fri Jun  6 14:06:59 2003

> To summarize the context of the crash: when UFS_EXTATTR_AUTOSTART is
> present in the kernel, UFS file systems are scanned for a ".attribute" 
> directory in the root of the file system, and then it walks into various
> subdirectories of that directory looking for attribute files to start. 
> This happens fairly early in the mount process, and it looks like the
> panic is in the UFS_DIRHASH code, so perhaps we're bumping into an
> incompletely initialized inode field of some sort.  I'll look in detail at
> this over the weekend. 
> 
> Is this during the boot, or is this later when you mount a UFS file
> system?  The trace is truncated at the bottom, I think.

On mount. fsck works, even.

As for the trace, there's the following on a simple bt:

#12 0xc0239fe1 in vfs_mount (td=0xc2643720, fstype=0xc0eb3580 "ufs", 
fspath=0xc2764280 "/tmp", fsflags=0,
     fsdata=0x0) at /usr/src/sys/kern/vfs_mount.c:1090
#13 0xc0239748 in mount (td=0x0, uap=0xd1d84d10) at 
/usr/src/sys/kern/vfs_mount.c:846
#14 0xc02eb71e in syscall (frame=
       {tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 134881775, tf_esi = 
-1077937308, tf_ebp = -1077939688, tf_isp = -774353548, tf_ebx = 
-1077939632, tf_edx = 128, tf_ecx = 0, tf_eax = 21, tf_trapno = 12, 
tf_err = 2, tf_eip = 134524695, tf_cs = 31, tf_eflags = 582, tf_esp = 
-1077939844, tf_ss = 47})
     at /usr/src/sys/i386/i386/trap.c:1023
#15 0xc02dae6d in Xint0x80_syscall () at {standard input}:138

Funny that bt full actually stops on that problem.

-- 
Daniel C. Sobral                   (8-DCS)
Gerencia de Operacoes
Divisao de Comunicacao de Dados
Coordenacao de Seguranca
VIVO Centro Oeste Norte
Fones: 55-61-313-7654/Cel: 55-61-9618-0904
E-mail: Daniel.Capo@tco.net.br
         Daniel.Sobral@tcoip.com.br
         dcs@tcoip.com.br

Outros:
	dcs@newsguy.com
	dcs@freebsd.org
	capo@notorious.bsdconspiracy.net

Kerr's Three Rules for a Successful College:
	Have plenty of football for the alumni, sex for the students,
and parking for the faculty.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EE10872.4060404>