[Bug 208691] "panic: ffs_valloc: dup alloc" as soon as UFS root partition is mounted

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Apr 11 07:37:08 UTC 2016


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208691

            Bug ID: 208691
           Summary: "panic: ffs_valloc: dup alloc" as soon as UFS root
                    partition is mounted
           Product: Base System
           Version: 10.2-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs at FreeBSD.org
          Reporter: martinwguy at gmail.com

On a system running STABLE since a week with STABLE kernel updated from svn, I 
left it on overnight, doing nothing, and woke up this morning to find it
rebooting continually:
-----------------------
** Resolving unreferenced inode list.
** Processing journal entries.

***** FILE SYSTEM MARKED CLEAN *****
Mounting local file systems:.
mode = 0100600, inum = 6742034, fs=/
panic: ffs_valloc: dup alloc
cpuid = 1
KDB: stack backtrace:
#0 0xc0b7c3c2 at kdb_backtrace+0x52
#1 0xc0b3c72b at vpanic+0x11b
#2 0xc0b3c60b at panic+0x1b
#3 0xc0d94221 at ffs_valloc+0x961
#4 0xc0ddbec3 at ufs_makeinode+0x73
#5 0xc0dd8110 at ufs_create+0x30
#6 0xc108ecd5 at VOP_CREATE_APV+0x95
#7 0xc0bfa316 at vn_open_cred+0x2d6
#8 0xc0bfa02d at vn_open+0x3d
#9 0xc0bf1fe0 at kern_openat+0x310
#10 0xc0bf1cba at sys_openat+0x3a
#11 0xc1067359 at syscall+0x5c9
#12 0xc10510bf at Xint0x80_syscall+0x2f
Uptime: 12s
Physical memory: 990 MB
Dumping 63 MB: 48 32 16
Dump complete
Automatic reboot in 15 seconds - press a key on the console to abort
-----------------------

This is using the i386 port running 10.2 STABLE with a GENERIC kernel
recompiled from updated svn. It has a single Hitachi SATA hard disk using MBR
default partitioning with everything on one slice.
Device         Start       End   Sectors  Size Type
/dev/sdg1         34      1057      1024  512K FreeBSD boot
/dev/sdg2       1058 111149089 111148032   53G FreeBSD UFS
/dev/sdg3  111149090 117010465   5861376  2.8G FreeBSD swap

I don't know if it's relevant but one thing I changed yesterday was to update
the kernel (while chasing a different panic!) from rX to rY and buildkernel
installkernel it but the symptom also happens if when I boot kernel.old
instead.
Unfortunately I can't tell you the kernel revision numbers because I can't stop
the boot sequence from scrolling, but the update was from the STABLE svn
version from about a week ago to yesterday (10 april 2016), bringing 6 to 10
new commits.
The kernel config is GENERIC with no modifications to code or config except for
installing ndiswrapper round bwnwl5.* to make bwnwl5_sys.ko for the BCM4311
wireless card (which also didn't work!).

The laptop tests 100% fine with memtest and has never given any signs of
hardware flakiness. The hard disk is 60GB from a few years ago but has never
given any signs of failure and read-test of the partition on a Linux box using
dd reads the whole partition without problems.

Running from live CD (10.2-RELEASE #0 r286666), mount says:
/dev/ada0p2: R/W mount of / denied. Filesystem is not clean - run fsck. ...

"fack /dev/ada0p2" says:
-----------------------------------
USE JOURNAL? [yn] y

** SU+J Recovering /dev/ada0p2
Reading 33554432 byte journal from inode 4

RECOVER? [yn] y

** Building recovery table.
** Resolving unreferenced inode list.
** Processing journal entries.

***** FILE SYSTEM MARKED CLEAN *****
------------------------------------
But booting it from the HD after this still panics; the only difference is that
it says "FILE SYSTEM CLEAN" before trying to mount the partition and panicking.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list