On 6/7/20 10:42 AM, Beartooth wrote:
On a System76 PC several years old, running F32 fully updated (not Ubuntu), I see the following: $ df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 7.8G 0 7.8G 0% /dev tmpfs 7.8G 0 7.8G 0% /dev/shm tmpfs 7.8G 1.6M 7.8G 1% /run /dev/mapper/fedora-root 49G 16G 31G 35% / tmpfs 7.8G 60K 7.8G 1% /tmp /dev/mapper/fedora-home 52G 20G 30G 40% /home /dev/sda1 976M 252M 658M 28% /boot /dev/mapper/backup_vg-backup 1.8T 174M 1.7T 1% /.snapshots tmpfs 1.6G 60K 1.6G 1% /run/user/65536 bash-5.0$ Going into the GUI, right clicking and choosing priorities, I see: Link to block device (inode/blockdevice) So I searched inode, but got over my head in no time. Searching snapshot was a little more comprehensible, but using what I think it told me would demand knowledge I lack. I also tried blockdevice, and that *really* got me into a jungle of jargon. I'm wondering whether *any* file on an old machine could be so big as a terabyte, let alone two. If not, what if anything is df -h telling me about this machine as compared to my others? Anything about speed or storage?
The file is probably sparse, i.e. it is only as large as the usage which, at the moment, is 174M. Enough snapshots and it could eventually grow to a max of 1.8T.
I also have a still broader question. Instead of keeping each machine, as heretofore, as nearly in sync with the others, actually as close a copy of the others, might it be reasonably safe to keep one for constant use and the others as supporting specialists of some sort. Advice? Comments?
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
