On 2019/1/16 上午9:38, Chris Murphy wrote:
> On Tue, Jan 15, 2019 at 5:04 AM David Sterba wrote:
>>
>> On Tue, Jan 15, 2019 at 07:48:47PM +0800, Qu Wenruo wrote:
>>> Super nice move, it shows the corruption and the cause.
>>>
>>> item 66 key (1714119835648 METADATA_ITEM 0) itemoff 13325 item
On Tue, Jan 15, 2019 at 5:04 AM David Sterba wrote:
>
> On Tue, Jan 15, 2019 at 07:48:47PM +0800, Qu Wenruo wrote:
> > Super nice move, it shows the corruption and the cause.
> >
> > item 66 key (1714119835648 METADATA_ITEM 0) itemoff 13325 itemsize 33
> > item 67 key (10510212874240 M
Qu Wenruo writes:
>> I'm working on the fix.
>> Please make sure there is no write into the fs (just in case, since the
>> fs should be RO).
>
> Here it is:
> https://github.com/adam900710/btrfs-progs/tree/dirty_fix_for_leonard_lausen
>
> You need to git checkout the branch, and then compile.
> (N
On 2019/1/15 下午8:28, Leonard Lausen wrote:
>
> Thanks Qu and David for your prompt attention!
>
> Qu Wenruo writes:
>>> following tree-dumps:
>>>
>>> sudo btrfs inspect dump-tree -t root /dev/mapper/vg1-root >
>>> /tmp/btrfsdumproot
>>> sudo btrfs inspect dump-tree -b 1350630375424 /dev/m
Thanks Qu and David for your prompt attention!
Qu Wenruo writes:
>> following tree-dumps:
>>
>> sudo btrfs inspect dump-tree -t root /dev/mapper/vg1-root >
>> /tmp/btrfsdumproot
>> sudo btrfs inspect dump-tree -b 1350630375424 /dev/mapper/vg1-root >
>> /tmp/btrfsdump1350630375424
>>
>>
On 2019/1/15 下午7:48, Qu Wenruo wrote:
>
>
> On 2019/1/15 下午7:28, Leonard Lausen wrote:
>> Hi everyone,
>>
>> I just found my btrfs filesystem to be remounted read-only with the
>> following in my journalctl [1]:
>>
>> Jan 15 08:56:40 leonard-xps13 kernel: BTRFS critical (device dm-2):
>> cor
On 2019/1/15 下午8:03, David Sterba wrote:
> On Tue, Jan 15, 2019 at 07:48:47PM +0800, Qu Wenruo wrote:
>> Super nice move, it shows the corruption and the cause.
>>
>> item 66 key (1714119835648 METADATA_ITEM 0) itemoff 13325 itemsize 33
>> item 67 key (10510212874240 METADATA_ITEM 0) it
On 2019/1/15 下午7:51, David Sterba wrote:
> On Tue, Jan 15, 2019 at 07:48:47PM +0800, Qu Wenruo wrote:
>>> following tree-dumps:
>>>
>>> sudo btrfs inspect dump-tree -t root /dev/mapper/vg1-root >
>>> /tmp/btrfsdumproot
>>> sudo btrfs inspect dump-tree -b 1350630375424 /dev/mapper/vg1-root >
On Tue, Jan 15, 2019 at 07:48:47PM +0800, Qu Wenruo wrote:
> Super nice move, it shows the corruption and the cause.
>
> item 66 key (1714119835648 METADATA_ITEM 0) itemoff 13325 itemsize 33
> item 67 key (10510212874240 METADATA_ITEM 0) itemoff 13283 itemsize 42
> item 68 key (1
On Tue, Jan 15, 2019 at 07:48:47PM +0800, Qu Wenruo wrote:
> > following tree-dumps:
> >
> > sudo btrfs inspect dump-tree -t root /dev/mapper/vg1-root >
> > /tmp/btrfsdumproot
> > sudo btrfs inspect dump-tree -b 1350630375424 /dev/mapper/vg1-root >
> > /tmp/btrfsdump1350630375424
> >
> > Th
On 2019/1/15 下午7:28, Leonard Lausen wrote:
> Hi everyone,
>
> I just found my btrfs filesystem to be remounted read-only with the
> following in my journalctl [1]:
>
> Jan 15 08:56:40 leonard-xps13 kernel: BTRFS critical (device dm-2): corrupt
> leaf: root=2 block=1350630375424 slot=68, bad
Hi everyone,
I just found my btrfs filesystem to be remounted read-only with the
following in my journalctl [1]:
Jan 15 08:56:40 leonard-xps13 kernel: BTRFS critical (device dm-2): corrupt
leaf: root=2 block=1350630375424 slot=68, bad key order, prev (10510212874240
169 0) current (1714119868
12 matches
Mail list logo
