Bug #1279
closedFilesystem on NanoBSD is left read/write at first bootup after package reinstallation
100%
Description
It should be read only by the end of the boot process, but it doesn't seem to be making that change when packages were reinstalled during that boot.
EF Updated by Erik Fonnesbeck over 15 years ago
Specifically it was commit:52f4c092b14cca36bcc430717baf907273b66532
I don't think I saw the discussion on this, so I don't know the exact reason that was done.
BM Updated by Braden McGrath over 15 years ago
This is happening in RC1; I haven't yet tried a newer snapshot to check there.
EF Updated by Erik Fonnesbeck over 15 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset commit:"548be1fd6697ab115cbb29d61bc5507744488094".
JP Updated by Jim Pingle over 15 years ago
Applied in changeset commit:"63e18082bb98d51763e542d5c4094793b300eb60".
JS Updated by Josh Stompro about 15 years ago
Using nanobsd i386 8.1-release-p4 Jul 8 06:31:18 EDT 2011, after resetting to system default and rebooting, the / mount is set to RW.
It is my impression that it should be RO after the bootup is complete.
Josh
JP Updated by Jim Pingle about 15 years ago
- Status changed from Feedback to New
The filesystem is mounted noatime, so even if it's left rw, it still isn't touched except when the system wants to write out things like the config, which it switched to rw to do anyhow. It should still be fixed at some point before release, but it isn't as critical as it looks.
EL Updated by Ermal Luçi about 15 years ago
- Status changed from New to Feedback
I put a fix that helps this.
Can you please try with latest snapshots?
JP Updated by Jim Pingle about 15 years ago
- Status changed from Feedback to New
It ends up read only but it breaks many other things if you upgrade with packages. GUI doesn't load, many processes die with sig11. Same thing that happened last time a fix was attempted.
CB Updated by Chris Buechler almost 15 years ago
- Priority changed from Normal to High
- Target version changed from 2.0 to 2.0.1
CB Updated by Chris Buechler almost 15 years ago
- Subject changed from Filesystem on NanoBSD is left read/write at bootup to Filesystem on NanoBSD is left read/write at first bootup after package installation
CB Updated by Chris Buechler almost 15 years ago
- Subject changed from Filesystem on NanoBSD is left read/write at first bootup after package installation to Filesystem on NanoBSD is left read/write at first bootup after package reinstallation
CB Updated by Chris Buechler almost 15 years ago
- Target version deleted (
2.0.1)
JP Updated by Jim Pingle over 14 years ago
- Target version set to 2.1
Seems we need to revisit this again... If a NanoBSD upgrade reinstalls packages, once again it tends to completely hose the system these days until you reboot. Sometimes the GUI will not respond, many processes still sig11, and so on.
PD Updated by Phillip Davis about 14 years ago
I have also seen this behaviour - both filesystem RW and sig11 process exits. Now I know it is not just me I will look harder and see if there are any interesting things in logs before rebooting, try to work out what combinations of packages etc have the symptoms.
EL Updated by Ermal Luçi about 14 years ago
- Status changed from New to Feedback
With changes done to the reference counting code this should be fixed.
JP Updated by Jim Pingle about 14 years ago
- Status changed from Feedback to Resolved
This is fixed from all the tests I've tried, and others on the forum have reported it to be fixed.