Date: Tue, 9 Aug 2016 07:32:14 +0200 From: Kurt Jaeger <lists@opsec.eu> To: Harry Schmalzbauer <freebsd@omnilan.de> Cc: Rick Macklem <rmacklem@uoguelph.ca>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: unionfs bugs, a partial patch and some comments [Was: Re: 1-BETA3 Panic: __lockmgr_args: downgrade a recursed lockmgr nfs @ /usr/local/share/deploy-tools/RELENG_11/src/sys/fs/unionfs/union_vnops.c:1905] Message-ID: <20160809053214.GW96200@home.opsec.eu> In-Reply-To: <57A83C78.1070403@omnilan.de> References: <57A79E24.8000100@omnilan.de> <YQBPR01MB0401201977AEA8A803F27B23DD1A0@YQBPR01MB0401.CANPRD01.PROD.OUTLOOK.COM> <57A83C78.1070403@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi! > Since then I'm draging a minimal patch which prevents at least the > kernel panics for me. > Unfortunately I don't have the skills to continue Attilio Raos work. > > Just for anybody else needing unionfs: > https://people.freebsd.org/~attilio/unionfs_missing_insmntque_lock.patch Is this referenced in any PR ? If not, can you create one ? > First thing to do for me, after I won in lottery, was to find someone > who can be sponsored fixing unionfs ;-) And bringing MNAMELEN into 21st > century state, matching ZFS needs: > https://lists.freebsd.org/pipermail/freebsd-hackers/2015-November/048640.html > This is another patch I'm carrying for a very long time which solves > tremendous limitations for me. Without that, I couldn't use ZFS > snapshots in real world, along with a human-friendly dataset naming :-) And is there a PR for that ? -- pi@opsec.eu +49 171 3101372 4 years to go !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160809053214.GW96200>