Date: Wed, 23 Sep 2020 19:07:54 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: Gleb Popov <6yearold@gmail.com> Cc: ports-committers <ports-committers@freebsd.org>, svn-ports-all <svn-ports-all@freebsd.org>, svn-ports-head <svn-ports-head@freebsd.org> Subject: Re: svn commit: r549723 - head/sysutils/e2fsprogs Message-ID: <71f2071d-8246-d6bb-ae47-4cd99a8d7248@FreeBSD.org> In-Reply-To: <CALH631mgVexqbvmJRZkyS8jg_k3Yh4sqxzk-Wr8eXs5zLakXDA@mail.gmail.com> References: <202009231244.08NCiHUQ090692@repo.freebsd.org> <CALH631mgVexqbvmJRZkyS8jg_k3Yh4sqxzk-Wr8eXs5zLakXDA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 23.09.20 um 18:52 schrieb Gleb Popov: > At $WORK I'm using "mountprog=/usr/local/bin/ntfs-3g" as an argument in > the /etc/fstab, so I didn't ever stumbled on the original problem. Can't > the same approach be used for e2fs? This way we don't need to put > anything above /usr/local Gleb, Unfortunatly not. Two important differences: - This is about fsck, not mount, and if you happen to have /usr on an ext2 because you're sharing storage with Linux, you've sawed off the very branch on which you were sitting. We don't have a mountprog=... equivalent for fsck anyways according to fstab(5)/mount(8) in FreeBSD 12.1. - FreeBSD has a native r/w capable ext2fs ext2/3/4 driver, which doesn't do journalling though, so we need to have fsck available. The kernel cannot possibly recover a dirty FS - that would require journalling. (We also have two fuse-based user-space implementations, one ships as FUSEFS option in e2fsprogs, but is slow, so its disabled by default, and sysutils/fusefs-ext2, https://github.com/alperakcan/fuse-ext2 which looks to be in early development and is mostly in Git, the last release from Git was two years ago.) Cheers, Matthias
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?71f2071d-8246-d6bb-ae47-4cd99a8d7248>