You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MacBook-Pro:~ user$ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 250.7 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.7 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 198.4 GB disk1s1
2: APFS Volume Preboot 45.8 MB disk1s2
3: APFS Volume Recovery 522.7 MB disk1s3
4: APFS Volume VM 4.3 GB disk1s4
/dev/disk2 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: FDisk_partition_scheme *250.1 GB disk2
1: Windows_NTFS ssd-t5 250.1 GB disk2s1
Am I the one who's doing it the wrong way? I would simply like to recover the I/O for each of the disks and inside each disk to have the list of partitions with the disk_usage of each mountpoint. Store it all in a dictionary. But the above concern blocks me in this process...
Best regards
The text was updated successfully, but these errors were encountered:
Platform
In addition, I have:
===
Bug description
When I retrieve the partitions (
psutil.disk_partitions(all=False)
), I get the following:And when I want to calculate the I/O for each of the disks (
psutil.disk_io_counters(perdisk=True)
), here is the result:What I don't understand is that the I/Os give me the
disk0
and thedisk2
, but what is the link with the partitions/dev/disk1s1
and/dev/disk1s4
????It seems that it returns the result returned by the df -H command:
No disk0 appears so far!
Except if I run
diskutil list
:Am I the one who's doing it the wrong way? I would simply like to recover the I/O for each of the disks and inside each disk to have the list of partitions with the disk_usage of each mountpoint. Store it all in a dictionary. But the above concern blocks me in this process...
Best regards
The text was updated successfully, but these errors were encountered: