- This topic has 4 replies, 2 voices, and was last updated 5 years, 9 months ago by
.
-
Posts
-
I’ve hardly used the program and yet it has consumed all of my available hard drive space!! Around 20-30GB in hardly any usage!! On top of this it is not obvious where it has stored all this junk so I can’t even find it to delete it and free up my system again!
Where are the files which have been saved and are consuming my hard drive on a Linux system?? (Ubuntu 18.04 to be precise.)
Why the hell is it generating so much data consumption? And by the looks of it somewhere in the system drive as I can’t find that much data anyhwhere in Home!!! This is really bad form!
First error message said out of space, checking available space on my drive confirms this, subsequent attempts to run the program produce the error in the attached screenshot.
I’ve hardly used the program and yet it has consumed all of my available hard drive space!!
Unlikely. The files generated during a profiling run are at most a few megabytes in size.
Around 20-30GB in hardly any usage!! On top of this it is not obvious where it has stored all this junk so I can’t even find it to delete it and free up my system again!
Check the usual storage location, i.e. %APPDATA%\DisplayCAL\storage. I doubt this is related to DisplayCAL.
OK you have given me 20GB of syslog and kern.log in barely any usage! That is rather retarded isn’t it!!!!
Aug 5 10:47:45 ThisOne kernel: [ 4322.087978] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before use
Aug 5 10:47:45 ThisOne kernel: [ 4322.087981] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before use
Aug 5 10:47:45 ThisOne kernel: [ 4322.087985] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before use
Aug 5 10:47:45 ThisOne kernel: [ 4322.087988] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before use
Aug 5 10:47:45 ThisOne kernel: [ 4322.087991] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before use
Aug 5 10:47:45 ThisOne kernel: [ 4322.087994] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before use
Aug 5 10:47:45 ThisOne kernel: [ 4322.087997] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before use
Aug 5 10:47:45 ThisOne kernel: [ 4322.088000] usb 2-2: usbfs: process 10658 (spotread) did not claim interface 0 before useOn and on and on for gigbytes!!
Aug 5 10:45:05 ThisOne kernel: [ 4162.081792] usb 2-2: usbfs: process 9516 (dispcal) did not claim interface 0 before use
Aug 5 10:45:05 ThisOne kernel: [ 4162.081799] usb 2-2: usbfs: process 9516 (dispcal) did not claim interface 0 before use
Aug 5 10:45:05 ThisOne kernel: [ 4162.081822] usb 2-2: usbfs: process 9516 (dispcal) did not claim interface 0 before use
Aug 5 10:45:05 ThisOne kernel: [ 4162.081830] usb 2-2: usbfs: process 9516 (dispcal) did not claim interface 0 before use
Aug 5 10:45:05 ThisOne kernel: [ 4162.081836] usb 2-2: usbfs: process 9516 (dispcal) did not claim interface 0 before useLoose the foul language.
OK you have given me 20GB of syslog and kern.log in barely any usage!
So? Seems like the message (which is bogus, by the way) that is repeated over and over again is coming from usbfs, which is not part of a standard Ubuntu distro, it was disabled a long time ago (probably rightfully so, seeing as it apparently tries to access a non-storage-related USB device). Is this really Ubuntu 18.04 or something you cobbled together yourself?
This is really Ubuntu 18.04 (well Ubuntu Studio but still an official Ubuntu release.)
I apologise for the expletive and harsh language. Rather frustrated over the ignoring of my previous post and message to the mail list coupled with it then seeming to junk the system for no reason. I hope you will forgive me.
I don’t think the log issue was due to DisplayCal in isolation now. I believe what may have triggered it was me being a little silly and trying to run a spotread command from the terminal while DisplayCal was running and using the device. Still it should not produce gigabytes of messages in literally minutes.
Thank you kindly for the quick response to this issue and providing what I’m sure will be a useful tool (once I’m used to it) as open source to the community.
