kurtking wrote: ⤴
Sun Sep 08, 2019 3:59 pm
The questions imply you not being clear on this, and I am afraid my earlier reply is still the most directly useful manner in which I can explain things. Allow me to quote myself:
A mount point is just a directory; when you copied to under said directory when nothing was in fact mounted on it it just did exactly that: copy to under said directory, hence, onto the filesystem on which said directory lived, hence, the root filesystem.
That is, other than some minimal space to keep the system up in the first place, not any
free space on your root fs is required for a backup to an external drive, using rsync or whatever else you may care for. When the external drive's plugged in its fs is (should be, rather) mounted on the directory /media/kurt/659186ea-07f8-4dea-94c2-eca5cba35de8 and any location under that directory refers to a location on
said external drive's fs. Your rsync command copies only to
the external drive's fs, nowhere else.
the external drive's fs had in fact been mounted, that is. The mountpoint is as said a mere directory, and when you ran the copying script when it was not it just copied to under that directory which at that point is a mere directory on your root fs. All this is independent of rsync, cp, or whatever else you may use to do the copying. I.e.,
1/2. Nothing specific.
3. The "/media/user/device" folder should show as empty with the device unmounted. Should even disappear if the drive is not connected or switched on: that mountpoint is dynamically created and destroyed by the system so as
to mount the external drive's fs on.
4. Not in a fundamental sense; as long as the system is not all the way down on free space to what is considered minimal to keep it chugging along in the first place the fact that no space on the root fs is required to copy to the external drive's fs means there's no connection.
5. 5% but don't bother even knowing that; it's as explained fully secondary to anything this issue is about.
Only at 6 are we at the the issue itself. Yes, if you with the external drive disconnected make sure that anything that is then still under /media/kurt/659186ea-07f8-4dea-94c2-eca5cba35de8 is something that is either already backed up to the external drive or something still available from wherever you backed it up from, you can simply delete the entire folder "659186ea-07f8-4dea-94c2-eca5cba35de8" from under /media/kurt. It should as explained not be
there with the external drive unconnected or switched of.
It's very likely that a backup just ran when the drive wasn't plugged in or, by the way, when "659186ea-07f8-4dea-94c2-eca5cba35de8" wasn't in fact its automatic mountpoint under /media/kurt any longer due to you reformatting the external drive (giving its fs a different UUID) or through giving it a label. That is, verify that mountpount IS still the correct mountpoint by simply looking in /media/kurt after connecting the drive and after having cleaned it up first as per above, but otherwise, just make sure that the external drive is in fact mounted on the expected location when you run the backup script.