#mountpoint — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #mountpoint, aggregated by home.social.
-
How can i clear space from 9.4 GB /var/tmp older which is now 100% #diskusage #mountpoint
-
Now this is an interesting #Python problem. I don't know if it's a #bug, but it's a change in behaviour that I don't see documented.
I upgraded from #Debian 12/Bookworm to 13/Trixie, so the default Python3 changed from 3.11 to 3.13. A script of mine broke, because `pathlib.Path.is_mount()` changed behaviour when the path is a symlink (at least to a directory).
i.e. I'm testing a path that is a symlink. The symlink points to a directory. That directory *is* a mountpoint. The `.is_mount()` test in 3.11 returned True, while in 3.13 it returns False.
This seems wrong to me. Most path-manipulation functions transparently treat symlinks as if they were the pointed-to object unless you pass an option/flag specifically to say you want the symlink itself.
Gonna have to dig to see what else I can find.
#pathlib #path #is_mount #stdlib #behaviour #symlink #filesystem #mountpoint #mount
-
Now this is an interesting #Python problem. I don't know if it's a #bug, but it's a change in behaviour that I don't see documented.
I upgraded from #Debian 12/Bookworm to 13/Trixie, so the default Python3 changed from 3.11 to 3.13. A script of mine broke, because `pathlib.Path.is_mount()` changed behaviour when the path is a symlink (at least to a directory).
i.e. I'm testing a path that is a symlink. The symlink points to a directory. That directory *is* a mountpoint. The `.is_mount()` test in 3.11 returned True, while in 3.13 it returns False.
This seems wrong to me. Most path-manipulation functions transparently treat symlinks as if they were the pointed-to object unless you pass an option/flag specifically to say you want the symlink itself.
Gonna have to dig to see what else I can find.
#pathlib #path #is_mount #stdlib #behaviour #symlink #filesystem #mountpoint #mount
-
Now this is an interesting #Python problem. I don't know if it's a #bug, but it's a change in behaviour that I don't see documented.
I upgraded from #Debian 12/Bookworm to 13/Trixie, so the default Python3 changed from 3.11 to 3.13. A script of mine broke, because `pathlib.Path.is_mount()` changed behaviour when the path is a symlink (at least to a directory).
i.e. I'm testing a path that is a symlink. The symlink points to a directory. That directory *is* a mountpoint. The `.is_mount()` test in 3.11 returned True, while in 3.13 it returns False.
This seems wrong to me. Most path-manipulation functions transparently treat symlinks as if they were the pointed-to object unless you pass an option/flag specifically to say you want the symlink itself.
Gonna have to dig to see what else I can find.
#pathlib #path #is_mount #stdlib #behaviour #symlink #filesystem #mountpoint #mount
-
Now this is an interesting #Python problem. I don't know if it's a #bug, but it's a change in behaviour that I don't see documented.
I upgraded from #Debian 12/Bookworm to 13/Trixie, so the default Python3 changed from 3.11 to 3.13. A script of mine broke, because `pathlib.Path.is_mount()` changed behaviour when the path is a symlink (at least to a directory).
i.e. I'm testing a path that is a symlink. The symlink points to a directory. That directory *is* a mountpoint. The `.is_mount()` test in 3.11 returned True, while in 3.13 it returns False.
This seems wrong to me. Most path-manipulation functions transparently treat symlinks as if they were the pointed-to object unless you pass an option/flag specifically to say you want the symlink itself.
Gonna have to dig to see what else I can find.
#pathlib #path #is_mount #stdlib #behaviour #symlink #filesystem #mountpoint #mount
-
Now this is an interesting #Python problem. I don't know if it's a #bug, but it's a change in behaviour that I don't see documented.
I upgraded from #Debian 12/Bookworm to 13/Trixie, so the default Python3 changed from 3.11 to 3.13. A script of mine broke, because `pathlib.Path.is_mount()` changed behaviour when the path is a symlink (at least to a directory).
i.e. I'm testing a path that is a symlink. The symlink points to a directory. That directory *is* a mountpoint. The `.is_mount()` test in 3.11 returned True, while in 3.13 it returns False.
This seems wrong to me. Most path-manipulation functions transparently treat symlinks as if they were the pointed-to object unless you pass an option/flag specifically to say you want the symlink itself.
Gonna have to dig to see what else I can find.
#pathlib #path #is_mount #stdlib #behaviour #symlink #filesystem #mountpoint #mount
-
Der Proxmox Backup Server als LXC
In meinem Proxmox-Cluster habe ich eine Node, auf der ein Linux-Container als Proxmox Backup Server läuft.
#proxmox #backup #lxc #Container #pbs #Mountpoint #Fstab #Berechtigung #Linux
-
Der Proxmox Backup Server als LXC
In meinem Proxmox-Cluster habe ich eine Node, auf der ein Linux-Container als Proxmox Backup Server läuft.
#proxmox #backup #lxc #Container #pbs #Mountpoint #Fstab #Berechtigung #Linux
-
Der Proxmox Backup Server als LXC
In meinem Proxmox-Cluster habe ich eine Node, auf der ein Linux-Container als Proxmox Backup Server läuft.
#proxmox #backup #lxc #Container #pbs #Mountpoint #Fstab #Berechtigung #Linux
-
Der Proxmox Backup Server als LXC
In meinem Proxmox-Cluster habe ich eine Node, auf der ein Linux-Container als Proxmox Backup Server läuft.
#proxmox #backup #lxc #Container #pbs #Mountpoint #Fstab #Berechtigung #Linux
-
Der Proxmox Backup Server als LXC
In meinem Proxmox-Cluster habe ich eine Node, auf der ein Linux-Container als Proxmox Backup Server läuft.
#proxmox #backup #lxc #Container #pbs #Mountpoint #Fstab #Berechtigung #Linux
-
#Mountpoint for #AmazonS3 is now generally available: https://bit.ly/3OLS9Vi
The new open-source file client provides through a file interface the elastic storage and throughput of Amazon S3, supporting data transfer at up to 100 Gb/second between each EC2 instance and the object storage.
-
#Mountpoint for #AmazonS3 is now generally available: https://bit.ly/3OLS9Vi
The new open-source file client provides through a file interface the elastic storage and throughput of Amazon S3, supporting data transfer at up to 100 Gb/second between each EC2 instance and the object storage.
-
#Mountpoint for #AmazonS3 is now generally available: https://bit.ly/3OLS9Vi
The new open-source file client provides through a file interface the elastic storage and throughput of Amazon S3, supporting data transfer at up to 100 Gb/second between each EC2 instance and the object storage.
-
#Mountpoint for #AmazonS3 is now generally available: https://bit.ly/3OLS9Vi
The new open-source file client provides through a file interface the elastic storage and throughput of Amazon S3, supporting data transfer at up to 100 Gb/second between each EC2 instance and the object storage.
-
#Mountpoint for #AmazonS3 is now generally available: https://bit.ly/3OLS9Vi
The new open-source file client provides through a file interface the elastic storage and throughput of Amazon S3, supporting data transfer at up to 100 Gb/second between each EC2 instance and the object storage.
-
[ Mountpoint for Amazon S3 Now GA to Access Bucket Like Local File System ]
https://www.infoq.com/news/2023/08/mountpoint-amazon-s3-ga/ #AWS #S3 #MountPoint -
[ Mountpoint for Amazon S3 Now GA to Access Bucket Like Local File System ]
https://www.infoq.com/news/2023/08/mountpoint-amazon-s3-ga/ #AWS #S3 #MountPoint -
[ Mountpoint for Amazon S3 Now GA to Access Bucket Like Local File System ]
https://www.infoq.com/news/2023/08/mountpoint-amazon-s3-ga/ #AWS #S3 #MountPoint -
[ Mountpoint for Amazon S3 Now GA to Access Bucket Like Local File System ]
https://www.infoq.com/news/2023/08/mountpoint-amazon-s3-ga/ #AWS #S3 #MountPoint -
[ Mountpoint for Amazon S3 Now GA to Access Bucket Like Local File System ]
https://www.infoq.com/news/2023/08/mountpoint-amazon-s3-ga/ #AWS #S3 #MountPoint -
Well, the only #docker #container refusing to start is my @team #unifi controller throwing that #error 48 in the mongodb.log still and this bugs me so badly. I read that there could be (nah, will be) issues when using #mongodb on a #smb share. When #unmounting and using the remaining files in the bare #mountpoint, unifi starts as expected. I think that's evident enough. :blobcatnotlikethis:
-
Well, the only #docker #container refusing to start is my @team #unifi controller throwing that #error 48 in the mongodb.log still and this bugs me so badly. I read that there could be (nah, will be) issues when using #mongodb on a #smb share. When #unmounting and using the remaining files in the bare #mountpoint, unifi starts as expected. I think that's evident enough. :blobcatnotlikethis:
-
Well, the only #docker #container refusing to start is my @team #unifi controller throwing that #error 48 in the mongodb.log still and this bugs me so badly. I read that there could be (nah, will be) issues when using #mongodb on a #smb share. When #unmounting and using the remaining files in the bare #mountpoint, unifi starts as expected. I think that's evident enough. :blobcatnotlikethis:
-
Well, the only #docker #container refusing to start is my @team #unifi controller throwing that #error 48 in the mongodb.log still and this bugs me so badly. I read that there could be (nah, will be) issues when using #mongodb on a #smb share. When #unmounting and using the remaining files in the bare #mountpoint, unifi starts as expected. I think that's evident enough. :blobcatnotlikethis: