Re: 3.19.6: __btrfs_free_extent:5987: errno=-2 No such entry, did btrfs check --repair break it?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris Murphy posted on Wed, 06 May 2015 11:25:51 -0600 as excerpted:

> On Wed, May 6, 2015 at 5:04 AM, Duncan <1i5t5.duncan@xxxxxxx> wrote:
> 
>> Long story short, nothing I tried (mounting with recovery, the new
>> integrated btrfs rescue zero-log, btrfs check --repair...)
> 
> What is integrated btrfs rescue zero-log btrfs check? Where is it? I
> don't see a check or repair option in btrfs rescue, I do see zero-log
> (and chunk-recover and super-recover).

I think you misread me.  Either that or I'm misreading you and am totally 
confused about what your question is...

Btrfs-zero-log was previously its own command.  In 4.0 it has moved under 
the btrfs rescue command as btrfs rescue zero-log.  That's what I was 
referring to as the new integrated btrfs rescue zero-log.

Then there's a comma, and specifically stated btrfs check --repair 
(starting with btrfs, thus suggesting an entirely new command as that's 
what btrfs commands start with), a /separate/ command I ran.

I'm not sure where you got btrfs rescue zero log btrfs check, apparently 
interpreting that as a single command, despite the comma and repeated 
btrfs, and the hint in "nothing I tried", which suggests several things 
were tried...

So someone's obviously confused, but I'm not sure if it's you or me or 
both! =:^)

>> So I got to use the new btrfs-progs v4.0 metadata-restoration option in
>> btrfs restore,
> 
> In man btrfs-restore I only see a -m option, is that what you're
> referring to?

Yes.  That too is new in 4.0, the patch in fact being new enough I wasn't 
actually expecting to see it in a release until 4.1 or at least 4.0.1.

But it works well (except with dry-run, -D, which apparently is falling a 
bit behind as it still has the too many loops error from older code that 
no longer affects a normal write-out run, too). =:^)

Since I suggested restoring ownership/perms to the person who came up 
with the patch (his first one restored dates but not ownership/perms, as 
the date issue was his itch and he scratched it, so I suggested ownership/
perms too, my itch, which not being a coder I can't scratch directly), 
I'm happy as a kid at Christmas! =:^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux