Thoughts on TMPFS no longer being considered "highly
experimental"
Alexander Best
arundel at freebsd.org
Thu Jun 23 17:53:14 UTC 2011
On Thu Jun 23 11, Matthew Jacob wrote:
>
> I gave up on using it after a brief try earlier this year. I can't
> remember the details, but it did lock up my amd64 system.
>
> On Thu, 23 Jun 2011, David O'Brien wrote:
>
> >Does anyone object to this patch?
> >
> >David Wolfskill and I have run TMPFS on a number of machines for two
> >years with no problems.
+1 here. i haven't experienced any issues for > 1 year or so, but if people
think removing the warning entirely is too early, maybe the warning can be
rephrased in order to be less frightening.
maybe sth like:
"TMPFS still needs wider testing and thus should not be considered ready for
production use, yet."
cheers.
alex
> >
> >I may have missed something, but I'm not aware of any serious PRs on
> >TMPFS either.
> >
> >
> >Index: tmpfs_vfsops.c
> >===================================================================
> >--- tmpfs_vfsops.c (revision 221113)
> >+++ tmpfs_vfsops.c (working copy)
> >@@ -155,9 +155,6 @@ tmpfs_mount(struct mount *mp)
> > return EOPNOTSUPP;
> > }
> >
> >- printf("WARNING: TMPFS is considered to be a highly experimental "
> >- "feature in FreeBSD.\n");
> >-
> > vn_lock(mp->mnt_vnodecovered, LK_SHARED | LK_RETRY);
> > error = VOP_GETATTR(mp->mnt_vnodecovered, &va, mp->mnt_cred);
> > VOP_UNLOCK(mp->mnt_vnodecovered, 0);
> >
> >--
> >-- David (obrien at FreeBSD.org)
> >_______________________________________________
> >freebsd-current at freebsd.org mailing list
> >http://lists.freebsd.org/mailman/listinfo/freebsd-current
> >To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
> >
More information about the freebsd-current
mailing list