[Bug 183328] freebsd-update upgrade from 9.1 to 9.2 for zfs on root results in unbootable system
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=183328 Garrett Cooper,425-314-3911 changed: What|Removed |Added Assignee|freebsd-bugs@FreeBSD.org|freebsd...@freebsd.org CC||n...@freebsd.org --- Comment #1 from Garrett Cooper,425-314-3911 --- (In reply to dms from comment #0) Unfortunately the forum page is a 404 now :(. I'm guessing you ran into a slew of errors like "boot: ZFS: i/o error - all block copies unavailable". I recently replaced a spinning rust disk with an SSD (with 4kB sectors), installed 9.3, upgraded to the latest point release, and unfortunately ran into this unbootable scenario, similar to what you've described below. I had to wipe out my root zpool and repartition the SSD. Fortunately I didn't have any critical data on it, but it was unfortunate that I had to hop through that hoop in order to get my system back in working shape.. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 203108] Thinkpad T420s will not boot GPT formatted disks.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203108 cr...@rlwinm.de changed: What|Removed |Added CC||cr...@rlwinm.de --- Comment #1 from cr...@rlwinm.de --- It is a known problem that the X220 and T420 refuse to boot in legacy mode from GPT formatted disks. I suspect that the T420s is affected as well. You can either boot in legacy mode from a MBR + bsdlabel formatted disk or boot in EFI mode with the experimental UFS only EFI bootloader. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202310] [PATCH] fix possible typo in src/Makefile.inc1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202310 --- Comment #1 from commit-h...@freebsd.org --- A commit references this bug: Author: brd Date: Tue Sep 15 14:24:20 UTC 2015 New revision: 287824 URL: https://svnweb.freebsd.org/changeset/base/287824 Log: Fix grammer in an error message PR:202310 Submitted by:Chris Petrik Approved by:will Changes: head/Makefile.inc1 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202310] [PATCH] fix possible typo in src/Makefile.inc1
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202310 Brad Davis changed: What|Removed |Added Resolution|--- |FIXED CC||b...@freebsd.org Status|New |Closed --- Comment #2 from Brad Davis --- Committed, thanks! -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 203129] syslogd: /dev/console: Interrupted system call on arm64
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203129 Bug ID: 203129 Summary: syslogd: /dev/console: Interrupted system call on arm64 Product: Base System Version: 11.0-CURRENT Hardware: arm64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: ema...@freebsd.org Observed fairly regularly on arm64: root@:~ # Sep 15 15:00:11 syslogd: /dev/console: Interrupted system call -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 203133] [nfs] [lor] newnfs/proctree lock order reversal
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203133 Bug ID: 203133 Summary: [nfs] [lor] newnfs/proctree lock order reversal Product: Base System Version: 10.2-BETA2 Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ga...@freebsd.org Host is 10.2-BETA2 running r285810. Host has four NFS mounts from two separate NetApp filers. One of those filers was rebooted, and a client got this: Sep 15 07:13:36 client kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 Sep 15 07:14:01 client kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 Sep 15 07:14:26 client kernel: NLM: failed to contact remote rpcbind, stat = 5, port = 28416 Sep 15 07:14:28 client kernel: lock order reversal: Sep 15 07:14:28 client kernel: 1st 0xf801b48639a0 newnfs (newnfs) @ /space/freebsd/stable/10/sys/kern/vfs_vnops.c:1332 Sep 15 07:14:28 client kernel: 2nd 0x81c69458 proctree (proctree) @ /space/freebsd/stable/10/sys/kern/subr_prf.c:205 Sep 15 07:14:28 client kernel: newnfs server netapp:/vol/filestore: not responding Sep 15 07:14:28 client kernel: KDB: stack backtrace: Sep 15 07:14:28 client kernel: newnfs server netapp:/vol/filestore: not responding Sep 15 07:14:28 client kernel: newnfs server netapp:/vol/filestore: not responding Sep 15 07:14:28 client kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0469134f40 Sep 15 07:14:28 client kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe0469134ff0 Sep 15 07:14:28 client kernel: witness_checkorder() at witness_checkorder+0xe24/frame 0xfe0469135080 Sep 15 07:14:28 client kernel: _sx_slock() at _sx_slock+0x76/frame 0xfe04691350c0 Sep 15 07:14:28 client kernel: vtprintf() at vtprintf+0x3d/frame 0xfe0469135140 Sep 15 07:14:28 client kernel: tprintf() at tprintf+0x3b/frame 0xfe04691351a0 Sep 15 07:14:28 client kernel: nfs_feedback() at nfs_feedback+0x232/frame 0xfe04691351e0 Sep 15 07:14:28 client kernel: clnt_reconnect_call() at clnt_reconnect_call+0x556/frame 0xfe0469135290 Sep 15 07:14:28 client kernel: newnfs_request() at newnfs_request+0x947/frame 0xfe04691353e0 Sep 15 07:14:28 client kernel: nfscl_request() at nfscl_request+0x72/frame 0xfe0469135430 Sep 15 07:14:28 client kernel: nfsrpc_getattr() at nfsrpc_getattr+0xbb/frame 0xfe0469135580 Sep 15 07:14:28 client kernel: nfs_getattr() at nfs_getattr+0x12e/frame 0xfe0469135740 Sep 15 07:14:28 client kernel: VOP_GETATTR_APV() at VOP_GETATTR_APV+0xf1/frame 0xfe0469135770 Sep 15 07:14:28 client kernel: vn_stat() at vn_stat+0x81/frame 0xfe0469135870 Sep 15 07:14:28 client kernel: vn_statfile() at vn_statfile+0x4f/frame 0xfe04691358c0 Sep 15 07:14:28 client kernel: kern_fstat() at kern_fstat+0xa2/frame 0xfe0469135910 Sep 15 07:14:28 client kernel: sys_fstat() at sys_fstat+0x17/frame 0xfe04691359a0 Sep 15 07:14:28 client kernel: amd64_syscall() at amd64_syscall+0x25a/frame 0xfe0469135ab0 Sep 15 07:14:28 client kernel: Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfe0469135ab0 Sep 15 07:14:28 client kernel: --- syscall (189, FreeBSD ELF64, sys_fstat), rip = 0x80bec274a, rsp = 0x7fffddbc9f58, rbp = 0x7fffddbc9ff0 --- On reconnect, I got a second (different) lock order reversal, I'll open a second PR about that as I believe it to be unrelated. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 203134] [nfs] [nlm] [lor] newnfs/allproc lock order reversal on NFS mount recovery
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203134 Bug ID: 203134 Summary: [nfs] [nlm] [lor] newnfs/allproc lock order reversal on NFS mount recovery Product: Base System Version: 10.2-BETA2 Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: ga...@freebsd.org Host is 10.2-BETA2 running r285810. Host has four NFS mounts from two separate NetApp filers. One of those filers was rebooted, which caused the mount to stop responding (and produced a LOR which I believe is unrelated, see bug 203133). When the filer became available again, a client got this: Sep 15 07:14:48 client kernel: lock order reversal: Sep 15 07:14:48 client kernel: 1st 0xf8000d704d50 newnfs (newnfs) @ /space/freebsd/stable/10/sys/nlm/nlm_advlock.c:500 Sep 15 07:14:48 client kernel: 2nd 0x81c694d8 allproc (allproc) @ /space/freebsd/stable/10/sys/kern/kern_proc.c:309 Sep 15 07:14:48 client kernel: KDB: stack backtrace: Sep 15 07:14:48 client kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0469a137a0 Sep 15 07:14:48 client kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe0469a13850 Sep 15 07:14:48 client kernel: witness_checkorder() at witness_checkorder+0xe24/frame 0xfe0469a138e0 Sep 15 07:14:48 client kernel: _sx_slock() at _sx_slock+0x76/frame 0xfe0469a13920 Sep 15 07:14:48 client kernel: pfind() at pfind+0x22/frame 0xfe0469a13940 Sep 15 07:14:48 client kernel: nlm_set_creds_for_lock() at nlm_set_creds_for_lock+0xb4/frame 0xfe0469a13970 Sep 15 07:14:48 client kernel: nlm_client_recover_lock() at nlm_client_recover_lock+0x61/frame 0xfe0469a139b0 Sep 15 07:14:48 client kernel: lf_iteratelocks_sysid() at lf_iteratelocks_sysid+0x194/frame 0xfe0469a13a10 Sep 15 07:14:48 client kernel: nlm_client_recovery() at nlm_client_recovery+0x51/frame 0xfe0469a13a50 Sep 15 07:14:48 client kernel: nlm_client_recovery_start() at nlm_client_recovery_start+0x35/frame 0xfe0469a13a70 Sep 15 07:14:48 client kernel: fork_exit() at fork_exit+0x84/frame 0xfe0469a13ab0 Sep 15 07:14:48 client kernel: fork_trampoline() at fork_trampoline+0xe/frame 0xfe0469a13ab0 Sep 15 07:14:48 client kernel: --- trap 0xc, rip = 0x800cb747a, rsp = 0x7fffeb78, rbp = 0x7fffed00 --- Sep 15 07:14:49 client rpc.statd: Unsolicited notification from host netapp-14 Sep 15 07:14:51 client rpc.statd: Unsolicited notification from host netapp-126 Sep 15 07:14:57 client kernel: newnfs server netapp:/vol/filestore: is alive aganin Unfortunately, I'm unlikely to be able to recreate this one at will. Gavin -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202892] open with O_CREAT | O_DIRECTORY when path references a symlink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202892 Konstantin Belousov changed: What|Removed |Added Resolution|--- |FIXED Status|In Progress |Closed -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 202892] open with O_CREAT | O_DIRECTORY when path references a symlink
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202892
--- Comment #11 from commit-h...@freebsd.org ---
A commit references this bug:
Author: kib
Date: Wed Sep 16 04:23:09 UTC 2015
New revision: 287847
URL: https://svnweb.freebsd.org/changeset/base/287847
Log:
MFC r287599:
Correct handling of open("name", O_DIRECTORY | O_CREAT).
PR:202892
Changes:
_U stable/10/
stable/10/sys/kern/vfs_vnops.c
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
