From: Pavel Volkov <negaipub@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error: could not do orphan cleanup -22
Date: Wed, 12 Feb 2014 18:38:26 +0400 [thread overview]
Message-ID: <1928972.8tGm4hVmjn@melforce> (raw)
In-Reply-To: <2426118.ZFJLMUnzLe@melforce>
On Wednesday 12 February 2014 11:32:30 Pavel Volkov wrote:
> On Monday 10 February 2014 16:13:40 Josef Bacik wrote:
> > Build a kernel with this patch applied
> >
> > http://ur1.ca/glslj
> >
> > and re-run the mount and when it fails attach dmesg to this email.
> > Thanks,
> >
> > Josef
>
> Now I re-created the filesystem and have the error again.
> Attaching dmesg with patch.
> The last error happened when I tried to create a snapshot (from a cron
> script).
And I'll add some later messages messages from the same boot.
This time inode 153006 unlinked successfully:
2月 12 11:37:44 melforce kernel: found orphan item for inode 88407, last_objectid 0
2月 12 11:37:44 melforce kernel: unlink is happening
2月 12 11:37:44 melforce kernel: found orphan item for inode 88407, last_objectid 88407
2月 12 11:37:44 melforce kernel: BTRFS error (device sdb3): Error removing orphan entry, stopping orphan cleanup
2月 12 11:37:44 melforce kernel: BTRFS critical (device sdb3): could not do orphan cleanup -22
2月 12 11:38:57 melforce kernel: found orphan item for inode 155269, last_objectid 0
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 153006, last_objectid 155269
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 152927, last_objectid 153006
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 152926, last_objectid 152927
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 152385, last_objectid 152926
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 152384, last_objectid 152385
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 152377, last_objectid 152384
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 152373, last_objectid 152377
2月 12 11:38:58 melforce kernel: unlink is happening
2月 12 11:38:58 melforce kernel: found orphan item for inode 152372, last_objectid 152373
2月 12 11:38:58 melforce kernel: unlink is happening
prev parent reply other threads:[~2014-02-12 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-09 20:20 Error: could not do orphan cleanup -22 Pavel Volkov
2014-02-10 19:38 ` Pavel Volkov
2014-02-10 20:53 ` Pavel Volkov
2014-02-10 21:13 ` Josef Bacik
2014-02-10 21:52 ` Pavel Volkov
2014-02-12 7:32 ` Pavel Volkov
2014-02-12 14:38 ` Pavel Volkov [this message]
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=1928972.8tGm4hVmjn@melforce \
--to=negaipub@gmail.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