On 03/23/2016 07:24 PM, Chris Murphy wrote:
LVM is not relevant at all in this case because even with LVM, XFS being used for /home still means it can't be resized, and therefore a tear down would still be required.
I disagree. This is why. Suppose I have /home as XFS in a 20G partition (aka LV) and 'df' tells me I'm only using 10G of that. So I create a new LV, Say I make it 15G. Now I have a few options. If I want to keep using XFS I can mkfs.xfs that LV, rsync the contents of /home across, rename the "HOME" LV to "oldHOME" and rename the new LV to "HOME". Of course in my infinite wisdom and foresight (gained by getting it wrong in the past) I choose to have the entries in /etc/fstab mount by name rather than mount by UUID :-) Another option is to mkfs.reiserfs since ReiserFS can, in the future, be both shrunk and grown, while mounted, without shutting the system down. I'm rather enamoured of that option :-) I have tried NilFS2, which can be shrunk or grown. If you are using a SSD you might look at this. It worked OK when I tied it, and it works for mounted (aka live) file systems, but I don't see a compelling reason to use it on spinning rust other than its continuous snapshotting. That *might* be relevant for /home/ for users who make a lot of mistakes and need to retrieve previous iterations of files. Then, of course, there's ext4FS. This can be resized with resize2fs, and it can both grow and shrink the size of the file system. The downside is that this has to be done off-line, that is with the FS unmounted. (So far as I can tell. If I'm wrong, please correct me and give details.) My conclusion with all this is that XFS is not an auspicious chose if you have the least uncertainty about provisioning. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org