linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell Coker <russell@coker.com.au>
To: linux-btrfs@vger.kernel.org
Subject: 3.14.2 Debian kernel BTRFS corruption after balance
Date: Mon, 19 May 2014 18:43:38 +1000	[thread overview]
Message-ID: <2019232.PTU0Tffgio@russell.coker.com.au> (raw)

Last night my cron job that runs "/sbin/btrfs fi balance start -dusage=30 -
musage=30 /" failed with no space for balancing.  Then I manually ran it to 
free space for further balancing and ended up running -musage=0 -dusage=60 
(dusage=40 resulted in nothing being done).

http://www.coker.com.au/bug/btrfs-3.14.2-dmesg.txt.gz

After running the dusage=60 balance I had a kernel panic apparently due to a 
corrupted filesystem, the above URL has the dmesg.

http://www.coker.com.au/bug/btrfs-3.14.2-dmesg2.txt.gz

Then I rebooted the system and got the above error.  It now seems impossible 
to get a read-write filesystem.  I'll try booting with the latest Debian kernel 
(3.14.4) and see if that makes it work.  Otherwise I guess it's 
backup/format/restore.

Would it be worth keeping an image of that filesystem to see if a newer kernel 
can handle it better?

-- 
My Main Blog         http://etbe.coker.com.au/
My Documents Blog    http://doc.coker.com.au/


                 reply	other threads:[~2014-05-19  8:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=2019232.PTU0Tffgio@russell.coker.com.au \
    --to=russell@coker.com.au \
    --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;
as well as URLs for NNTP newsgroup(s).