[ Sorry for not getting back to your earlier ]
Theodore Ts'o wrote...
> What could have happened on your file system? Well, there are two
> scenarios that could explain what had happened:
After some more desastrous experiences (kernel stack traces and
segfaults) I assume serious hardware
On Wed, Jan 27, 2021 at 01:10:33AM +0100, Christoph Biedl wrote:
>
> Yes, and my question here: Is it possible the existence of that bogus
> fscrypt feature flag made e2fsck or the kernel think this is an ext4,
> and things went downhill from there? That's a situation I'd like to
> avoid - since
Theodore Ts'o wrote...
> On Tue, Jan 26, 2021 at 12:10:20AM +0100, Christoph Biedl wrote:
> > EXT4-fs (sdf3): mounted filesystem without journal. Opts: (null)
> >
> > Expected:
> >
> > EXT4-fs (sdf3): mounting ext2 file system using the ext4 subsystem
>
> That's just a matter of how it
On Tue, Jan 26, 2021 at 12:10:20AM +0100, Christoph Biedl wrote:
> Package: e2fsprogs
> Version: 1.44.5-1+deb10u3
> Severity: normal
>
> Dear Maintainer,
>
> at first, I am sorry to tell I cannot provide the raw data. I was quite
> in a hurry and overwrote it before realizing its high value for
Package: e2fsprogs
Version: 1.44.5-1+deb10u3
Severity: normal
Dear Maintainer,
at first, I am sorry to tell I cannot provide the raw data. I was quite
in a hurry and overwrote it before realizing its high value for
debugging.
Story: An ext2 file system, actually a boot partition, suffered
5 matches
Mail list logo
