On Sat, Dec 29, 2012 at 5:28 AM, Hendrik Friedel <[email protected]> wrote: > Hello, > > I re-send this message, hoping that someone can give me a hint? > > Regards, > Hendrik >
Two possibilities come to mind (although there may be others). (1) The file still exists, but it is somewhere you did not expect. (2) Your filesystem tree has some sort of corruption. For item (1), have you thoroughly searched the entire volume for this file with something like: find <path/to/volume/top/level/mount> -iname 'Sting_Live_in_Berlin' It is possible that the file exists in a snapshot or different directory then you were expecting. If the filesystem tree is corrupted, the task becomes tricky. Perhaps you can look at the Wiki entry for how the filesystem tree is constructed: https://btrfs.wiki.kernel.org/index.php/Trees Then examine the btrfs-debug-tree output around these entries, and try to determine why the tree still has entries for these files, but does not show these files nor report the problem with btrfsck. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
