Date: Mon, 07 Jan 2019 06:22:39 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234680] file system apparently does not commit changes Message-ID: <bug-234680-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234680 Bug ID: 234680 Summary: file system apparently does not commit changes Product: Base System Version: 11.2-STABLE Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: tootall79@gmail.com hard to be succinct: I am building a process with about 15 static librarie= s.=20 If i make a change to one of them then relink, the link is unpredictable.=20 Sometimes it links the previous version of the file. Today it was all day trying to convince the linker lldb 6 that this file is NEW use the NEW one = not the OLD one which isn't even on the file system. I am baffled. After I took a two hour dinner break the file showed up with= the changes compiled in and linked and ran as expected. So do I need to take a= two hour break after each build so the file system ufs can commit? I have been manually executing sync and sudo sync after each build. Whats = up?=20 I must be missing something. The appearance is that the old file is lurking in memory and the linker is linking to the old image. Why is that? Is that by design? Thanks! --=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-234680-227>