All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Christian Wimmer <telefonchris@icloud.com>, Qu WenRuo <wqu@suse.com>
Cc: Anand Jain <anand.jain@oracle.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] btrfs-progs: Skip device tree when we failed to read it
Date: Wed, 11 Dec 2019 08:36:37 +0800	[thread overview]
Message-ID: <985d1845-d211-9134-4c9b-85a0956e7404@gmx.com> (raw)
In-Reply-To: <18F0134D-AFF9-4CB9-A996-E44AC949DCAA@icloud.com>


[-- Attachment #1.1: Type: text/plain, Size: 2280 bytes --]



On 2019/12/11 上午5:25, Christian Wimmer wrote:
> Hi Qu and all others,
> 
> thanks a lot for your help and patience!
> 
> Unfortunately I could not get out any file from the arrive yet but I can survive.
> 
> I would like just one more answer from you. Do you think with the newest version of btrfs it would not have happened?

From the result, it looks like either btrfs is doing wrong trim, or the
storage stack below (including the Parallels, the apple fs, and the
apple drivers) is blowing up data.

In the latter case, it doesn't matter whatever kernel version you're
using, if it happens, it will take your data along with it.

But for the former case, newer kernel has improved trim check to prevent
bad trim, so at least newer kernel is a little more safer.

> Should I update to the newest version?

Not always the newest, although we're trying our best to prevent bugs,
but sometimes we still have some bugs sneaking into latest kernel.

> 
> I have many partitions with btrfs and I like them a lot. Very nice file system indeed but am I safe with the version that I have (4.19.1)?

Can't say it's unsafe, since SUSE has all necessary backports and quite
some customers are using (testing) it.
As long as you're using the latest SUSE updates, it should be safe and
all found bugs should have fixes backported.

Thanks,
Qu
> 
> BTW, you are welcome to suggest any command or try anything with my broken file system that I still have backed up in case that you want to experiment with it.
> 
> Thanks 
> 
> Chris
> 
> 
>> On 7. Dec 2019, at 22:21, Qu WenRuo <wqu@suse.com> wrote:
>>
>>
>>
>> On 2019/12/8 上午12:44, Christian Wimmer wrote:
>>> Hi Qu,
>>>
>>> I was reading about chunk-recover. Do you think this could be worth a try?
>>
>> Nope, your chunk tree is good, so that makes no sense.
>>
>>>
>>> Is there any other command that can search for files that make sense to recover?
>>
>> The only sane behavior here is to search the whole disk and grab
>> anything looks like a tree block, and then extract data from it.
>>
>> This is not something supported by btrfs-progs yet, so really not much
>> more can be done here.
>>
>> Thanks,
>> Qu
>>
>>>
>>> Regards,
>>>
>>> Chris
>>>
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-12-11  0:37 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06  3:44 [PATCH] btrfs-progs: Skip device tree when we failed to read it Qu Wenruo
2019-12-06  6:12 ` Anand Jain
2019-12-06 15:50   ` Christian Wimmer
2019-12-06 16:34   ` Christian Wimmer
     [not found]   ` <762365A0-8BDF-454B-ABA9-AB2F0C958106@icloud.com>
2019-12-07  1:16     ` Qu WenRuo
2019-12-07  3:47       ` Christian Wimmer
2019-12-07  4:31         ` Qu Wenruo
2019-12-07 13:03           ` Christian Wimmer
2019-12-07 14:10             ` Qu Wenruo
2019-12-07 14:25               ` Christian Wimmer
2019-12-07 16:44               ` Christian Wimmer
2019-12-08  1:21                 ` Qu WenRuo
2019-12-10 21:25                   ` Christian Wimmer
2019-12-11  0:36                     ` Qu Wenruo [this message]
2019-12-11 15:57                       ` Christian Wimmer
     [not found]           ` <9FB359ED-EAD4-41DD-B846-1422F2DC4242@icloud.com>
2020-01-04 17:07             ` 12 TB btrfs file system on virtual machine broke again Christian Wimmer
2020-01-05  4:03               ` Chris Murphy
2020-01-05 13:40                 ` Christian Wimmer
2020-01-05 14:07                   ` Martin Raiber
2020-01-05 14:14                     ` Christian Wimmer
2020-01-05 14:23                       ` Christian Wimmer
2020-01-05  4:25               ` Qu Wenruo
2020-01-05 14:17                 ` Christian Wimmer
2020-01-05 18:50                   ` Chris Murphy
2020-01-05 19:18                     ` Christian Wimmer
2020-01-05 19:36                       ` Chris Murphy
2020-01-05 19:49                         ` Christian Wimmer
2020-01-05 19:52                         ` Christian Wimmer
2020-01-05 20:34                           ` Chris Murphy
2020-01-05 20:36                             ` Chris Murphy
     [not found]                         ` <3F43DDB8-0372-4CDE-B143-D2727D3447BC@icloud.com>
2020-01-05 20:30                           ` Chris Murphy
2020-01-05 20:36                             ` Christian Wimmer
2020-01-05 21:13                               ` Chris Murphy
2020-01-05 21:58                                 ` Christian Wimmer
2020-01-05 22:28                                   ` Chris Murphy
2020-01-06  1:31                                     ` Christian Wimmer
2020-01-06  1:33                                     ` Christian Wimmer
2020-01-11 17:04                                     ` 12 TB btrfs file system on virtual machine broke again (third time) Christian Wimmer
2020-01-11 17:23                                     ` Christian Wimmer
2020-01-11 19:46                                       ` Chris Murphy
2020-01-13 19:41                                         ` 12 TB btrfs file system on virtual machine broke again (fourth time) Christian Wimmer
2020-01-13 20:03                                           ` Chris Murphy
2020-01-31 16:35                                             ` btrfs not booting any more Christian Wimmer
2020-05-08 12:20                                             ` btrfs reports bad key ordering after out of memory situation Christian Wimmer
2020-01-05 23:50                   ` 12 TB btrfs file system on virtual machine broke again Qu Wenruo
2020-01-06  1:32                     ` Christian Wimmer
2020-01-11  7:25                     ` Andrei Borzenkov
2021-10-15 21:01                     ` need help in a broken 2TB BTRFS partition Christian Wimmer
2021-10-16 10:08                       ` Qu Wenruo
2021-10-16 17:29                         ` Christian Wimmer
2021-10-16 22:55                           ` Qu Wenruo
2021-10-16 17:35                         ` Christian Wimmer
2021-10-16 23:27                           ` Qu Wenruo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=985d1845-d211-9134-4c9b-85a0956e7404@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=anand.jain@oracle.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=telefonchris@icloud.com \
    --cc=wqu@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.