Re: cleanup after a small data loss on incorrect shutdown.

[Michael Raskin <a0091f122@rambler.ru>]

Chris Mason wrote:
>>> I'd say to send us the btrfsck output, it will help answer these
>>> questions.
>> Oh, easily. "Bad block <number way beyond partition block count>".
> 
> Btrfs deals in byte numbers not block numbers ;)

Interesting to know. Maybe just adding "at" in the message would reduce
confusion.

It doesn't look like it is a canonical bad block anyway.

>> That's all. Reading one of the damaged file actually returned
>> "Input/output error" - probably it tried to read beyond end-of-device. I
>>  had to kill this file (practical testing means that to continue to use
>> my notebook normally I had to nuke the damaged file and get intact
>> copies). The "no such file except in readdir" is still there right now.
> 
> Ok, btrfsck will give us more output when it finishes, but it hasn't
> finished.  It would help to use btrfs-image to send us a coyp of the
> metadata so we can fix the btrfsck bug.

Well, as the partition fills up at ~25 G of 30 G used, I guess that
average metadata size is >=1G for that partition. And now I destroyed
the evidence to make the notebook boot. The disappearing file, though,
is a minor annoyance so I can keep it and do whatever is needed with
btrfs-image..