From: Hugo Mills <hugo@carfax.org.uk>
To: Nacho Man <nacho2874@yahoo.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: unlinked orphans.
Date: Mon, 23 Dec 2013 09:39:53 +0000 [thread overview]
Message-ID: <20131223093953.GH17179@carfax.org.uk> (raw)
In-Reply-To: <1387780037.66690.YahooMailNeo@web162601.mail.bf1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
On Sun, Dec 22, 2013 at 10:27:17PM -0800, Nacho Man wrote:
> Hello,
> I ran dmesg and saw a bunch of these:
> [564421.874063] BTRFS debug (device sda2): unlinked 32 orphans
> [568021.386733] BTRFS debug (device sda2): unlinked 32 orphans
> [569943.269610] BTRFS debug (device sda2): unlinked 32 orphans
> [570929.840278] BTRFS debug (device sda2): unlinked 32 orphans
> [570942.035251] BTRFS debug (device sda2): unlinked 33 orphans
> [571623.719086] BTRFS debug (device sda2): unlinked 32 orphans
> [572075.684003] BTRFS debug (device sda2): unlinked 32 orphans
>
> I just counted and there's a 175 of them. Do I have to worry? I've been working on a toolchain and some other stuff for the PS3 so my hard drive was being accessed a bit. Could it be related? Thanks.
No, this is harmless. Orphans are files that were deleted while
they were still held open by a process. POSIX semantics requires that
the file data is still readable by the process, but that the file's
hardlink(s) are no longer visible -- so there's no way of finding the
file again by "normal" methods. Once the process closes the file, it
is unlinked.
With btrfs, making a snapshot of a subvolume with (still open)
orphan files in it will close the orphans on the new copy, because
they're new files. This leads to the messages above.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- Ceci est un travail pour l'Australien. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2013-12-23 9:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 6:27 unlinked orphans Nacho Man
2013-12-23 9:39 ` Hugo Mills [this message]
2013-12-23 10:10 ` Duncan
2013-12-24 6:16 ` Nacho Man
2014-01-02 16:04 ` David Sterba
2013-12-23 17:16 ` Chris Murphy
2014-01-02 16:21 ` David Sterba
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=20131223093953.GH17179@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=nacho2874@yahoo.com \
/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).