Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 24 Mar 2009 18:34:02 GMT
From:      George Wenzel <gwenzel@univaud.com>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   kern/133020: inappropriate panic caused by zfs. Panic: zfs_fuid_create
Message-ID:  <200903241834.n2OIY2ja028059@www.freebsd.org>
Resent-Message-ID: <200903241840.n2OIe4hY021278@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         133020
>Category:       kern
>Synopsis:       inappropriate panic caused by zfs.  Panic: zfs_fuid_create
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 24 18:40:04 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator:     George Wenzel
>Release:        7.1 and 8.0
>Organization:
Univa UD
>Environment:
FreeBSD cfpbak01.univaud.com 8.0-CURRENT-200902 FreeBSD 8.0-CURRENT-200902 #0: Wed Mar 18 12:06:18 CDT 

2009     gwenzel@cfpbak01.univaud.com:/usr/src/sys/i386/compile/zfs  i386

>Description:
I am seeing this panic message:

Panic: zfs_fuid_create
cpuid=1
KDB: enter: Panic
[thread pid2819 tid 100215]
stopped at kdb_enter+0x3a:movl
$,kdb_why
(this is from hand-written notes, and may not be exact)

zfs is causing a panic when I try to write a file with a 64 bit "nobody" UID.

This occurs from a tar, from cp, and from rsync, and any other attempt to write a file owned by UID 4294967294.

This UID originates from the anonymous (nobody) UID -2 on a windows server.  When this UID is written to a unix NFS server, it becomes 4294967294.

More details on this UID origination are at 
http://blogs.msdn.com/sfu/pages/who-s-4294967294.aspx

Other filesystems don't have a problem with this 64bit UID.  Ideally ZFS shouldn't either, but if we don't want to support 64bit UIDs, then we should find something more useful to do than generating a panic.
>How-To-Repeat:
extract the files from the attached tar file onto a zfs filesystem.

Due to a browser bug, the file is named with .txt, but it IS a tar file.
>Fix:


Patch attached with submission follows:

PaxHeader/429496729418 uid=4294967294
20 ctime=1237918499
20 atime=1237918460
38 LIBARCHIVE.creationtime=1237910562
18 SCHILY.dev=122
22 SCHILY.ino=6712369
18 SCHILY.nlink=2
18 uid=4294967294
20 ctime=1237918471
20 atime=1237917918
38 LIBARCHIVE.creationtime=1200689912
18 SCHILY.dev=122
22 SCHILY.ino=6712461
18 SCHILY.nlink=1
18 uid=4294967294
20 ctime=1237918471
20 atime=1237917840
38 LIBARCHIVE.creationtime=1200689712
18 SCHILY.dev=122
22 SCHILY.ino=6712460
18 SCHILY.nlink=1
18 uid=4294967294
20 ctime=1237918471
20 atime=1237918384
38 LIBARCHIVE.creationtime=1200690132
18 SCHILY.dev=122
22 SCHILY.ino=6712462
18 SCHILY.nlink=1

>Release-Note:
>Audit-Trail:
>Unformatted:



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