Date: Fri, 18 Aug 2023 21:17:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 273215] nullfs: modification times incorrect, breaking make etc. Message-ID: <bug-273215-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273215 Bug ID: 273215 Summary: nullfs: modification times incorrect, breaking make etc. Product: Base System Version: 13.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: andrew@tao11.riddles.org.uk Created attachment 244204 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D244204&action= =3Dedit file creation test script for modtimes bug On (recent) 13.2-STABLE, but apparently not on CURRENT, the modification ti= mes of created files on nullfs (at least when the lower filesystem is UFS, have= n't tried other combinations yet) are ending up some arbitrary time later than = they should be, as though the "marked for update" condition is not being process= ed when it should. For example, running the attached test on 13.2-stable, despite taking 2 sec= onds delay between creating files, file 2 ends up looking older than file 1, and files 1,3,4 end up with the same timestamp. This manifests in build failures for ports if the port workdir is on a null= fs mount, because for example the files created by autoreconf / libtoolize / e= tc. end up with timestamps that don't match their dependency order, resulting in erroneous attempts to rebuild them in build phase (an example of a port that fails reliably is graphics/graphviz). --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273215-227>