Re: What is backup_vg-backup? Can it be so big?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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:

What gui?  Right-clicking on what?

  Link to block device (inode/blockdevice)

Yes, it's a block device.

	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.

An inode is the chunk of metadata in the filesystem that describes a file. You could think of it simply as a directory entry, but it's more complicated than that. A block device is storage that accesses data in chunks. For example, hard drives can only access data in chunks of 512 bytes. You can't directly access a specific byte.

	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?

It's not a file. It appears to be an lvm volume, kind of like a partition. It's mounted at /.snapshot, so what does "ls -a /.snapshot" show you?

	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.

That's completely up to you and what you want to use it for.


To figure out what's going on with that storage, run the following four commands and copy their output:
vgs
lvs
fdisk -l
lsblk -t
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux