Skip to main content
6 events
when toggle format what by license comment
5 hours ago comment added Joshua I was wondering how on earth a filesytem ended up with that structure that bytes per inode was a fixed quantity once formatting, so I pulled up the ext4 header. It should be possible to construct an ext4 filesystem consisting of one group that doesn't have this problem anymore; however that is another version of erase the disk.
8 hours ago comment added cas ZFS also supports transparent compression (with compression=on|off|gzip|gzip-N|lz4|lzjb|zle|zstd|zstd-N|zstd-fast|zstd-fast-N. see man zfsprops) which serves the OP's goal of "I only need more filesystem size" if the data being stored is compressible.
10 hours ago history edited Stephen Kitt CC BY-SA 4.0
Clarify that this is only Ext4.
10 hours ago comment added Marcus Müller and on OpenWRT (I only mention this because 46 TB might sound a bit like a network-attached appliance) I have no clue. ZFS might be a good choice here, assuming you want to make use of its built-in multi-volume / mirroring abilities while also making use of in-filesystem checksums (zRAID). If not (i.e., you are happy with your current mapper, probably LVM), and if you don't need to be able to shrink filesystems later on, XFS simply works and is (in my experience) quite fast.
10 hours ago comment added Marcus Müller Note that if unpredictable (or very low) number of "average bytes used by files per inode" is a problem here, the reader might want to consider different file systems than the ext family offers – a fixed byters-per-inode ratio is not necessary; at least XFS and Btrfs and ZFS have dynamic inode allocations. Considering the asker's resize2fs version and assuming they are on "mainstream" Linux distributions that are still in support today, they're probably using debian 12, Ubuntu 24.04LTS or openWRT 23.x or 24.x; on ubuntu, ZFS support is first-hand, on debian it's relatively commonly used,
15 hours ago history answered Stephen Kitt CC BY-SA 4.0