linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: A L <mail@lechevalier.se>, Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: how to recover from "enospc errors during balance"
Date: Fri, 02 Oct 2020 11:32:27 +0200	[thread overview]
Message-ID: <87v9ftdlck.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <0afae20d-62d2-00eb-4ac5-fa9b5205a937@lechevalier.se>

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

Hello,

A L <mail@lechevalier.se> writes:

> On 2020-10-01 10:56, Giovanni Biscuolo wrote:

[...]

>> --8<---------------cut here---------------start------------->8---
>>
>> ~$ mount -o skip_balance,relatime,ssd,subvol=/ /dev/sda3 /
>> mount: /: wrong fs type, bad option, bad superblock on /dev/sda3, missing codepage or helper program, or other error.
>>
>> --8<---------------cut here---------------end--------------->8---
>>
>> dmesg says:
>>
>> --8<---------------cut here---------------start------------->8---
>>
>> [7484575.970136] BTRFS info (device sda3): disk space caching is enabled
>> [7484576.001375] BTRFS error (device sda3): Remounting read-write after error is not allowed
>>
>> --8<---------------cut here---------------end--------------->8---
>>
>> Am I doing something wrong?

[...]

> I think you need to mount an unmounted filesystem and not re-mounting it 
> (as per dmesg output).
>
> Example: "mount -o skip_balance /media && btrfs balance cancel /media"

Ah OK, now I understand

> However, I think this is your root filesystem, correct? They you must 
> boot with a bootable media and do recovery from there

Yes it's the roof filesystem of that machine, so yes: I'll have to
recover via bootable media.

> Just remember that deleting data on Btrfs can increase metadata usage, 
> especially if you have lots of snapshots and such. In the case your 
> filesystem goes back into ro mode when deleting files, you may need to 
> add two additional disks (or loop devices, usb sticks etc) to continue.

OK I'll do that.

Thank you both for your support!

Best regards, Giovanni.

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2020-10-02  9:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-29 14:25 how to recover from "enospc errors during balance" Giovanni Biscuolo
2020-09-29 15:07 ` A L
2020-10-01  8:24   ` Giovanni Biscuolo
2020-09-30  0:04 ` Zygo Blaxell
2020-10-01  8:56   ` Giovanni Biscuolo
2020-10-01 15:28     ` A L
2020-10-02  9:32       ` Giovanni Biscuolo [this message]
2020-10-02  2:44     ` Zygo Blaxell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v9ftdlck.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me \
    --to=g@xelera.eu \
    --cc=ce3g8jdj@umail.furryterror.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=mail@lechevalier.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).