Re: error while compiling

Am 18.11.18 um 19:48 schrieb Jens Kasten:
> Sun Nov 18 19:20:44 2018 :
40000002377|rsbac_write_open(): could not
> rename fd_ff to fd_ffb on dev 179:03, error -2 - no backup!
> Sun Nov 18 19:20:44 2018 :
40000002378|rsbac_write_open(): relookup of
> fd_ff returned dentry with existing inode 404917, trying unlink
> Sun Nov 18 19:20:44 2018 :
40000002379|rsbac_write_open(): could not
> unlink fd_ff on dev 179:03, error -117!
> Sun Nov 18 19:20:44 2018 :
40000002380|rsbac_write_open(): relookup of
> fd_ff returned dentry with existing inode 404917
> Sun Nov 18 19:20:44 2018 :
40000002381|rsbac_list_write_buffers():
> opening file fd_ff on device 179:03 failed with error -1004!
> Sun Nov 18 19:20:44 2018 :
40000002382|rsbac_write_open(): could not
> rename authfd to authfdb on dev 179:03, error -2 - no backup!
> Sun Nov 18 19:20:44 2018 :
40000002383|rsbac_write_open(): relookup of
> authfd returned dentry with existing inode 407579, trying unlink
> Sun Nov 18 19:20:44 2018 :
40000002384|rsbac_write_open(): could not
> unlink authfd on dev 179:03, error -117!
> Sun Nov 18 19:20:44 2018 :
40000002385|rsbac_write_open(): relookup of
> authfd returned dentry with existing inode 407579
> Sun Nov 18 19:20:44 2018 :
40000002386|rsbac_list_write_lol_buffers():
> opening file authfd on device 179:03 failed with error -1004!
> Sun Nov 18 19:20:44 2018 :
40000002387|rsbac_write():
> rsbac_write_lists() returned error -1004
> 
> After a reboot all working again.
> Once I got a wrong ff setup on a directory which was never touched before.
> But have to observe it.

Please retry with latest Git, it seems to resolve the issue.

Amon.
-- 
http://www.rsbac.org - GnuPG: 2048g/5DEAAA30 2002-10-22