On Mon, Dec 03, 2018 at 08:24:07AM -0000, Tor Stenvaag wrote:
> The maint branch indeed fixed the problem. Output attached. Thanks for
> your effort.
>
> (There is still a "warning" about "extent tree (at level 1) could be
> narrower. Fix<y>? yes" when running e2fsck after resize. When selecting
> yes and running the e2fsck once more the warning is still present.)
Ah... that's interesting. So to be clear, if you run:
e2fsck -fy /dev/skole-vg/root
twice, the second time, you will still see:
Inode 8 extent tree (at level 1) could be narrower. Fix<y>? yes
On Mon, Dec 03, 2018 at 08:24:07AM -0000, Tor Stenvaag wrote:
> The maint branch indeed fixed the problem. Output attached. Thanks for
> your effort.
>
> (There is still a "warning" about "extent tree (at level 1) could be
> narrower. Fix<y>? yes" when running e2fsck after resize. When selecting
> yes and running the e2fsck once more the warning is still present.)
Ah... that's interesting. So to be clear, if you run:
e2fsck -fy /dev/skole-vg/root
twice, the second time, you will still see:
Inode 8 extent tree (at level 1) could be narrower. Fix<y>? yes
... on the second run. Is that correct?
Hmmm..... can you send me the output of:
debugfs -R "extents <8>" /dev/skole-vg/root
Many thanks!!
- Ted