Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[Bug 208882] zfs root filesystem mount failure on startup in FreeBSD

2 views
Skip to first unread message

bugzilla...@freebsd.org

unread,
Apr 18, 2016, 9:18:29 AM4/18/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208882

Mark Linimon <lin...@FreeBSD.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|freebs...@FreeBSD.org |freeb...@FreeBSD.org

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freeb...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-fs
To unsubscribe, send any mail to "freebsd-fs-...@freebsd.org"

bugzilla...@freebsd.org

unread,
Apr 23, 2016, 8:27:39 AM4/23/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208882

--- Comment #4 from Masachika ISHIZUKA <i...@amail.plala.or.jp> ---
(In reply to Fabian Keil from comment #3)

Thank you for new patch.
Although I hope this patch to be merged into base/head branch, I don't know how
to request them.

# I'm not test 'nfs mount retry' because I don't use nfs filesystems that are
nessesary on bootup, and I use 'autofs' for /home, /usr/altlocal and so on to
avoid mount error when nfs server is down for maintenance.

bugzilla...@freebsd.org

unread,
Apr 25, 2016, 12:46:23 PM4/25/16
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208882

--- Comment #5 from Fabian Keil <f...@fabiankeil.de> ---
No worries, I did not expect you to test the NFS mount retries.

The freebsd-fs@ list is already CC'd, so an additional request
to get the patch reviewed and committed should not be necessary.

bugzilla...@freebsd.org

unread,
Mar 3, 2018, 2:03:32 PM3/3/18
to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208882

--- Comment #18 from Kurt Jaeger <p...@FreeBSD.org> ---
See

https://lists.freebsd.org/pipermail/freebsd-stable/2018-March/088484.html

and discussion. Seems to be a common problem.
0 new messages