On 2019/1/7 上午1:57, Giuseppe Della Bianca wrote: > In data domenica 6 gennaio 2019 15:12:38 CET, Qu Wenruo ha scritto: > ]zac[ >> Do you have a full history of the kernel versions? > > I believe from version 4.13.9 to 4.17.7 . > Today I updated everything to fedora 29, kernel 4.19.10 . > >> I'm not sure when the corruption happened. >> It's completely possible that some old kernel caused the corruption but >> not exposed until now. > > I am quite convinced that it happens during the snapshot delete and the > subsequent cleanup. > And maybe even the umount is part of the problem.
No, I mean the corruption which finally results the hang was there for a long time. It's relatively common that extent tree get corrupted before and some unfortunately operation touching the corrupted extent tree triggered some user affecting error. > >> Also, would you please run "btrfs check --readonly" on the fs? >> It should show all corruption. >> >> And if "btrfs check" shows no corruption, then it's completely a bug in >> that given kernel (and even current kernel). > > btrfs check reported various corruptions and fixed them. Please paste the output if possible. Thanks, Qu > A this time it seems that the filesystem works fine (it's the first time it > does not have to be redone from scratch). > >> Thanks, >> Qu > > No, thanks to you for your work. > > Gdb > >
signature.asc
Description: OpenPGP digital signature
