[Bug 234680] file system apparently does not commit changes
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Mon Jan 7 06:22:41 UTC 2019
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234680
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 at FreeBSD.org
Reporter: tootall79 at gmail.com
hard to be succinct: I am building a process with about 15 static libraries.
If i make a change to one of them then relink, the link is unpredictable.
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?
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!
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list