All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Navitsky <john@navitsky.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: system stuck with flush-btrfs-4 at 100% after filesystem resize
Date: Mon, 10 Feb 2014 07:35:32 -0800	[thread overview]
Message-ID: <52F8F1C4.5070701@navitsky.org> (raw)
In-Reply-To: <52F67926.7060209@navitsky.org>

As a follow-up, at some point over the weekend things did finish on 
their own:

romulus:/vms/johnn-sles11sp3 # df -h /vms
Filesystem      Size  Used Avail Use% Mounted on
/dev/dm-4       2.6T  1.6T  1.1T  60% /vms
romulus:/vms/johnn-sles11sp3 #

I'd still be interested in any comments about what was going on or 
suggestions.

Thanks,

-john

On 2/8/2014 10:36 AM, John Navitsky wrote:
> Hello,
>
> I have a large file system that has been growing.  We've resized it a
> couple of times with the following approach:
>
>    lvextend -L +800G /dev/raid/virtual_machines
>    btrfs filesystem resize +800G /vms
>
> I think the FS started out at 200G, we increased it by 200GB a time or
> two, then by 800GB and everything worked fine.
>
> The filesystem hosts a number of virtual machines so the file system is
> in use, although the VMs individually tend not to be overly active.
>
> VMs tend to be in subvolumes, and some of those subvolumes have snapshots.
>
> This time, I increased it by another 800GB, and it it has hung for many
> hours (over night) with flush-btrfs-4 near 100% cpu all that time.
>
> I'm not clear at this point that it will finish or where to go from here.
>
> Any pointers would be much appreciated.
>
> Thanks,
>
> -john (newbie to BTRFS)


  reply	other threads:[~2014-02-10 15:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 18:36 system stuck with flush-btrfs-4 at 100% after filesystem resize John Navitsky
2014-02-10 15:35 ` John Navitsky [this message]
2014-02-11  5:23   ` Duncan
2014-02-10 16:43 ` Josef Bacik
2014-02-10 16:52   ` John Navitsky

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=52F8F1C4.5070701@navitsky.org \
    --to=john@navitsky.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.