Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Maciej Marcin Piechotka <uzytkownik2@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: btrfs: could not do orphan cleanup -116
Date: Mon, 07 Nov 2011 13:17:04 +0000	[thread overview]
Message-ID: <1320671824.2445.8.camel@picard> (raw)

[-- Attachment #1: Type: text/plain, Size: 1312 bytes --]

Hello,

When I booted my machine (after clean powerdown) the following message
appeared:
[   32.757913] device fsid XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX devid 1
transid 40864 /dev/mapper/XXXXX-XXXXX
[   32.758466] btrfs: use lzo compression
[   32.758475] btrfs: enabling disk space caching
[   32.758483] btrfs: enabling inode map caching
[   32.758490] btrfs: enabling auto defrag
[   32.758497] btrfs: thread pool 2
[   34.024359] btrfs: could not do orphan cleanup -116
[   63.173382] btrfs: open_ctree failed

btrfsck has shown no errors.

Afterwards when I tried to mount filesystem it have shown:

[  116.012528] btrfs: enabling inode map caching
[  116.012534] btrfs: enabling auto defrag
[  116.012542] btrfs: thread pool 2

It looked like everything is working but to be sure I've run scrub:

scrub status for fsid XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
        scrub started at Mon Nov  7 13:05:50 2011 and finished after 606
seconds
        total bytes scrubbed: 32.37GB with 0 errors

PS. 
# find include | xargs grep 116
(...)
include/asm-generic/errno.h:#define     ESTALE          116     /* Stale
NFS file handle */
(...)

I don't use NFS - I use LVM on LUKS. In any case - it have been done
concurrently with mounting of other fs which had no such problems.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2011-11-07 13:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-07 13:17 Maciej Marcin Piechotka [this message]
2011-11-07 15:29 ` btrfs: could not do orphan cleanup -116 Josef Bacik
2011-11-07 18:41   ` Maciej Marcin Piechotka
2011-11-07 19:01     ` Josef Bacik
2011-11-09 15:43       ` Maciej Marcin Piechotka
2011-11-09 16:14         ` Josef Bacik
2011-11-09 16:18           ` Maciej Marcin Piechotka

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=1320671824.2445.8.camel@picard \
    --to=uzytkownik2@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