3 ms·
> when a file is striped across different physical disks with possibly different characteristics, how would you defrag it without knowing the read access patter
by Dylan16807 4y ago
> when a file is striped across different physical disks with possibly different characteristics, how would you defrag it without knowing the read access pattern?
Looking at a single disk at a time, do your best to make sure all chunks of the same file are in order and adjacent.
You could be smarter than that, but just that would do fine.
The problem is that ZFS basically can't move things.
- ender341341 4y ago> The problem is that ZFS basically can't move things. The one killer feature for me with btrfs is offline deduping (and by extension not having de-duping require a super computer to run). My data has enough duplication that it'd be nice to have, but not worth requiring hundreds of gigs of ram. Being able to fire off a job after importing a large set of data (or maybe yearly-ish) would be awesome and give me a few extra years without having to update my hardware.
- vkaku 4y agoThat doesn't account for physical disk characteristics at all. You could have disks from different generations all be part of a pool, CMR vs SMR(!) (needs zone resets and large chunk writes), disks could degrade etc. Plus, when you update a file, you literally create new links and update the file out of place (true for any COW FS). So the read won't be sequential if you want to access two versions at the same time. In that case you want to know if you optimize for hardware failure as opposed to for performance. This could be fixed for specific usecases but not all block patterns in general. Just why I posted this.