On 18/02/2022 04:08, John-Mark Gurney wrote:
Andriy Gapon wrote this message on Tue, Feb 15, 2022 at 08:44 +0200:
On 15/02/2022 01:17, John-Mark Gurney wrote:
Andriy Gapon wrote this message on Mon, Feb 07, 2022 at 14:15 +0200:
I've got a problem where fsck behaves differently from my expectat
Andriy Gapon wrote this message on Tue, Feb 15, 2022 at 08:44 +0200:
> On 15/02/2022 01:17, John-Mark Gurney wrote:
> > Andriy Gapon wrote this message on Mon, Feb 07, 2022 at 14:15 +0200:
> >> I've got a problem where fsck behaves differently from my expectations.
> >> The problem happens with a f
On 15/02/2022 01:17, John-Mark Gurney wrote:
Andriy Gapon wrote this message on Mon, Feb 07, 2022 at 14:15 +0200:
I've got a problem where fsck behaves differently from my expectations.
The problem happens with a filesystem on a GELI encrypted ZVOL.
The volume has 4K block size and that's the GE
Andriy Gapon wrote this message on Mon, Feb 07, 2022 at 14:15 +0200:
> I've got a problem where fsck behaves differently from my expectations.
> The problem happens with a filesystem on a GELI encrypted ZVOL.
> The volume has 4K block size and that's the GELI's sector size as well.
> FreeBSD is sta
I've got a problem where fsck behaves differently from my expectations.
The problem happens with a filesystem on a GELI encrypted ZVOL.
The volume has 4K block size and that's the GELI's sector size as well.
FreeBSD is stable/13 from mid January.
Let me demonstrate:
# fsck -C -p /dev/zvol/.../
