Date: Tue, 22 Dec 2015 11:34:43 +0200 From: Daniel Braniss <danny@cs.huji.ac.il> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: Yuri <yuri@rawbw.com>, Freebsd hackers list <freebsd-hackers@freebsd.org> Subject: Re: Should DEBUG_VFS_LOCKS messages be reported as bugs? Message-ID: <CE48BB9B-2FB0-4427-AC5E-4F0EDAAC8CC4@cs.huji.ac.il> In-Reply-To: <1331010544.139156804.1450706805234.JavaMail.zimbra@uoguelph.ca> References: <567791E9.50207@rawbw.com> <56779542.8020205@rawbw.com> <1331010544.139156804.1450706805234.JavaMail.zimbra@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 21 Dec 2015, at 16:06, Rick Macklem <rmacklem@uoguelph.ca> wrote: >=20 > Yuri wrote: >> On 12/20/2015 21:45, Yuri wrote: >>>=20 >>> it prints some messages that look like errors, see below. >>=20 >> I have recently began mounting /usr/ports as nullfs and unionfs on = top >> of it, and I believe this causes the system crashes during the = intense >> file activity on the unionfs-ed /usr/ports. >> /usr/ports.patches on /usr/ports (nullfs, local, read-only) >> <above>:/usr/ports.subversion on /usr/ports (unionfs, local, noatime) >>=20 > Unionfs is broken. See the BUGS section of "man mount_unionfs". > Here a snippet from it: > THIS FILE SYSTEM TYPE IS NOT YET FULLY SUPPORTED (READ: IT DOESN'T = WORK) > AND USING IT MAY, IN FACT, DESTROY DATA ON YOUR SYSTEM. USE AT = YOUR OWN > RISK. BEWARE OF DOG. SLIPPERY WHEN WET. BATTERIES NOT INCLUDED. >=20 > As such, reports for problems that you encounter when not using = unionfs are > far more useful, imho. >=20 I have been using unionfs for a very long time, mounting /etc (nfs read = only) and md whiteout any problems. I=E2=80=99m not sure if i tested it on 11, but i = will soon. yes, it can be problematic for other crazy things, but in my case, where = many of=20 my hosts are dataless so the unionfs is a great simplifier :-) just my 2 cents. > rick >=20 >> The messages I reported are related to this. >>=20 >> Yuri >>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >>=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CE48BB9B-2FB0-4427-AC5E-4F0EDAAC8CC4>