Bug 234680 - file system apparently does not commit changes
Summary: file system apparently does not commit changes
Status: New
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 11.2-STABLE
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-01-07 06:22 UTC by Tim
Modified: 2019-01-07 06:22 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim 2019-01-07 06:22:39 UTC 
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!