Date: Fri, 18 Nov 2005 20:30:25 +0100 From: Joerg Pernfuss <elessar@bsdforen.de> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: RELENG_6 vm_fault panic on filesystem mount Message-ID: <20051118203025.11e98f92@loki> In-Reply-To: <20051118185634.Q52197@fledge.watson.org> References: <20051118183947.24a9427b@loki> <20051118185634.Q52197@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Signature_Fri__18_Nov_2005_20_30_25_+0100_H6xJ79W=1dxR2QZe Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Fri, 18 Nov 2005 18:59:34 +0000 (GMT) Robert Watson <rwatson@FreeBSD.org> wrote: >=20 > On Fri, 18 Nov 2005, Joerg Pernfuss wrote: >=20 > > #6 0xc078806a in calltrap () > > at /usr/src/sys/i386/i386/exception.s:139 #7 0xc070c00c in > > ufsdirhash_build (ip=3D0xc5426948) > > at /usr/src/sys/ufs/ufs/ufs_dirhash.c:232 #8 0xc070f5c3 in > > ufs_lookup (ap=3D0xeabb6824) at /usr/src/sys/ufs/ufs/ufs_lookup.c:192 > > #9 0xc070d8f4 in ufs_extattr_lookup (start_dvp=3D0xc5414dd0, > > lockparent=3D0x2, dirname=3D0xd71f3000 "\002", vp=3D0xd71f3000, > > td=3D0xc5558780) at /usr/src/sys/ ufs/ufs/ufs_extattr.c:274 #10 > > 0xc070dfd6 in ufs_extattr_autostart (mp=3D0xc4ca3000, td=3D0xc5558780) > > at /usr/src/sys/ufs/ufs/ufs_extattr.c:463 #11 0xc0706fa6 in > > ffs_mount (mp=3D0xc4ca3000, td=3D0xc5558780) > > at /usr/src/sys/ufs/ffs/ffs_vfsops.c:779 #12 0xc0640d57 in > > vfs_donmount (td=3D0xc5558780, fsflags=3D0x8008, fsoptions=3D0xeabb6bf4) > > at /usr/src/sys/kern/vfs_mount.c:739 #13 0xc06427c0 in kernel_mount > > (ma=3D0xc5235240, flags=3D0x0) at pcpu.h:162 >=20 > The UFS1 extended attribute code performs directory listings, > lookups, and file operations very early in the "life cycle" of a UFS > file system in order to identify attribute backing files. We could > be looking at a bug or new negative interaction between the extended > attribute code in UFS1, dirhash, and the changes to VFS required to > get SMP VFS support in 6.x. In principle, however, the EA code waits > until everything is "ready to go" before starting on file system > I/O. Are you actively using UFS1 attributes on that file system? No, it is just my nfs exported distfiles collection. Nothing special I was aware of until recently. > Could I ask you to boot to single user mode, try mounting the file > system, then try compiling a kernel without UFS_EXTATTR and > UFS_EXTATTR_AUTOSTART, boot to single user mode, and see if you can > mount the file system successfully? I.e., compare mounting with and > without extended attributes, but on a "quiet" file system so any > existing extended attributes remain in sync. No problem, the kernel is already building. I'll post the output as soon as I have it. Joerg --=20 | /"\ ASCII ribbon | GnuPG Key ID | c7e4 d91d 64e2 6321 9988 | | \ / campaign against | 0xb248b614 | f27a 4e5b 06ce b248 b614 | | X HTML in email | .the next sentence is a lie. | | / \ and news | .the previous sentence was true. | --Signature_Fri__18_Nov_2005_20_30_25_+0100_H6xJ79W=1dxR2QZe Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDfivjTlsGzrJIthQRAi+RAJ9l9vUL5Ul3N2g8q6Uu9YRL2uTapQCfU9EF JrcwnaCatL1Kw2+Ij1WAlDs= =b64N -----END PGP SIGNATURE----- --Signature_Fri__18_Nov_2005_20_30_25_+0100_H6xJ79W=1dxR2QZe--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051118203025.11e98f92>