-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/02/15 12:00, jdd wrote:
Le 09/02/2015 12:07, Bernhard Voelker a écrit :
$ df -h --out .
this gave all zeros, so I noted the /tmp is on btrfs (13.2 default).
so
# btrfs fi df / Data, single: total=38.24GiB, used=17.91GiB System, single: total=4.00MiB, used=16.00KiB Metadata, single: total=1.76GiB, used=1.31GiB GlobalReserve, single: total=432.00MiB, used=80.00KiB
# btrfs fi usage / Overall: Device size: 40.00GiB Device allocated: 40.00GiB Device unallocated: 0.00B Used: 19.22GiB Free (estimated): 20.33GiB (min: 20.33GiB) Data ratio: 1.00 Metadata ratio: 1.00 Global reserve: 432.00MiB (used: 320.00KiB)
Data,single: Size:38.24GiB, Used:17.91GiB /dev/sdb1 38.24GiB
Metadata,single: Size:1.76GiB, Used:1.31GiB /dev/sdb1 1.76GiB
System,single: Size:4.00MiB, Used:16.00KiB /dev/sdb1 4.00MiB
Unallocated: /dev/sdb1 0.00B
but of course after /tmp was cleaned
I'm a bit short of undertanding :-(
thanks jdd
Take a look at Yast2 > Miscellaneous > Snapper. I suspect snapper is creating btrfs snapshots of your / every time you patch/update anything. This seems to the default behaviour of the openSUSE btrfs. Once you've tamed this behaviour, btrfs is quite well behaved. I've been using it for about 6 months here. Bob - -- Bob Williams System: Linux 3.16.7-7-desktop Distro: openSUSE 13.2 (x86_64) with KDE Development Platform: 4.14.3 Uptime: 06:00am up 7:55, 3 users, load average: 0.16, 0.05, 0.06 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTY3k8ACgkQ0Sr7eZJrmU5ydQCeKOWzdgwP46cy+kT9dkydy9xh 4pYAoI8+eFj8upmvUkSZfMw9RGaH0zpX =CqTR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org