We may encounter both checkpoints invalid in such a case:
1. write checkpoint A, B, C;
2. sudden power-cut during write checkpoint D;
3. fsck changes the total block count of checkpoint C;
4. sudden power-cut during fsck write checkpoint C in place
- -
| ver C |
On 2018/7/27 4:54, Weichao Guo wrote:
> We may encounter both checkpoints invalid in such a case:
> 1. write checkpoint A, B, C;
> 2. sudden power-cut during write checkpoint D;
> 3. fsck changes the total block count of checkpoint C;
> 4. sudden power-cut during fsck write checkpoint C in place
>
Hi Weichao,
This is corrupting the checkpoint showing dangling nids when running my test
where injects faults with shutdown loop.
Thanks,
On 07/28, Chao Yu wrote:
> On 2018/7/27 4:54, Weichao Guo wrote:
> > We may encounter both checkpoints invalid in such a case:
> > 1. write checkpoint A, B, C
Hi Jaegeuk,
Is your test using a kernel include some unstable patches like "f2fs: guarantee
journalled quota data by checkpoint"?
I am planing to reproduce the problem with dev branch. Is that OK? Any hints
for reproducing?
Thank,
Weichao
On 2018/8/18 2:32, Jaegeuk Kim wrote:
> Hi Weichao,
>
On 08/20, guoweichao wrote:
> Hi Jaegeuk,
>
> Is your test using a kernel include some unstable patches like "f2fs:
> guarantee journalled quota data by checkpoint"?
> I am planing to reproduce the problem with dev branch. Is that OK? Any hints
> for reproducing?
I actually removed such the pat
