Project

General

Profile

Actions
Copy link

Bug #1279

closed

Filesystem on NanoBSD is left read/write at first bootup after package reinstallation

Added by Jim Pingle almost 14 years ago. Updated over 12 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Operating System
Target version:
2.1
Start date:
02/11/2011
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0
Affected Architecture:
All

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.

Actions
Copy link
 #1

Updated by Erik Fonnesbeck almost 14 years ago

Specifically it was 52f4c092b14cca36bcc430717baf907273b66532

I don't think I saw the discussion on this, so I don't know the exact reason that was done.

Actions
Copy link
 #2

Updated by Braden McGrath almost 14 years ago

This is happening in RC1; I haven't yet tried a newer snapshot to check there.

Actions
Copy link
 #3

Updated by Erik Fonnesbeck almost 14 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions
Copy link
 #4

Updated by Jim Pingle over 13 years ago

Actions
Copy link
 #5

Updated by Josh Stompro over 13 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

Actions
Copy link
 #6

Updated by Jim Pingle over 13 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.

Actions
Copy link
 #7

Updated by Ermal Luçi over 13 years ago

  • Status changed from New to Feedback

I put a fix that helps this.
Can you please try with latest snapshots?

Actions
Copy link
 #8

Updated by Jim Pingle over 13 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.

Actions
Copy link
 #9

Updated by Chris Buechler over 13 years ago

  • Priority changed from Normal to High
  • Target version changed from 2.0 to 2.0.1
Actions
Copy link
 #10

Updated by Chris Buechler over 13 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
Actions
Copy link
 #11

Updated by Chris Buechler over 13 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
Actions
Copy link
 #12

Updated by Chris Buechler about 13 years ago

  • Target version deleted (2.0.1)
Actions
Copy link
 #13

Updated by Jim Pingle over 12 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.

Actions
Copy link
 #14

Updated by Phillip Davis over 12 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.

Actions
Copy link
 #15

Updated by Ermal Luçi over 12 years ago

  • Status changed from New to Feedback

With changes done to the reference counting code this should be fixed.

Actions
Copy link
 #16

Updated by Jim Pingle over 12 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.

Actions
Copy link

Also available in: Atom PDF