On Sun, 07 Jun 2020 14:07:29 -0700, Samuel Sieb wrote:
> On 6/7/20 10:42 AM, I Beartooth wrote:
>> Going into the GUI, right clicking and choosing priorities, I see:
>
> What gui? Right-clicking on what?
Sorry. Mate. I clicked on the desktop icon for Computer, then
Filesystem, dev, mapper; that displayed backup_vg-backup among others; I
right-clicked on it.
>> Link to block device (inode/blockdevice)
>
> Yes, it's a block device.
[....]
> 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.
OK, I think I follow that. Thanks!
>> 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?
Now it gets weird. I tried that command both as user and as root,
and got only
ls: cannot access '/.snapshot': No such file or directory
>> 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.
IOW, it's a reasonable thing to do, given that old evils like
dependency hell are pretty well gone. Good. All hail the developers!
For most of my time, there has been no question whether I would
snarl up a machine, but only when. So every time I bought a new one, I
kept the old one and the one before it, in order to be able to holler for
help.
> To figure out what's going on with that storage, run the following four
> commands and copy their output:
> vgs
# vgs
VG #PV #LV #SN Attr VSize VFree
backup_vg 1 1 0 wz--n- <1.82t 0
fedora 1 3 0 wz--n- <110.79g 0
lvs
# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log
Cpy%Sync Convert
backup backup_vg -wi-ao----
<1.82t
home fedora -wi-ao----
52.92g
root fedora -wi-ao----
50.00g
swap fedora -wi-ao---- 7.86g
fdisk -l
# fdisk -l
Disk /dev/sda: 111.81 GiB, 120034123776 bytes, 234441648 sectors
Disk model: Samsung SSD 850
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x57db626c
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 2099199 2097152 1G 83 Linux
/dev/sda2 2099200 234440703 232341504 110.8G 8e Linux LVM
Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: WDC WD20EZRZ-00Z
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 772CAD71-6AAB-4868-9D69-C46B183C9581
Device Start End Sectors Size Type
/dev/sdb1 2048 251903 249856 122M Microsoft reserved
/dev/sdb2 251904 3907026943 3906775040 1.8T Linux filesystem
Disk /dev/mapper/fedora-root: 50 GiB, 53687091200 bytes, 104857600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/fedora-swap: 7.88 GiB, 8443133952 bytes, 16490496 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/fedora-home: 52.94 GiB, 56824430592 bytes, 110985216
sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mapper/backup_vg-backup: 1.84 TiB, 2000267771904 bytes,
3906772992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
lsblk -t
NAME ALIGNMENT MIN-IO OPT-IO PHY-SEC LOG-SEC ROTA SCHED
RQ-SIZE RA WSAME
sda 0 512 0 512 512 0
bfq 64 128 0B
├─sda1 0 512 0 512 512 0
bfq 64 128 0B
└─sda2 0 512 0 512 512 0
bfq 64 128 0B
├─fedora-root 0 512 0 512 512
0 128 128 0B
├─fedora-swap 0 512 0 512 512
0 128 128 0B
└─fedora-home 0 512 0 512 512
0 128 128 0B
sdb 0 4096 0 4096 512 1
bfq 64 128 0B
├─sdb1 0 4096 0 4096 512 1
bfq 64 128 0B
└─sdb2 0 4096 0 4096 512 1
bfq 64 128 0B
└─backup_vg-backup 0 4096 0 4096 512
1 128 128 0B
sr0 0 512 0 512 512 1
bfq 64 128 0B
--
Beartooth Staffwright, Not Quite Clueless Linux Power User
I have precious (very precious) little idea where up is.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
