Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Spencer Collyer <spencer@spencercollyer.plus.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Change BTRFS filesystem back to R/W from R/O
Date: Tue, 15 Nov 2022 14:08:47 +0000	[thread overview]
Message-ID: <20221115140847.12fa1902@selket> (raw)
In-Reply-To: <7be0584d-5596-189a-353a-63e4b21c3b5e@gmx.com>

(Resending to the list as I accidentally sent it just to Qu.)

On Tue, 15 Nov 2022 20:41:54 +0800, Qu Wenruo wrote:

> Considering you have some metadata space left, I believe you can free 
> enough space by deleting files (aka, moving it to other filesystems)
> 
> Thanks,
> Qu  

Hi Qu,

Thanks for that. You say I should move some files to other filesystems, but that's really the nub of my problem - the filesystem is marked as read-only. Am I Ok to do what I mentioned previously:

> 1) Unmount the filesystem.
> 2) Remount it as R/W
> 3) Move data to the external disk  

If that is all good, would I need to do anything else or would the BTRFS system sort itself out correctly?

Thanks for your attention,

Spencer

PS. The output form the 'btrfs fi usage /data' command you requested is as follows (run as root to get everything):

Overall:
    Device size:		  10.92TiB
    Device allocated:		  10.92TiB
    Device unallocated:		   1.00MiB
    Device missing:		     0.00B
    Device slack:		     0.00B
    Used:			  10.90TiB
    Free (estimated):		  15.26GiB	(min: 15.26GiB)
    Free (statfs, df):		  15.26GiB
    Data ratio:			      1.00
    Metadata ratio:		      2.00
    Global reserve:		 512.00MiB	(used: 0.00B)
    Multiple profiles:		       yes	(metadata, system)

Data,RAID0: Size:10.87TiB, Used:10.86TiB (99.86%)
   /dev/mapper/data1	   5.44TiB
   /dev/mapper/data2	   5.44TiB

Metadata,single: Size:8.00MiB, Used:0.00B (0.00%)
   /dev/mapper/data1	   8.00MiB

Metadata,RAID1: Size:23.00GiB, Used:21.39GiB (93.00%)
   /dev/mapper/data1	  23.00GiB
   /dev/mapper/data2	  23.00GiB

System,single: Size:4.00MiB, Used:0.00B (0.00%)
   /dev/mapper/data1	   4.00MiB

System,RAID1: Size:8.00MiB, Used:784.00KiB (9.57%)
   /dev/mapper/data1	   8.00MiB
   /dev/mapper/data2	   8.00MiB

Unallocated:
   /dev/mapper/data1	     0.00B
   /dev/mapper/data2	   1.00MiB

  reply	other threads:[~2022-11-15 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 12:27 Change BTRFS filesystem back to R/W from R/O Spencer Collyer
2022-11-15 12:41 ` Qu Wenruo
2022-11-15 14:08   ` Spencer Collyer [this message]
2022-11-15 15:21     ` Spencer Collyer
     [not found]   ` <20221115125208.02a2876d@selket>
2022-11-15 22:46     ` Qu Wenruo
  -- strict thread matches above, loose matches on Subject: below --
2022-11-16  6:40 Forza

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=20221115140847.12fa1902@selket \
    --to=spencer@spencercollyer.plus.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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