On Tue, Jan 12, 2016 at 4:23 PM, Andrew Price wrote:
> On 12/01/16 13:30, Andreas Gruenbacher wrote:
>>
>> Is it guaranteed that the kernel will never set the new rg_skip field
>> if it hasn't verified that the next resource group is where it thinks
>> it is?
>
>
> No, but
On Tue, Jan 12, 2016 at 2:12 PM, Andrew Price wrote:
> On 12/01/16 12:39, Andreas Gruenbacher wrote:
>>
>> On Tue, Jan 12, 2016 at 12:39 PM, Andrew Price wrote:
>>>
>>> Add a new rg_skip field to struct gfs2_rgrp, replacing __pad. The
>>> rg_skip field has
Add a new rg_skip field to struct gfs2_rgrp, replacing __pad. The
rg_skip field has the following meaning:
- If rg_skip is zero, it is considered unset and not useful.
- If rg_skip is non-zero, its value will be the number of blocks between
this rgrp's address and the next rgrp's address. This
Hi,
On 12/01/16 11:39, Andrew Price wrote:
Add a new rg_skip field to struct gfs2_rgrp, replacing __pad. The
rg_skip field has the following meaning:
- If rg_skip is zero, it is considered unset and not useful.
- If rg_skip is non-zero, its value will be the number of blocks between
this
On Tue, Jan 12, 2016 at 12:39 PM, Andrew Price wrote:
> Add a new rg_skip field to struct gfs2_rgrp, replacing __pad. The
> rg_skip field has the following meaning:
>
> - If rg_skip is zero, it is considered unset and not useful.
> - If rg_skip is non-zero, its value will be
On 12/01/16 12:39, Andreas Gruenbacher wrote:
On Tue, Jan 12, 2016 at 12:39 PM, Andrew Price wrote:
Add a new rg_skip field to struct gfs2_rgrp, replacing __pad. The
rg_skip field has the following meaning:
- If rg_skip is zero, it is considered unset and not useful.
- If
On 12/01/16 13:30, Andreas Gruenbacher wrote:
Is it guaranteed that the kernel will never set the new rg_skip field
if it hasn't verified that the next resource group is where it thinks
it is?
No, but rg_skip is set from the ri_addr of the next resource group in
the rindex and gfs2 generally