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:
signature.asc
Description: Digital signature
