https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
Jason W. Bacon changed:
What|Removed |Added
Resolution|--- |Overcome By Events
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
--- Comment #7 from Jason W. Bacon ---
Oddly, about a week after I switched to "umount -A -t nfs", I experienced a
couple more freezes. I switched back to "automount -u" and it hasn't froze
again since. Doesn't really make sense to me and
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
--- Comment #6 from Edward Tomasz Napierala ---
Yes, it's safe - "automount -u" is really just a kind of an user-friendly
shortcut so that you don't need to manually figure out which filesystems to
unmount.
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
--- Comment #5 from Jason W. Bacon ---
The problem has occurred on multiple laptops. The two I use most are using
rtwn and iwn (wifi) most of the time. They have re and im Ethernet, but I
don't often plug in.
I'll run with
umount -A -t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
--- Comment #4 from Edward Tomasz Napierala ---
Hm. I'd say it's a problem with NFS then, not automount - and the workaround
should be more like "umount -At nfs".
Still, would be nice to figure out the root cause for this. What's your
ne
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
Rodney W. Grimes changed:
What|Removed |Added
CC||b...@freebsd.org,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
Edward Tomasz Napierala changed:
What|Removed |Added
Status|New |Open
Assignee|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
Edward Tomasz Napierala changed:
What|Removed |Added
CC||tr...@freebsd.org
--- Co
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228786
Mark Linimon changed:
What|Removed |Added
Summary|autoconf interferes with|automount interferes with
