Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 22

Thread: Unable to update

  1. #11
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,395
    Blog Entries
    1

    Default Re: Unable to update

    Quote Originally Posted by thestig View Post
    I didn't think Leap 42.1 was that old, so I'm surprised if what you're saying is true about it being discontinued (in terms of update support) so soon. I thought they usually run 3 versions at once then when a 4th comes out, the 1st gets discontinued?

    Cheers
    Have a read of the following....
    https://en.opensuse.org/Lifetime
    Maintained Regular distributions

    The following distributions are expected to receive updates until the specified date:

    • Leap 42.1 - will be maintained until 6 months after 42.2 (May 16th 2017)
    • Leap 42.2 - will be maintained until 6 months after 42.3 (EXPECTED Second Quarter of 2018)

  2. #12

    Default Re: Unable to update

    That's very useful, thank you for that! Looks like 42.2 will be supported for quite a while at least.

    Bit concerning my root partition was so full. After the fresh install it's now got over 13gb free. Short of periodically deleting the tmp directory, and disabling snapper, is there any other way to ensure that it doesn't get full?

    Cheers

  3. #13
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,748

    Default Re: Unable to update

    Don't put things in it LOL

    But it all depends on your usage.

    Snapper just does not do well with root partitions significantly under 40 gig.

  4. #14

    Default Re: Unable to update

    Quote Originally Posted by gogalthorp View Post
    Don't put things in it LOL

    But it all depends on your usage.

    Snapper just does not do well with root partitions significantly under 40 gig.
    I never purposefully put anything in temp, I always try to save stuff to /home or a USB hard drive, and yet, over time, the root partition still got full.....?

  5. #15
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,748

    Default Re: Unable to update

    With snapper on or off??

    Snapper does use space and if you have less then the minimum recommended then it may use most of the available thus reducing available space

    /tmp is cleaned out on boot I think

  6. #16

    Default Re: Unable to update

    On 03/09/2017 08:46 AM, gogalthorp wrote:
    >
    > With snapper on or off??
    >
    > Snapper does use space and if you have less then the minimum recommended
    > then it may use most of the available thus reducing available space
    >
    > /tmp is cleaned out on boot I think
    >
    >


    I don't remember where zypper cache is located, perhaps that is using
    space as well.

    zypper clean

    can be used to clear the cache directory.
    You might want to allocate 100G to / next time to at least give you time
    to monitor disk usage.

    --
    Ken
    linux since 1994
    S.u.S.E./openSUSE since 1996

  7. #17

    Default Re: Unable to update

    Thanks everyone. I'm half contemplating using something like gparted to shrink my /home by 20gb or so, and increase the root partition, though obviously it's a fairly risky business doing so.

    Snapper was disabled, yes

  8. #18
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    26,865
    Blog Entries
    15

    Default Re: Unable to update

    Quote Originally Posted by thestig View Post
    Thanks everyone. I'm half contemplating using something like gparted to shrink my /home by 20gb or so, and increase the root partition, though obviously it's a fairly risky business doing so.

    Snapper was disabled, yes
    Hi
    So if it's using btrfs, then you still need to look at running btrfs-balance which should recover space before looking at adjust partition sizes...
    Code:
    btrfs fi usage /
    Are the btrfs maintenance tools installed?
    Code:
    zypper in btrfsmaintenance
    /etc/cron.weekly/btrfs-balance
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  9. #19

    Default Re: Unable to update

    Hi,

    thanks for your help thus far. Here's an output for you...

    ross@linux-p7rj:~> su
    Password:
    linux-p7rj:/home/ross # btrfs fi usage /
    Overall:
    Device size: 20.00GiB
    Device allocated: 8.13GiB
    Device unallocated: 11.87GiB
    Device missing: 0.00B
    Used: 6.18GiB
    Free (estimated): 13.21GiB (min: 7.28GiB)
    Data ratio: 1.00
    Metadata ratio: 2.00
    Global reserve: 96.00MiB (used: 0.00B)

    Data,single: Size:7.01GiB, Used:5.67GiB
    /dev/sdb4 7.01GiB

    Metadata,DUP: Size:512.00MiB, Used:264.84MiB
    /dev/sdb4 1.00GiB

    System,DUP: Size:64.00MiB, Used:16.00KiB
    /dev/sdb4 128.00MiB

    Unallocated:
    /dev/sdb4 11.87GiB
    linux-p7rj:/home/ross #

    Does that mean anything for you?

    Thanks!

    Bare in mind this is my clean install.


  10. #20

    Default Re: Unable to update

    Sorry, for this is a long one....btrfs balance already installed....

    linux-p7rj:/home/ross # /etc/cron.weekly/btrfs-balance
    Before balance of /
    Data, single: total=7.01GiB, used=5.67GiB
    System, DUP: total=64.00MiB, used=16.00KiB
    Metadata, DUP: total=512.00MiB, used=264.89MiB
    GlobalReserve, single: total=96.00MiB, used=0.00B
    Filesystem Size Used Avail Use% Mounted on
    /dev/sdb4 22G 6.8G 15G 33% /
    Done, had to relocate 1 out of 14 chunks
    Dumping filters: flags 0x1, state 0x0, force is off
    DATA (flags 0x2): balancing, usage=1
    Done, had to relocate 1 out of 14 chunks
    Dumping filters: flags 0x1, state 0x0, force is off
    DATA (flags 0x2): balancing, usage=5
    Done, had to relocate 1 out of 14 chunks
    Dumping filters: flags 0x1, state 0x0, force is off
    DATA (flags 0x2): balancing, usage=10
    Done, had to relocate 1 out of 14 chunks
    Dumping filters: flags 0x1, state 0x0, force is off
    DATA (flags 0x2): balancing, usage=20
    Done, had to relocate 1 out of 14 chunks
    Dumping filters: flags 0x1, state 0x0, force is off
    DATA (flags 0x2): balancing, usage=30
    Done, had to relocate 1 out of 14 chunks
    Dumping filters: flags 0x1, state 0x0, force is off
    DATA (flags 0x2): balancing, usage=40
    Done, had to relocate 1 out of 14 chunks
    Dumping filters: flags 0x1, state 0x0, force is off
    DATA (flags 0x2): balancing, usage=50
    Done, had to relocate 1 out of 14 chunks
    Done, had to relocate 2 out of 14 chunks
    Dumping filters: flags 0x6, state 0x0, force is off
    METADATA (flags 0x2): balancing, usage=1
    SYSTEM (flags 0x2): balancing, usage=1
    Done, had to relocate 1 out of 12 chunks
    Dumping filters: flags 0x6, state 0x0, force is off
    METADATA (flags 0x2): balancing, usage=5
    SYSTEM (flags 0x2): balancing, usage=5
    Done, had to relocate 1 out of 12 chunks
    Dumping filters: flags 0x6, state 0x0, force is off
    METADATA (flags 0x2): balancing, usage=10
    SYSTEM (flags 0x2): balancing, usage=10
    Done, had to relocate 1 out of 12 chunks
    Dumping filters: flags 0x6, state 0x0, force is off
    METADATA (flags 0x2): balancing, usage=20
    SYSTEM (flags 0x2): balancing, usage=20
    Done, had to relocate 1 out of 12 chunks


    Is this a command I should run regularly then?

Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

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