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

Thread: Server crashes with a long BTRFS error list

  1. Re: Server crashes with a long BTRFS error list

    Quote Originally Posted by AAEBHolding View Post
    Which logs should I check? I am in the rescue mode and mounted the root partition as /mnt.
    Can I try to fix it somehow? Running btrfs check --repair /dev/xvda2 doesn't solve the problem. As I wrote, when I then boot regularly the / partion is out of space.
    Hi
    Check down in /var/log for big files, check those for clues (maybe even copy them off to an external drive), especially messages log.

    Maybe it's coredumping?

    Run;

    Code:
    coredumpctl list
    If there are old logs you think can be deleted, remove those and see how it goes getting some disk space.
    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!

  2. #12

    Re: Server crashes with a long BTRFS error list

    Quote Originally Posted by malcolmlewis View Post
    Hi
    Check down in /var/log for big files, check those for clues (maybe even copy them off to an external drive), especially messages log.

    Maybe it's coredumping?

    If there are old logs you think can be deleted, remove those and see how it goes getting some disk space.
    Good, I think I could fix it after hours of desperate trying.
    These 3 threads did it:
    1. https://unix.stackexchange.com/quest...left-on-device
    2. http://marc.merlins.org/perso/btrfs/...-Problems.html
    3. http://marc.merlins.org/perso/btrfs/...-Problems.html


    I summarize what I did:
    1. Start the VM in the rescue mode.
    2. mount /dev/xvda2 /mnt
    3. btrfs balance start -v --full-balance /mnt


    When I got Done, had to relocate 12 out of 12 chunks then it worked (1).
    When I got the message
    ERROR: error during balancing '/mnt' - No space left on device
    There may be more info in syslog - try dmesg | tail

    I had to proceed with (2).

    And here, I had two different situations:
    1) One VM has been completely recovered and works well even before the VM didn't start and crashed while booting - with other words the VM became void.
    2) The other VM was more persistent and really tiresome. I had to find a XenServer snapshot from the VM where the VM did at least start properly even it crashed within few seconds.

    Then, to check if it really works I was running some heavy disk access routines where before the VM crashed within seconds. Now, it runs without any problem.
    I hope, it will remain like this.
    Last edited by AAEBHolding; 18-May-2019 at 21:13.

  3. Re: Server crashes with a long BTRFS error list

    Quote Originally Posted by AAEBHolding View Post
    Good, I think I could fix it after hours of desperate trying.
    These 3 threads did it:
    1. https://unix.stackexchange.com/quest...left-on-device
    2. http://marc.merlins.org/perso/btrfs/...-Problems.html
    3. http://marc.merlins.org/perso/btrfs/...-Problems.html


    I summarize what I did:
    1. Start the VM in the rescue mode.
    2. mount /dev/xvda2 /mnt
    3. btrfs balance start -v --full-balance /mnt


    When I got Done, had to relocate 12 out of 12 chunks then it worked (1).
    When I got the message
    ERROR: error during balancing '/mnt' - No space left on device
    There may be more info in syslog - try dmesg | tail

    I had to proceed with (2).

    And here, I had two different situations:
    1) One VM has been completely recovered and works well even before the VM didn't start and crashed while booting - with other words the VM became void.
    2) The other VM was more persistent and really tiresome. I had to find a XenServer snapshot from the VM where the VM did at least start properly even it crashed within few seconds.

    Then, to check if it really works I was running some heavy disk access routines where before the VM crashed within seconds. Now, it runs without any problem.
    I hope, it will remain like this.
    Hi
    Thanks for the feedback and good work
    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!

  4. #14

    Re: Server crashes with a long BTRFS error list

    I've experienced this exact same error at relocation.c:1449 running "4.12.14-lp150.12.58-default #1 openSUSE Leap 15.0". The call to btrfs_insert_root() within create_reloc_root() returns an error code which causes the subsequent BUG_ON() assertion to fail.

    I'm hopeful that the following commit in the kernel will fix the underlying issue.

    https://bugzilla.kernel.org/show_bug.cgi?id=203405
    https://lkml.org/lkml/2019/6/7/720
    https://github.com/torvalds/linux/co...a9570b6e23eb2b

  5. #15

    Re: Server crashes with a long BTRFS error list

    OMG, after the last updates SUSE offered and I ran it started again. But now I cannot fix it. One VM which had the problem wasn't updated and it doesn't have any problem.
    Again the same. There is no way I fix it with restoring a snapshot. This VM is apparently broken.

Page 2 of 2 FirstFirst 12

Tags for this Thread

Bookmarks

Posting Permissions

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