Date: Thu, 12 Oct 2017 09:18:22 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 222948] LOR Panic in disk access Message-ID: <bug-222948-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222948 Bug ID: 222948 Summary: LOR Panic in disk access Product: Base System Version: 11.1-STABLE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: grarpamp@gmail.com Boot the latest amd64 snapshot either 11 or 12, set the dev=3D parameter in= the script to some available da device and run it. Repeats every time. LOR panic is almost identical to http://docs.freebsd.org/cgi/mid.cgi?CAD2Ti2-6W_b04fHen5XHiT-bFQZ9CncZptUbDP= 0yaHbg7gjnUA and was possibly first noted here https://lists.freebsd.org/pipermail/freebsd-stable/2017-June/087291.html #!/bin/sh -- dev=3Dda1 set -x dd if=3D/dev/zero of=3D/dev/${dev} bs=3D1m count=3D64 gpart create -s mbr ${dev} gpart add -t freebsd -a 1m -b 1m -s 64m -i 1 ${dev} gpart create -s bsd ${dev}s1 gpart add -t freebsd-ufs -a 1m -b 1m -s 31m -i 1 ${dev}s1 gpart show -p ${dev} ${dev}s1 newfs /dev/${dev}s1a fsck -fy /dev/${dev}s1a mount -v -o rw /dev/${dev}s1a /mnt sysctl kern.geom.debugflags=3D16 ### this is broken, footshooting should be allowed here # dd: /dev/da0s1: Operation not permitted dd if=3D/dev/zero of=3D/dev/${dev}s1 seek=3D2 count=3D1 bs=3D1m sysctl kern.geom.debugflags=3D0 umount -v /dev/${dev}s1a mount -v -o ro /dev/${dev}s1a /mnt ls /mnt dd if=3D/dev/zero of=3D/dev/${dev}s1 seek=3D34 count=3D1 bs=3D1m ### this is broken # ls: .snap: Device not configured ls -l /mnt ### select mount instead of umount to get the LOR PANIC umount -v /dev/${dev}s1a #mount -uvw /dev/${dev}s1a --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222948-8>