linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Logtenberg <erik@logtenberg.eu>
To: linux-btrfs@vger.kernel.org
Subject: Re: Kernel error during btrfs balance
Date: Mon, 17 Jan 2011 15:39:42 +0100	[thread overview]
Message-ID: <4D3454AE.5060903@logtenberg.eu> (raw)
In-Reply-To: <4D34543F.3050100@logtenberg.eu>

Hi,

Please disregard that last message, the filesystem did mount after a
period of hanging in state D. Apparently something called an "orphan"
was unlinked:

[  422.323116] btrfs: use compression
[  761.778675] btrfs: unlinked 1 orphans
[  761.841581] SELinux: initialized (dev dm-5, type btrfs), uses xattr

Thanks,

Erik.


On 01/17/2011 03:37 PM, Erik Logtenberg wrote:
> Hi,
> 
> Additionally, I cannot mount the filesystem anymore. mount gives no
> error messages but hangs in state D.
> dmesg shows:
> [  422.323116] btrfs: use compression
> Which is a good thing, but it doesn't do anything otherwise.
> 
> Thanks,
> 
> Erik.
> 
> 
> On 01/17/2011 03:31 PM, Erik Logtenberg wrote:
>> Hi,
>>
>> Please find attached the error log, for future reference.
>>
>> Forgot to mention:
>> I could still use the system after this error, so it was not a complete
>> fatal error in that regard. All active processes (mostly rsync) were
>> hanging in state D though, so I couldn't kill them anymore. Also the FS
>> was not umountable. So I still had to reboot.
>>
>> Thanks,
>>
>> Erik.
>>
>>
>> On 01/17/2011 03:14 PM, Erik Logtenberg wrote:
>>> Hi,
>>>
>>> btrfs balance results in:
>>>
>>> http://pastebin.com/v5j0809M
>>>
>>> My system: fully up-to-date Fedora 14 with rawhide kernel to make btrfs
>>> balance do useful stuff to my free space:
>>>
>>> kernel-2.6.37-2.fc15.x86_64
>>> btrfs-progs-0.19-12.fc14.x86_64
>>>
>>> Filesystem had 0 bytes free, should be 45G, so on darklings advice I ran
>>> btrfs balance on the fs, while doing heavy I/O (re-running 5 backup jobs
>>> that had failed due to ENOSP).
>>> Up until the crash, btrfs balance did retrieve a couple of Gigs free
>>> space though, so that part of the plan worked just fine.
>>>
>>> Thanks,
>>>
>>> Erik.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2011-01-17 14:39 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-17 14:14 Kernel error during btrfs balance Erik Logtenberg
2011-01-17 14:31 ` Erik Logtenberg
2011-01-17 14:37   ` Erik Logtenberg
2011-01-17 14:39     ` Erik Logtenberg [this message]
2011-01-21  8:50   ` Erik Logtenberg
2011-01-21  9:19     ` Yan, Zheng 
2011-01-26  9:04       ` Erik Logtenberg
2011-01-26  9:27         ` Hugo Mills
2011-01-26  9:40           ` Helmut Hullen
2011-01-26  9:46             ` Erik Logtenberg
2011-01-29 10:56             ` Chris Samuel
2011-01-26  9:43           ` Erik Logtenberg
2011-01-18  0:54 ` Yan, Zheng 
2011-01-18 13:22   ` Erik Logtenberg
2011-01-18 13:58     ` Helmut Hullen
2011-01-18 14:13     ` Yan, Zheng 
2011-01-18 14:29       ` Erik Logtenberg

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=4D3454AE.5060903@logtenberg.eu \
    --to=erik@logtenberg.eu \
    --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).