linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Rich Rauenzahn <rich@shroop.net>,
	Rich Rauenzahn <rrauenza@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: CPU: 3 PID: 439 at fs/btrfs/ctree.h:1559 btrfs_update_device+0x1c5/0x1d0 [btrfs]
Date: Thu, 21 Sep 2017 07:19:39 +0800	[thread overview]
Message-ID: <b45b34b5-1dc5-deda-6725-6e281d0e343c@gmx.com> (raw)
In-Reply-To: <c2161464-65e0-93b9-f118-2f3938deef00@shroop.net>



On 2017年09月21日 02:10, Rich Rauenzahn wrote:
> 
> On 9/20/2017 9:58 AM, Rich Rauenzahn wrote:
>>
>> What's the most direct way to do that?  (Was about to risk breaking 
>> the mirror and repartitioning!  I'd rather not!)
>>
>> Hmm -- maybe this worked:
>>
>> $ sudo btrfs filesystem resize -1m /.MEDIA/
>> Resize '/.MEDIA/' of '-1m'
> No, doesn't seem to have worked.  I used btrfs fi show --raw /.MEDIA to 
> see the size in bytes, and then ...
> 
> sudo btrfs filesystem resize N:SIZE /.MEDIA/
> 

Yes, this is what I did to my fs.
While in fact you can do it better by using:

btrfs fi resize N:max <path>

Or

btrfs fi resize N:-1 <path>

The first one will resize the devid N to its max size.
The 2nd one will resize the devid N to current size - 1 (byte).

Both will go through shrink routine, which will do the round_down.

Thanks,
Qu

> Where N was the disk number in the show output, and SIZE was the number 
> of bytes to set it to that was a multiple of 4k.
> 
> Rich

  reply	other threads:[~2017-09-20 23:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 15:56 WARNING: CPU: 3 PID: 439 at fs/btrfs/ctree.h:1559 btrfs_update_device+0x1c5/0x1d0 [btrfs] Rich Rauenzahn
2017-09-20  0:31 ` Qu Wenruo
2017-09-20  4:49   ` Rich Rauenzahn
2017-09-20  4:59     ` Qu Wenruo
2017-09-20  5:10       ` Qu Wenruo
2017-09-20  5:39         ` Qu Wenruo
2017-09-20  6:11           ` nborisov
2017-09-20  6:23             ` Qu Wenruo
2017-09-20 14:14               ` nborisov
2017-09-20 14:42                 ` Qu Wenruo
2017-09-20 16:53                 ` Rich Rauenzahn
2017-09-20 16:58           ` Rich Rauenzahn
2017-09-20 18:10             ` Rich Rauenzahn
2017-09-20 23:19               ` Qu Wenruo [this message]
2019-08-28 14:21 ` Qu Wenruo

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=b45b34b5-1dc5-deda-6725-6e281d0e343c@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rich@shroop.net \
    --cc=rrauenza@gmail.com \
    /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).