I'm going back and putting / in a partition of it's own. And will then try to add the other 3 disks to a btrfs.
So during install I don't see a way to add 3 disks to btrfs without first creating an LVM volume group. I see no way to run this command, btrfs device add dev1 dev2 /path/to/filesystem during install. On Fri, Dec 19, 2014 at 12:54 PM, Mark Post <[email protected]> wrote: > >>> On 12/19/2014 at 09:46 AM, Mark Pace <[email protected]> wrote: > > sles003:~> df -Ht > > df: option requires an argument -- 't' > > Try 'df --help' for more information. > > sles003:~> df -H > > Filesystem Size Used Avail Use% Mounted on > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% / > > devtmpfs 460M 8.2k 460M 1% /dev > > tmpfs 467M 0 467M 0% /dev/shm > > tmpfs 467M 7.4M 460M 2% /run > > tmpfs 467M 0 467M 0% /sys/fs/cgroup > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% /.snapshots > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% /var/tmp > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% /var/spool > > /dev/dasda1 204M 26M 168M 14% /boot/zipl > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% /var/opt > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% /var/lib/pgsql > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% /var/lib/mailman > > /dev/mapper/system-root 5.7G 2.5G 3.0G 46% /opt > -snip- > > OK, even though I got the switches wrong (should have been -hT) I can see > what you've done. First, I'll reiterate my long-standing "don't put / on > an LV" recommendation. Having the ability to boot from a read-only > snapshot might make that less important, but I don't know that to be true > yet. > > Since btrfs is new to everyone in an enterprise environment, I'm not sure > what you've done is of any real benefit. A btrfs file system can span > multiple physical (or virtual) volumes. So, you can do a > > btrfs device add dev1 dev2 /path/to/filesystem > > if extra space is needed. Having everything in one large btrfs on LVM > doesn't help with the problem of a runaway process (or user) filling up > everything, _unless_ you start using quotas. I suspect most people on this > mailing list haven't bothered doing that up until now, so this would be one > more new thing to deal with. > > It will be interesting to see what winds up working best for you and > anyone else trying things out. Thanks for helping me understand your setup. > > > Mark Post > > ---------------------------------------------------------------------- > For LINUX-390 subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO LINUX-390 or > visit > http://www.marist.edu/htbin/wlvindex?LINUX-390 > ---------------------------------------------------------------------- > For more information on Linux on System z, visit > http://wiki.linuxvm.org/ > -- The postings on this site are my own and don’t necessarily represent Mainline’s positions or opinions Mark D Pace Senior Systems Engineer Mainline Information Systems ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
