On Sunday June 12 2011, Greg Freemyer wrote:
On Sun, Jun 12, 2011 at 7:23 PM, Randall R Schulz <rschulz@sonic.net> wrote:
On Sunday June 12 2011, Greg Freemyer wrote:
...
I'm a big fan of ext2 for /boot.
It is about as simple as it gets and everything out there can read it.
But the boot / root volume is on SSD and I want to exploit it _and_ preserve maximum lifetime (or whatever tradeoff I can decide is optimum between those to goals, to the extent they conflict).
I realize I'm confusing myself. The requirements for /boot are unrelated to it being on an SSD, since it's used so very little. Root, however, must be optimized for SSD. ... Whatever that turns out to mean. I'm still pretty short on those details.
I updated http://en.opensuse.org/SDB:SSD_discard_%28trim%29_support to talk about fstrim this afternoon. But I don't have any discussion of a good choice for /boot.
Why don't you research the FITRIM ioctl as well as wiper.sh (from the hdparm package). If either of them support ext2, I'd still go for the simplicity of ext2 for /boot.
The SSD I got is essentially a RAID 0 device, so none of the TRIM-based solutions are relevant (at least that's what I've read in several places, now). It's all on ITGC. I don't know if the "wiper" thing is useful for this device.
I believe both support ext4 and xfs at a minimum, but I don't know about ext2 or ext3 for either.
Also, it could be that the ext4 filesystem driver when using the ext2 or ext3 on disk format will support one or both. This actually sounds like a good question to take straight to the ext4 kernel mailinglist. (Subscription NOT needed to post to it.)
If you find out any new info, please add it to the above page, or ask me to.
OK. My research is ongoing.
Greg
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org