severity 1072566 minor
thanks
On Thu, Jun 06, 2024 at 12:19:39PM +0200, Fabio Fantoni wrote:
> You wrote about metadata_csum but the issue is not with it, included
> also in the root filesystem that don't have issue with backup but with
> metadata_csum_seed that is different and newer, anyway seems supported
> by grub in backports as supported from 2.11
Yes, sorry, that was a typo on my part. In my reply to you, it should
have read metadata_csum_seed, not metadata_csum (which as you noted is
a much older file system feature).
Could you clarify about why storage file systems created using open
media vault 7 are causing problems for you? These aren't used for
booting, so grub compatibility should matter, right? And Open Media
Vault is a Network Attached Storage solution, so why should it matter
whether or not the metadata_csum_seed or orphan_file features are
enabled on its own internal storage volumes?
> Now that I know I'll use a workaround on any omv 7 server changing
> /etc/mke2fs.conf before create storage filesystem and so I won't have
> problems but I created this bug because other users might have similar
> problems.
Sure, but important is a vastly inflated priority. It's quite
specific to your particular use case, and arguably, the bug is in omv,
since if it is causing problems, omv shouldn't have pulled in
e2fsprogs from bullseye-backports, or it could have edited the
/etc/mke2fs.conf file itself. But I'm guessing perhaps that it's not
even generally applicable problem for more omv users, but is one
specific to your unique use case? At least, as a guess, since in
general the exact file system used by a NAS Really Doesn't Matter.
Heck, my home NAS system is a Synology box, and which happens to use
btrfs, and it really doesn't matter that it's not using ext4, or xfs,
or any other file system instead. It's certainly not user-visible!
- Ted
