On Sat, Mar 31, 2018 at 04:34:58PM -0600, Chris Murphy wrote:
> On Sat, Mar 31, 2018 at 12:57 AM, Goffredo Baroncelli
> wrote:
> > On 03/31/2018 07:03 AM, Zygo Blaxell wrote:
> btrfs has no optimization like mdadm write-intent bitmaps; recovery
> is always a full-device operation. In th
On Mon, Nov 20, 2017 at 11:10 PM, Qu Wenruo wrote:
>
>
> On 2017年11月21日 13:58, Chris Murphy wrote:
>> On Mon, Nov 20, 2017 at 9:58 PM, Qu Wenruo wrote:
>>>
>>>
>>> On 2017年11月21日 12:49, Chris Murphy wrote:
On Mon, Nov 20, 2017 at 9:43 PM, Qu Wenruo wrote:
>
>
>>
>> Apply in
On Sat, Mar 31, 2018 at 4:40 PM, Adam Borowski wrote:
> On Sat, Mar 31, 2018 at 03:50:03PM -0600, Chris Murphy wrote:
>> This is perhaps a novelty problem report. And it's also a throw away
>> card data wise, and is a $12 Samsung EVO+ SDXC card used in an Intel
>> NUC.
>>
>> It contains FAT, ext4,
On Sat, Mar 31, 2018 at 12:57 AM, Goffredo Baroncelli
wrote:
> On 03/31/2018 07:03 AM, Zygo Blaxell wrote:
btrfs has no optimization like mdadm write-intent bitmaps; recovery
is always a full-device operation. In theory btrfs could track
modifications at the chunk level but this is
On Sat, Mar 31, 2018 at 3:50 PM, Chris Murphy wrote:
> This is perhaps a novelty problem report. And it's also a throw away
> card data wise, and is a $12 Samsung EVO+ SDXC card used in an Intel
> NUC.
>
> Kernel is 4.15.14-300.fc27.x86_64
>
> It contains FAT, ext4, and Btrfs file systems. They ca
This is perhaps a novelty problem report. And it's also a throw away
card data wise, and is a $12 Samsung EVO+ SDXC card used in an Intel
NUC.
Kernel is 4.15.14-300.fc27.x86_64
It contains FAT, ext4, and Btrfs file systems. They can all be fsck'd,
but none can be mounted. Even if it use blockdev
On Sat, Mar 31, 2018 at 11:36:50AM +0300, Andrei Borzenkov wrote:
> 31.03.2018 11:16, Goffredo Baroncelli пишет:
> > On 03/31/2018 09:43 AM, Zygo Blaxell wrote:
> >>> The key is that if a data write is interrupted, all the transaction
> >>> is interrupted and aborted. And due to the COW nature of b
On 03/31/2018 09:43 AM, Zygo Blaxell wrote:
>> The key is that if a data write is interrupted, all the transaction
>> is interrupted and aborted. And due to the COW nature of btrfs, the
>> "old state" is restored at the next reboot.
> This is not presently true with raid56 and btrfs. RAID56 on bt
On Sat, Mar 31, 2018 at 08:57:18AM +0200, Goffredo Baroncelli wrote:
> On 03/31/2018 07:03 AM, Zygo Blaxell wrote:
> >>> btrfs has no optimization like mdadm write-intent bitmaps; recovery
> >>> is always a full-device operation. In theory btrfs could track
> >>> modifications at the chunk level b
