Hello! <sfjro <at> users.sourceforge.net> writes:
> > Although I didn't read the systemd's fallback routine, my current > conclusion is, > - as long as systemd doesn't handle EOVERFLOW (and doesn't go into the > fallback routine), systemd will not work with many(? a few?) fs, I am > afraid. > - if systemd support EOVERFLOW, aufs can co-work with systemd. the "nfs > branch is not exportable" message will be still produced, but systemd > will go into its fallback routine. > - since systemd has "configure" script and if you disable > CONFIG_FHANDLE, then systemd will not try calling name_to_handle_at(). > And it will go into the fallback routine. and you will be happy too. Sorry for resurrecting this old thread, but I'm experiencing this very same issue. I'm observing this in a Debian Jessie (kernel 3.16.7) box, so my guess is that the issue was never solved in the systemd part (I'm using version 215-17+deb8u4). Can anyone confirm this? Also, regarding the disable of CONFIG_FHANDLE, how would I do that? Should I set CONFIG_FHANDLE=n and recompile the kernel (with aufs)? When I tried that I got this error: fs/built-in.o: In function `aufs_encode_fh': /home/sgimeno/kernel-patches/linux-backports/fs/aufs/export.c:752: undefined reference to `exportfs_encode_fh' fs/built-in.o: In function `decode_by_path': /home/sgimeno/kernel-patches/linux-backports/fs/aufs/export.c:518: undefined reference to `exportfs_decode_fh' Makefile:893: recipe for target 'vmlinux' failed ... so I think it must be something else. Any help would be appreciated!! Best regards, Santiago ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
