[Bug 193237] Boot attempts to execute `fsck_zfs`, fails and goes single-user.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193237 kpn...@pobox.com changed: What|Removed |Added CC||kpn...@pobox.com --- Comment #1 from kpn...@pobox.com --- >From man fstab: If the sixth field is not present or is zero, a value of zero is returned and fsck(8) and quotacheck(8) will assume that the file system does not need to be checked. The sixth field is the "pass" field, which says in what order fsck should be run. Does setting it to zero solve the problem for you? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 193237] New: Boot attempts to execute `fsck_zfs`, fails and goes single-user.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193237 Bug ID: 193237 Summary: Boot attempts to execute `fsck_zfs`, fails and goes single-user. Product: Base System Version: 10.0-RELEASE Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Only Me Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: zyxaba...@yahoo.com After a system crash, the boot process stops while trying to execute `fsck_zfs`. The crash occurred when trying to mount UnionFS from a directory in a storage filesystem to a path in the root FS. The ZFS filesystems are in legacy mode, with mountpoints defined in '/etc/fstab'. If set to non-legacy, or manually mounted in single-user mode, everything mounts okay and the system boots. `zpool scrub` finds no errors and does not solve the problem. Relevant bootup messages (after running `fsck` once and rebooting): Starting filesystem checks: /dev/ada0p3: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0p3: clean, 31540463 free (1663 frags, 3942350 blocks, 0.0% fragmentation) fsck: exec fsck_zfs for storage/data1 in /sbin:/usr/sbin: No such file or directory fsck: exec fsck_zfs for storage/data2 in /sbin:/usr/sbin: No such file or directory fsck: exec fsck_zfs for storage/data1 in /sbin:/usr/sbin: No such file or directory fsck: exec fsck_zfs for storage/data2 in /sbin:/usr/sbin: No such file or directory /dev/ada0p4: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ada0p4: clean, 64996259 free (35 frags, 8124528 blocks, 0.0% fragmentation) THE FOLLOWING FILE SYSTEMS HAD AN UNEXPECTED INCONSISTENCY: zfs: storage/data2 (/mnt/storage/data2), zfs: storage/data1 (/mnt/storage/data1) Unknown error; help! ERROR: ABORTING BOOT (sending SIGTERM to parent)! Sep 1 18:34:58 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Re: Most submittal-specific things for bugs.freebsd.org just get: 502 Bad Gateway nginx/1.6.1 [Never Mind]
I've now got some direct evidence that the issue is somehow local to my context. So ignore the report! === Mark Millard mar...@dsl-only.net On Sep 1, 2014, at 5:22 PM, Mark Millard wrote: Most submittal-specific things for bugs.freebsd.org just get: 502 Bad Gateway nginx/1.6.1 (At least it has been that way for me for some time, although I've not frequently trying until today. I was going guessing temporary/intermittent but none of my tries have worked in some time. So I just tried a bunch of accesses and all failed as indicated.) Examples accesses that fail that way include: https://bugs.freebsd.org/browse/ https://bugs.freebsd.org/search/ https://bugs.freebsd.org/submit/ https://bugs.freebsd.org/135576 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135576 === Mark Millard markmi at dsl-only.net ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Most submittal-specific things for bugs.freebsd.org just get: 502 Bad Gateway nginx/1.6.1
Most submittal-specific things for bugs.freebsd.org just get: 502 Bad Gateway nginx/1.6.1 (At least it has been that way for me for some time, although I've not frequently trying until today. I was going guessing temporary/intermittent but none of my tries have worked in some time. So I just tried a bunch of accesses and all failed as indicated.) Examples accesses that fail that way include: https://bugs.freebsd.org/browse/ https://bugs.freebsd.org/search/ https://bugs.freebsd.org/submit/ https://bugs.freebsd.org/135576 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=135576 === Mark Millard markmi at dsl-only.net ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 192085] [zfs] panic on zvol resize
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192085 Chloé Desoutter changed: What|Removed |Added CC||chloe.desout...@atasta.net --- Comment #4 from Chloé Desoutter --- Affects me aswell on 11-CURRENT. Run on a machine that had just panicked before. Will panic when zfs set volsize= root@cabron:~ # zpool status pool: zroot state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: none requested config: NAME STATE READ WRITE CKSUM zroot ONLINE 0 0 0 gptid/14121fe7-dc29-11e3-9178-84349711c070 ONLINE 0 0 0 errors: No known data errors root@cabron:~ # zfs list NAME USED AVAIL REFER MOUNTPOINT zroot918G 1.74T 144K none zroot/ROOT 13.2G 1.74T 144K none zroot/ROOT/default 13.2G 1.74T 6.69G / zroot/centoracle20.6G 1.76T 1.09G - zroot/chdesk 531G 2.24T 15.6G - zroot/factorie 41.3G 1.78T 2.37G - zroot/freebsdguest 13.1G 1.75T 2.76G - zroot/herpderp 12.4G 1.74T 12.0G - zroot/hostie51.6G 1.78T 5.23G - zroot/jabba 10.3G 1.74T 2.65G - zroot/memailguest206G 1.94T 2.72G - zroot/tmp 42.5M 1.74T 42.5M /tmp zroot/usr 5.51G 1.74T 144K /usr zroot/usr/home 2.86G 1.74T 2.86G /usr/home zroot/usr/ports 1.40G 1.74T 940M /usr/ports zroot/usr/src 1.25G 1.74T 1.14G /usr/src zroot/var777M 1.74T 420M /var zroot/var/crash 159M 1.74T 159M /var/crash zroot/var/log 3.22M 1.74T 2.19M /var/log zroot/var/mail 3.74M 1.74T 3.50M /var/mail zroot/var/tmp 4.31M 1.74T 4.31M /var/tmp zroot/vmtest12.0G 1.75T 1.73G - ...skipping... Dump header from device /dev/gpt/swap0 Architecture: amd64 Architecture Version: 2 Dump Length: 1353125888B (1290 MB) Blocksize: 512 Dumptime: Mon Sep 1 22:12:29 2014 Hostname: cabron.atasta.net Magic: FreeBSD Kernel Dump Version String: FreeBSD 11.0-CURRENT #0 r269749: Sat Aug 9 17:05:00 CEST 2014 r...@cabron.atasta.net:/usr/obj/usr/src/sys/GENERIC Panic String: solaris assert: !rrw_held(&dp->dp_config_rwlock, RW_READER), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_pool.c, line: 1115 Dump Parity: 531732301 Bounds: 0 Dump Status: good cabron.atasta.net dumped core - see /var/crash/vmcore.0 Mon Sep 1 22:19:17 CEST 2014 FreeBSD cabron.atasta.net 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r269749: Sat Aug 9 17:05:00 CEST 2014 r...@cabron.atasta.net:/usr/obj/usr/src/sys/GENERIC amd64 panic: solaris assert: !rrw_held(&dp->dp_config_rwlock, RW_READER), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_pool.c, line: 1115 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... Unread portion of the kernel message buffer: panic: solaris assert: !rrw_held(&dp->dp_config_rwlock, RW_READER), file: /usr/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/dsl_pool.c, line: 1115 cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe08568bd3b0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe08568bd460 vpanic() at vpanic+0x126/frame 0xfe08568bd4a0 panic() at panic+0x43/frame 0xfe08568bd500 assfail() at assfail+0x1d/frame 0xfe08568bd510 dsl_pool_hold() at dsl_pool_hold+0x67/frame 0xfe08568bd550 dmu_objset_hold() at dmu_objset_hold+0x21/frame 0xfe08568bd590 dsl_prop_get_integer() at dsl_prop_get_integer+0x28/frame 0xfe08568bd5d0 zvol_set_volsize() at zvol_set_volsize+0x126/frame 0xfe08568bd660 zfs_prop_set_special() at zfs_prop_set_special+0x2e2/frame 0xfe08568bd6f0 zfs_set_prop_nvlist() at zfs_set_prop_nvlist+0x23f/frame 0xfe08568bd780 zfs_ioc_set_prop() at zfs_ioc_set_prop+0x106/frame 0xfe08568bd7e0 zfsdev_ioctl() at zfsdev_ioctl+0x6ee/frame 0xfe08568bd890 devfs_ioctl_f() at devfs_ioctl_f+0xfb/frame 0xfe08568bd8f0 kern_ioctl() at kern_ioctl+0x22b/frame 0xfe08568bd950 sys_ioctl() at sys_ioctl+0x13c/frame 0xfe08568bd9a0 amd64_syscall() at amd64_syscall+0x25a/frame 0xfe08568bdab0 Xfast_syscall() at Xfast_syscall+0xfb/
[Bug 193228] freebsd-update(8) -b for jail updates fails on last "install" within major-update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193228 Martin Kropfinger changed: What|Removed |Added Summary|freebsd-update(8) for |freebsd-update(8) -b for |jailupdates |jail updates fails on last ||"install" within ||major-update --- Comment #1 from Martin Kropfinger --- Updating a jails, for patch levels, can be done with freebsd-update(8). I tried updating a jail with freebsd-update from 9.2-p10 to 10.0-p7. At first i set UNAME_r using setenv to 9.2-RELEASE-p10 and did the: freebsd-update upgrade -r 10.0-RELEASE -b /usr/jails/wiki Followed by freebsd-update install and again freebsd-update install. During this I restarted the jail. After this I rebuild all ports inside the jail. At last I tried the last freebsd-install with: freebsd-update upgrade -r 10.0-RELEASE -b /usr/jails/wiki freebsd-install(8) returned: Installing updates...rmdir: /usr/jails/wiki//var/named/etc/namedb/master: Directory not empty rmdir: /usr/jails/wiki//var/named/etc/namedb: Directory not empty rmdir: /usr/jails/wiki//var/named/etc: Directory not empty rmdir: /usr/jails/wiki//var/named: Directory not empty done. So the paths seem to be handled in a wrong way. The jail can't be started at all because oh wrong libs. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bug 193228] New: freebsd-update(8) for jailupdates
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193228 Bug ID: 193228 Summary: freebsd-update(8) for jailupdates Product: Base System Version: 10.0-RELEASE Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: freebsdbugzi...@schreibteinemail.de -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
[Bugzilla] Commit Needs MFC
Hi, You have a bug in the "Needs MFC" state which has not been touched in 7 or more days. This email serves as a reminder that you may want to MFC this bug or marked it as completed. In the event you have a longer MFC timeout you may update this bug with a comment and I won't remind you again for 7 days. This reminder is only sent on Mondays. Please file a bug about concerns you may have. This search was scheduled by ead...@freebsd.org. (9 bugs) Bug 155028: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=155028 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: init(8): "init q" in single user causes segfault Bug 156481: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156481 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [kernel] [patch] kernel incorrectly reports PPS jitter with accurate measurements Bug 165630: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165630 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [ndis][panic][patch] IRQL_NOT_GREATER_THAN Bug 167133: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=167133 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: stale files in /usr/share/examples Bug 169471: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=169471 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] pw(8) deletes group "username" on userdel even if group "username" is not assoc. w/user "username" Bug 171779: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171779 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] passwd(1): make option NO_FSCHG incomplete Bug 184681: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184681 Severity: Affects Only Me Priority: Normal Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: A bug of bsdconfig(8) in 10.0 RC1 Bug 192760: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192760 Severity: Affects Some People Priority: --- Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [build] sbin/ifconfig: missing DPADD for LIBM Bug 192926: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192926 Severity: Affects Some People Priority: --- Hardware: Any Assignee: freebsd-bugs@FreeBSD.org Status: Needs MFC Resolution: Summary: [patch] sched_yield is a no-op ___ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
