On Fri, Dec 27, 2019 at 04:44:46PM +0100, Stefan Sperling wrote:
On Fri, Dec 27, 2019 at 03:56:00PM +0100, Thomas de Grivel wrote:
Hello,
I have a few ext3 drives from an old gentoo which mount fine but do
not fsck (something about the first alternate superblock not matching
values) they mount and fsck fine under linux.
OpenBSD ext3 support is limited and read-only. I wouldn't expect fsck
to work since fixing errors requires writing to the filesystem.
In my experience, ext3 support is fragile, but not limited to read-only
access. Had to save some big files on a 10-year old HDD that I used
with Gentoo, and it worked mostly fine. Except for a panic, reported
at https://marc.info/?l=openbsd-bugs&m=157634364811892.
Also, fixing an ext3 filesystem in OpenBSD is handled by the Linux
fsck utilities compiled for OpenBSD as the "e2fsprogs" package. This
worked beautifully for me after the crash. As far as I can tell, this
need not be correlated to the ext2 support in the kernel.
