Page 2 of 2 FirstFirst 12
Results 11 to 16 of 16

Thread: How to fix btrfsmaintenance

  1. #11

    Default Re: How to fix btrfsmaintenance

    I had experienced this issue of partitions getting unmounted during boot since two months ago, cf. https://forums.opensuse.org/showthread.php/539125-TW-after-update-to-20200211-My-user-hard-drive-partitions-do-not-get-mounted-at-boot-any-longer. Very similar to e.g. https://forums.opensuse.org/showthre...is-not-mounted among the more recent reports on such issue.

    In the meantime, I have been following the recipe by Andre Werlang https://forums.opensuse.org/showthre...tenance-on-SSD to go for a fully manual (i.e. scripted) btrfs maintenance. It works very well, but it leaves me with the little burden of keeping track of when I ran it last and when to run it again.

    Discovering this thread here and in particular Karl Mistelberger's SDB post https://en.opensuse.org/SDB:Fix_btrf...enance-refresh, I switched to Karl Mistelberger's solution some days ago. Up to now, it worked really well. All status outputs show things to be the way they are supposed to.

    However, looking at the associated openSUSE bugzilla discussion at https://bugzilla.suse.com/show_bug.cgi?id=1165780 between Karl Mistelberger and Franck Bui, I for now do unfortunately feel like being in some unhappy state. Seems like the diagnoses and/or the proposed fixes haven't really settled yet. Guess I will have to wait until an "official" fix is agreed upon and will have found its way into the Tumbleweed repositories.

    In the meantime, can I do anything to help with the bugzilla report?

    But then, at that point in the future, I do have a request and a question for you, Karl Mistelberger: The request is that I am asking you to post a note here and on your SDB when and how things are ultimately fixed, i.e. when a Tumbleweed zypper dup brings the solution to the TW installations. And the question is: Please post a recipe here how to revert the changes that I and others made when following your SDB, i.e. (1) how to get rid of the
    Code:
    /etc/systemd/system/btrfsmaintenance-refresh.path.d/override.conf
    file (hmm, just guessing, is it systemctl rm that_file?), and (2) how to bring all relevant service units and timers to their "correct" state.

    Thank you, Karl Mistelberger and Andre Werlang, for all your efforts, and thanks in advance, Karl, for answering the two things raised in the last paragraph right above this one.

  2. #12
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,632

    Default Re: How to fix btrfsmaintenance

    Quote Originally Posted by 111MilesToGo View Post
    I had experienced this issue of partitions getting unmounted during boot since two months ago, cf. https://forums.opensuse.org/showthread.php/539125-TW-after-update-to-20200211-My-user-hard-drive-partitions-do-not-get-mounted-at-boot-any-longer. Very similar to e.g. https://forums.opensuse.org/showthre...is-not-mounted among the more recent reports on such issue.

    In the meantime, I have been following the recipe by Andre Werlang https://forums.opensuse.org/showthre...tenance-on-SSD to go for a fully manual (i.e. scripted) btrfs maintenance. It works very well, but it leaves me with the little burden of keeping track of when I ran it last and when to run it again.

    Discovering this thread here and in particular Karl Mistelberger's SDB post https://en.opensuse.org/SDB:Fix_btrf...enance-refresh, I switched to Karl Mistelberger's solution some days ago. Up to now, it worked really well. All status outputs show things to be the way they are supposed to.

    However, looking at the associated openSUSE bugzilla discussion at https://bugzilla.suse.com/show_bug.cgi?id=1165780 between Karl Mistelberger and Franck Bui, I for now do unfortunately feel like being in some unhappy state. Seems like the diagnoses and/or the proposed fixes haven't really settled yet. Guess I will have to wait until an "official" fix is agreed upon and will have found its way into the Tumbleweed repositories.

    In the meantime, can I do anything to help with the bugzilla report?

    But then, at that point in the future, I do have a request and a question for you, Karl Mistelberger: The request is that I am asking you to post a note here and on your SDB when and how things are ultimately fixed, i.e. when a Tumbleweed zypper dup brings the solution to the TW installations. And the question is: Please post a recipe here how to revert the changes that I and others made when following your SDB, i.e. (1) how to get rid of the
    Code:
    /etc/systemd/system/btrfsmaintenance-refresh.path.d/override.conf
    file (hmm, just guessing, is it systemctl rm that_file?), and (2) how to bring all relevant service units and timers to their "correct" state.

    Thank you, Karl Mistelberger and Andre Werlang, for all your efforts, and thanks in advance, Karl, for answering the two things raised in the last paragraph right above this one.

    1. Don't delete the changes if you experience umounting during boot. Otherwise you may delete the file: 'rm /etc/systemd/system/btrfsmaintenance-refresh.path.d/override.conf' and run: 'systemctl daemon-reload' for changes to take effect.
    2. Run the following: 'systemctl enable btrfsmaintenance-refresh.path' and 'systemctl disable btrfsmaintenance-refresh.service' Verify the changes made: https://en.opensuse.org/SDB:Fix_btrf..._correct_state
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  3. #13
    Join Date
    Mar 2020
    Location
    São Leopoldo, RS, Brazil
    Posts
    158

    Default Re: How to fix btrfsmaintenance

    Quote Originally Posted by 111MilesToGo View Post
    But then, at that point in the future, I do have a request and a question for you, Karl Mistelberger: The request is that I am asking you to post a note here and on your SDB when and how things are ultimately fixed, i.e. when a Tumbleweed zypper dup brings the solution to the TW installations. And the question is: Please post a recipe here how to revert the changes that I and others made when following your SDB, i.e. (1) how to get rid of the
    Code:
    /etc/systemd/system/btrfsmaintenance-refresh.path.d/override.conf
    file (hmm, just guessing, is it systemctl rm that_file?), and (2) how to bring all relevant service units and timers to their "correct" state.
    If you use `systemctl edit service-name` to override a service, the reversion of that is:

    Code:
    systemctl revert btrfsmaintenance-refresh.path
    It removes the override file and directory from /etc/* and reloads systemd.
    openSUSE Tumbleweed

  4. #14
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,632

    Default Re: How to fix btrfsmaintenance

    Quote Originally Posted by awerlang View Post
    If you use `systemctl edit service-name` to override a service, the reversion of that is:

    Code:
    systemctl revert btrfsmaintenance-refresh.path
    It removes the override file and directory from /etc/* and reloads systemd.
    Yes, see 'systemctl --help': revert UNIT... Revert one or more unit files to vendor version. You always have 2 options: use built-in command or edit manually and reload. You may want to verify the result with 'systemctl cat'.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

  5. #15
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    20,823
    Blog Entries
    14

    Default Re: How to fix btrfsmaintenance

    Hey, Karl,
    Thanks for posting this. I was today hit by /opt not mounting during boot, and having followed this thread, it was easily solved. I disabled the ....refresh.service, enabled the ...refresh.path and the issues ( of course everything in /opt was affected ) are indeed gone after a reboot. IMNSHO this should be fixed in TW a.s.a.p. People are using Chrome ( whether we like it or not ) and docker ( containerd puts stuff there ).
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  6. #16
    Join Date
    Jan 2014
    Location
    Erlangen
    Posts
    1,632

    Default Re: How to fix btrfsmaintenance

    Quote Originally Posted by Knurpht View Post
    IMNSHO this should be fixed in TW a.s.a.p. People are using Chrome ( whether we like it or not ) and docker ( containerd puts stuff there ).
    You can help: https://forums.opensuse.org/showthre...26#post2933726

    systemd 245 is fixed. If your version still exhibits the bug consider reporting.
    AMD Athlon 4850e (2009), openSUSE 13.1, KDE 4, Intel i3-4130 (2014), i7-6700K (2016), i5-8250U (2018), AMD Ryzen 5 3400G (2020), openSUSE Tumbleweed, KDE Plasma 5

Page 2 of 2 FirstFirst 12

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •