[opensuse-factory] filesystem mess with btrf
Hi, I created multiple volumes with the intention to keep all /var stuff in one volume /boot separate, etc. I did this on Opensuse 13.2 in the same way I did on 12.3 only using btrf. What I did not do is setting up subvolumes, but somehow OpenSuse did making my efforts to separate volumes unsuccessful. Can someone tell me which process creates the /boot/grub2/x86_64-efi, /boot/grub2/i386-pc, /var/log, ... subvolumes on the root filesystem ?? opensuse13:~ # df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% / devtmpfs 235M 8.0K 235M 1% /dev tmpfs 242M 88K 242M 1% /dev/shm tmpfs 242M 2.4M 240M 1% /run tmpfs 242M 0 242M 0% /sys/fs/cgroup /dev/mapper/system_13.2-usr_lv 18G 6.9G 10G 41% /usr /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /.snapshots /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /tmp /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /srv /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /usr/local /dev/sda2 486M 59M 398M 13% /boot /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /boot/grub2/x86_64-efi /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /boot/grub2/i386-pc /dev/mapper/export_vg-export_lv 20G 18G 2.9G 86% /export /dev/mapper/export_vg-src_lv 5.0G 2.6G 2.5G 51% /src /dev/mapper/system_13.2-opt_lv 6.0G 152M 5.3G 3% /opt /dev/mapper/system_13.2-var_lv 4.0G 254M 3.4G 7% /var /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/tmp /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/spool /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/opt /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/log /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/lib/pgsql /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/lib/mailman /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/lib/named /dev/mapper/system_13.2-root_lv 5.0G 1.5G 3.2G 32% /var/crash My fstab looks like: opensuse13:~ # cat /etc/fstab UUID=d300b5ad-372b-4f86-b952-4aa4fc62a84e swap swap defaults 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f / btrfs defaults 0 0 UUID=fd14684f-1950-4f33-95b5-b54f069b4fe0 /boot ext4 acl,user_xattr 1 2 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /boot/grub2/i386-pc btrfs subvol=boot/grub2/i386-pc 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /boot/grub2/x86_64-efi btrfs subvol=boot/grub2/x86_64-efi 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /home btrfs subvol=home 0 0 UUID=f535177b-18a5-443c-8236-96105d58a621 /opt btrfs defaults 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /srv btrfs subvol=srv 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /tmp btrfs subvol=tmp 0 0 UUID=62ffc2f3-7e3a-433e-8a4e-5a89a352f8cf /usr btrfs defaults 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /usr/local btrfs subvol=usr/local 0 0 UUID=323ba68a-e7ed-4f0f-9716-dcad92bb9808 /var btrfs defaults 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/crash btrfs subvol=var/crash 0 0 #UUID=323ba68a-e7ed-4f0f-9716-dcad92bb9808 /var/crash btrfs subvol=var/crash 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/lib/mailman btrfs subvol=var/lib/mailman 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/lib/named btrfs subvol=var/lib/named 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/lib/pgsql btrfs subvol=var/lib/pgsql 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/log btrfs subvol=var/log 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/opt btrfs subvol=var/opt 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/spool btrfs subvol=var/spool 0 0 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /var/tmp btrfs subvol=var/tmp 0 0 /dev/export_vg/export_lv /export xfs defaults 1 2 /dev/export_vg/src_lv /src xfs defaults 1 2 UUID=7a681ad4-5b82-4e78-9b20-1d719c89fe6f /.snapshots btrfs subvol=.snapshots 0 0 Thank you Markus
On Sat, Feb 07, 2015 at 03:32:18PM -0000, Markus Moeller wrote:
Hi,
I created multiple volumes with the intention to keep all /var stuff in one volume /boot separate, etc. I did this on Opensuse 13.2 in the same way I did on 12.3 only using btrf. What I did not do is setting up subvolumes, but somehow OpenSuse did making my efforts to separate volumes unsuccessful. Can someone tell me which process creates the /boot/grub2/x86_64-efi, /boot/grub2/i386-pc, /var/log, ... subvolumes on the root filesystem ??
YaST creates those subvolumes. They are needed for rollbacks.
Regards,
Arvin
--
Arvin Schnell,
Hi,
Gesendet: 08.02.2015 um 17:16 Uhr; Von: "Arvin Schnell"
YaST creates those subvolumes. They are needed for rollbacks.
I've done a new installation with ext4 - due to the fact that the filesystem fills to 100% after only some weeks and the system hangs. This was also the same for 1 or 2 years, I tested the filesystem. (SSD Space was 64GB without /home which is mounted via NFS). Especially this behavior was forced by the default settings - which creates a snapshot after each 'zypper up' on my Tumbleweed with many changes. Regards Ulf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Arvin, Ok, but how can I create them on the right filesystem ( e.g. not the root filesystem) . It does not make any sense to me if I create a /var filesystem that /var/log is created under root and not under /var. Do I miss something ? Thank you Markus "Arvin Schnell" wrote in message news:20150208161631.GA5472@suse.de... On Sat, Feb 07, 2015 at 03:32:18PM -0000, Markus Moeller wrote:
Hi,
I created multiple volumes with the intention to keep all /var stuff in one volume /boot separate, etc. I did this on Opensuse 13.2 in the same way I did on 12.3 only using btrf. What I did not do is setting up subvolumes, but somehow OpenSuse did making my efforts to separate volumes unsuccessful. Can someone tell me which process creates the /boot/grub2/x86_64-efi, /boot/grub2/i386-pc, /var/log, ... subvolumes on the root filesystem ??
YaST creates those subvolumes. They are needed for rollbacks.
Regards,
Arvin
--
Arvin Schnell,
participants (3)
-
Arvin Schnell
-
Markus Moeller
-
ulfbart@gmx.net