On Tue, Oct 22, 2013 at 06:58:48PM +0100, Martin wrote: > Dear list, > > I've been trying to recover a 2TB single disk btrfs from a good few days > ago as already commented on the list. btrfsck complained of an error in > the extents and so I tried: > > btrfsck --repair --init-extent-tree /dev/sdX > > > That was 8 days ago. > > The btrfs process is still running at 100% cpu but with no disk activity > and no visible change in memory usage. > > Looped? > > Is there any way to check whether it is usefully doing anything or > whether this is a lost cause? > > > The only output it has given, within a few seconds of starting, is: > > > parent transid verify failed on 911904604160 wanted 17448 found 17449 > parent transid verify failed on 911904604160 wanted 17448 found 17449 > parent transid verify failed on 911904604160 wanted 17448 found 17449 > parent transid verify failed on 911904604160 wanted 17448 found 17449 > Ignoring transid failure > > > Any comment/interest before abandoning? > > This all started from trying to delete/repair a directory tree of a few > MBytes of files... >
Sooo it probably is looped, you should be able to attach gdb to it and run bt to see where it is stuck and send that back to the list so we can figure out what to do. Thanks, Josef -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
