Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

kern/36220: panic: sched_sync: fsync failded vp 0xcf4ccc08 tag 19

0 views
Skip to first unread message

Vladimir B. Grebenschikov

unread,
Mar 22, 2002, 5:30:23 PM3/22/02
to

>Number: 36220
>Category: kern
>Synopsis: panic: sched_sync: fsync failded vp 0xcf4ccc08 tag 19
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Mar 22 14:30:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: Vladimir B. Grebenschikov
>Release: FreeBSD 5.0-CURRENT i386
>Organization:
SWsoft
>Environment:
System: FreeBSD lightning.express.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #9: Fri Mar 22 22:49:46 MSK 2002 vo...@vbook.express.ru:/usr/local/src/sys/i386/compile/LIGHTNING i386

>Description:

System panic just fater try to mount msdos filesystem
(my guess: at first sync after triing to mount)
with message:
panic: sched_sync: fsync failded vp 0xcf4ccc08 tag 19

please note, that mount_msdosfs finished before panic with error
message:

# mount /m/C
msdosfs: /dev/ad0s1: Not a directory
#

backtrace:
db> tr
Debugger(x0299efb) at Debugger+0x40
panic(c0299eea0,cf4ccc08,13,ce85c600,c01da0cc) at panic+0x70
sched_sync(0, cee2ad48) at sched_sync+0x191
fork_exit(c01da0cc,0cee2ad48) at forl_exit+0x98
fork_trampoline() at fork_trampoline+0x8
db>


>How-To-Repeat:
FreeBSD 5.0-CURRENT dated 22 Mar 2002 22:00 MSK
and try to mount msdosfs
(mount options:
rw,-u=operator,-g=operator,-m=775,-l,-L=ru_RU.KOI8-R,-W=koi2dos
my usual options)
>Fix:

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

To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message

0 new messages