Hi Ashwin, It does seem likely that these failures are due to using ZFS, yes.
It looks like possible ZFS does not implement the renameat2() flags and so returns EINVAL -- we should probably treat this the same as ENOSYS and fall back to rename(). However, it looks like there are also some cases where regular rename() failed. At first glance I don't have any ideas why that would happen. It could be a conformance bug in ZFS itself. I don't have access to a ZFS machine so I'm not able to debug this myself. It's possible these bugs could pretty seriously break anything that uses the KJ filesystem API, which includes in particular the capnp compiler itself. :/ -Kenton On Tue, Mar 12, 2019 at 10:57 AM Ashwin Kapur <ash...@rebootinvesting.com> wrote: > I'm running on Ubuntu 18.04 on a Root ZFS filesystem. I see that the > failures are mainly to filesystem-disk-test.c++ and I'm wondering if the > failures have something to do with ZFS. > > Thanks. > > Ashwin > > -- > You received this message because you are subscribed to the Google Groups > "Cap'n Proto" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to capnproto+unsubscr...@googlegroups.com. > Visit this group at https://groups.google.com/group/capnproto. > -- You received this message because you are subscribed to the Google Groups "Cap'n Proto" group. To unsubscribe from this group and stop receiving emails from it, send an email to capnproto+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/capnproto.
