From: Pavel Volkov <negaipub@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error: could not do orphan cleanup -22
Date: Tue, 11 Feb 2014 01:52:42 +0400 [thread overview]
Message-ID: <1726046.kZYFW4zOS4@melforce> (raw)
In-Reply-To: <52F94104.4030201@fb.com>
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,
I don't see these new messages nor the previous "-22" messages in dmesg now.
Only the access problem:
melforce mnt # ls btr2
home vap-snap1 vap-snap2 var
melforce mnt # ls btr2/var-snap1
ls: cannot access btr2/var-snap1: No such file or directory
melforce mnt # ls btr2/var
cache db empty lib lock log mail nmbd run spool src tmp www
next prev parent reply other threads:[~2014-02-10 21:52 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 [this message]
2014-02-12 7:32 ` Pavel Volkov
2014-02-12 14:38 ` Pavel Volkov
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=1726046.kZYFW4zOS4@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;
as well as URLs for NNTP newsgroup(s).