[Bug 205932] [panic] Kernel panic when copying from ext2fs partition to UFS partition
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Jan 5 19:49:15 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205932
Bug ID: 205932
Summary: [panic] Kernel panic when copying from ext2fs
partition to UFS partition
Product: Base System
Version: 10.2-RELEASE
Hardware: amd64
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: misc
Assignee: freebsd-bugs at FreeBSD.org
Reporter: will_brokenbourgh at yahoo.com
CC: freebsd-amd64 at FreeBSD.org
CC: freebsd-amd64 at FreeBSD.org
Created attachment 165117
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165117&action=edit
Verbose kernel panic textual information
When copying files from an ext4 partition on device ada1 mounted read-only to a
user's home directory on the FreeBSD root (UFS) partition on device ada0, a
kernel panic occurs after around 100 files are copied.
It appears at least one other person has experienced this recently:
http://freebsd.1045724.n5.nabble.com/Ext4-Kernel-Panic-td6025605.html
This kernel panic happens after a fresh install with NO packages or ports
installed yet and both before AND after performing system update with
freebsd-update.
COMMANDS ISSUED (under root account):
- - -
# mount -t ext2fs -o ro /dev/ada1p4 /mnt/adisk
# cd /mnt/adisk
# ls
lost+found will
# cp -Rnv will /home/will
(KP happens after about 100 files copied)
- - -
CRASH INFO:
- - -
Dump header from device /dev/ada0p3
Architecture: amd64
Architecture Version: 2
Dump Length: 714723328B (681 MB)
Blocksize: 512
Dumptime: Tue Jan 5 10:51:56 2016
Hostname: will-freebsd
Magic: FreeBSD Kernel Dump
Version String: FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015
root at releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC
Panic String: __lockmgr_args: recursing on non recursive lockmgr getblk @
(null):0
Dump Parity: 3650188378
Bounds: 1
Dump Status: good
- - -
The more verbose crash text is attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-amd64
mailing list