The only reason I even know about them is they got mentioned in SGI's IRIX Sysadmin courses.
Only not relevant for those who actually know about inodes already. This is the first time I've actually heard of this happening, ever. Files of any size will almost always run out of drive space before inodes run out in 99.9999% of situations. It actually makes sense that said it was mostly directories. How is that not relevant? more files = more inodes being used That is not relevant except for that fact that large files would have filled drive space and likely been noticed. Literally, we were making 30K files an hour or so. But it did not (had already done that.) It was real files causing the issue, nothing orphaned. Someone mentioned rebooting to try to solve it. Is this a bad way of thinking or simply not needed?Īre there any others a good idea or generally a best practice to said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space said in Fedora 26 No Space Left on Device with Plenty of Space I could've sworn there was a post here related to a reboot solving it
My thinking is that should they become changed somehow, this will set it straight again.
I know some of it may be redundant, as in they already may be set as such by default. Strictly SYSCTL speaking, here's what I got so far:
0 kommentar(er)
