On 2018年07月13日 15:24, Anand Jain wrote:
>
>
> On 07/13/2018 01:39 PM, Qu Wenruo wrote:
>>
>>
>> On 2018年07月13日 13:32, Anand Jain wrote:
>>>
>>>
>>>
>>>
>>>
> But if you are planning to
> record and start at transaction [14] then its an overkill because
> transaction [19 and
On 07/13/2018 01:39 PM, Qu Wenruo wrote:
On 2018年07月13日 13:32, Anand Jain wrote:
But if you are planning to
record and start at transaction [14] then its an overkill because
transaction [19 and [20] are already in the disk.
Yes, I'm doing it overkilled.
Ah. Ok.
But it'
On 2018年07月13日 13:32, Anand Jain wrote:
>
>
>
>
>
>>> But if you are planning to
>>> record and start at transaction [14] then its an overkill because
>>> transaction [19 and [20] are already in the disk.
>>
>> Yes, I'm doing it overkilled.
>
> Ah. Ok.
>
>> But it's already much bet
But if you are planning to
record and start at transaction [14] then its an overkill because
transaction [19 and [20] are already in the disk.
Yes, I'm doing it overkilled.
Ah. Ok.
But it's already much better than scrub all block groups (my original plan).
That's true. Whic
On 2018年07月13日 08:20, Qu Wenruo wrote:
>
>
> [snip]
>>> In this case, it depends on when and how we mark the device resilvering.
>>> If we record the generation of write error happens, then just initial a
>>> scrub for generation greater than that generation.
>>
>> If we record all the degrade
[snip]
>> In this case, it depends on when and how we mark the device resilvering.
>> If we record the generation of write error happens, then just initial a
>> scrub for generation greater than that generation.
>
> If we record all the degraded transactions then yes. Not just the last
> faile
On 07/12/2018 08:59 PM, Qu Wenruo wrote:
On 2018年07月12日 20:33, Anand Jain wrote:
On 07/12/2018 01:43 PM, Qu Wenruo wrote:
On 2018年07月11日 15:50, Anand Jain wrote:
BTRFS Volume operations, Device Lists and Locks all in one page:
Devices are managed in two contexts, the scan context a
On 2018年07月12日 20:33, Anand Jain wrote:
>
>
> On 07/12/2018 01:43 PM, Qu Wenruo wrote:
>>
>>
>> On 2018年07月11日 15:50, Anand Jain wrote:
>>>
>>>
>>> BTRFS Volume operations, Device Lists and Locks all in one page:
>>>
>>> Devices are managed in two contexts, the scan context and the mounted
>>>
On 07/12/2018 01:43 PM, Qu Wenruo wrote:
On 2018年07月11日 15:50, Anand Jain wrote:
BTRFS Volume operations, Device Lists and Locks all in one page:
Devices are managed in two contexts, the scan context and the mounted
context. In scan context the threads originate from the btrfs_control
io
On 2018年07月11日 15:50, Anand Jain wrote:
>
>
> BTRFS Volume operations, Device Lists and Locks all in one page:
>
> Devices are managed in two contexts, the scan context and the mounted
> context. In scan context the threads originate from the btrfs_control
> ioctl and in the mounted context th
BTRFS Volume operations, Device Lists and Locks all in one page:
Devices are managed in two contexts, the scan context and the mounted
context. In scan context the threads originate from the btrfs_control
ioctl and in the mounted context the threads originates from the mount
point ioctl.
Ap
11 matches
Mail list logo
