Comment 6 for bug 1479546

> I went initially with block because I do want to control the filesystem type (ext3/4 vs. xfs, perhaps), as well as various mount options, like noatime. It all adds a little bit of complexity, but goes far in helping do benchmarking and performance-tuning. Are these something "type: filesystem" can do?

Not at the moment. All you get with "type: filesystem" is ext4. Juju will make sure it's formatted and mounted before installing, and will ensure the mount is maintained whenever the agent restarts. Control over filesystems and mount options was originally in the plan, but was removed due to complexity around required vs. preferred options. If you find yourself repeating this work a lot, it may be worth us reconsidering that position.

Adding an fstab entry would be fine. Just be careful about persistent naming; block device names can change across machine reboots. I suggest using the filesystem UUID.