Re: Filesystem won't mount (open_ctree failed) or repair (BUG_ON)

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

 



Op 12-06-17 om 01:00 schreef Chris Murphy:
> On Sun, Jun 11, 2017 at 4:13 AM, Koen Kooi <koen@xxxxxxxxxxxxxxxxxxxxx> wrote:
>>
>>> Op 11 jun. 2017, om 12:05 heeft Koen Kooi <koen@xxxxxxxxxxxxxxxxxxxxx> het volgende geschreven:
>>>
>>>>
>>>> Op 11 jun. 2017, om 06:20 heeft Chris Murphy <lists@xxxxxxxxxxxxxxxxx> het volgende geschreven:
>>>>
>>>> On Fri, Jun 9, 2017 at 1:57 PM, Hugo Mills <hugo@xxxxxxxxxxxxx> wrote:
>>
>> [..]
>>
>>>> I'd say take a btrfs-image and put it up somewhere and also file a
>>>> bug. The fsck should not crash.
>>>
>>> I’ll create a bugzilla account and file a bug for that.
>>
>> Done: https://bugzilla.kernel.org/show_bug.cgi?id=196031
>>
>> Btrfs-image is still running, will put it online when it has finished. It’s already 1.2G:
>>
>> koen@beast:~$ du -ms /data/backup/btrfs.img
>> 1205    /data/backup/btrfs.img
> 
> Hopefully you're using -s -t4 -c9 but if not you can at least compress
> it after the fact but that takes even longer.

I wasn't using '-s', after I did it and ran it again it shrunk from 14GiB to 733MiB:

	https://dominion.thruhere.net/btrfs.img

xz -9 -e wouldn't only compressed that 14GiB file to 13.99GiB, so I wonder why '-s' seems to make such a difference.

regards,

Koen


--
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