One of the reasons we often partition /var separately from the root (/)
filesystem is so that things that grow forever (like log files) do not
exhaust the root filesystem of space. With that said, I’ve filled / a
bunch of times out of carelessness or stupidity and never had much more
than a need to clean and then retry what I was doing when it ran out of
space. The system has never crashed for me, that I remember anyway,
though I typically avoid filling up space entirely of course.
Anyway, why are you copying things to /var/run? The last time I checked
this was not meant to be the target of anything other than little runtime
stuff for various processes, such as PID files. Why it is partitioned
separately for you I cannot say, but that seems to be overkill. Still,
since /var is also out of space you probably need to do some cleanup on
your system in general. What is this rsync command doing for you (besides
obviously trying to copy stuff)?
On 08/27/2013 09:15 AM, ab pecked at the keyboard and wrote:
> One of the reasons we often partition /var separately from the root (/)
> filesystem is so that things that grow forever (like log files) do not
> exhaust the root filesystem of space. With that said, I’ve filled / a
> bunch of times out of carelessness or stupidity and never had much more
> than a need to clean and then retry what I was doing when it ran out of
> space. The system has never crashed for me, that I remember anyway,
> though I typically avoid filling up space entirely of course.
>
> Anyway, why are you copying things to /var/run? The last time I checked
> this was not meant to be the target of anything other than little runtime
> stuff for various processes, such as PID files. Why it is partitioned
> separately for you I cannot say, but that seems to be overkill. Still,
> since /var is also out of space you probably need to do some cleanup on
> your system in general. What is this rsync command doing for you (besides
> obviously trying to copy stuff)?
>
> Good luck.
Could you also post the exact rsync commands you are using?
How full is /var/run? Post the output to these commands, please:
Code:
du -h -c /var/run
df -h
mount
Maybe luckybackup is using /var/run as a temporary space, or something…
I cannot tell from here so you may want to ask the author on that one (saw
no mention of /var/run on the luckybackup sourceforge page). What else is
happening on your system that might use up space? Maybe /var/run is not
partitioned separately (your output made me think it was, but that may be
a stupid assumption on my part) and /var is the thing filled up, in which
case you may want to go clean up some logs or other temporary/cache data.
> I tried to do the du -h -c /var/run and it was listing tons of stuff.
> I stopped it and ran this instead du -h -c /var/run >1.txt
> and it generated a 9.8mb file.
> Yikes, what the heck is in there ?
That command lists ALL the files and its sizes. Perhaps you should add
the ‘-s’ switch, for summary.
> I have no idea what is supposed to be in var/run and apparently
> something in LuckyBackup is using it.
See wolfi323 post.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
Well, it’s cheating because it’s going across filesystems. How about
this? I’ll bet it shows 1.9 GB, so this isn’t that important now:
Code:
du -h -s -x -c /var/run
Anyway, the backup is going to /var/run/media/hexdump/6CC2-7168/ according
to your ‘ps’ output, but that is not something I see in your list of mount
points, meaning it is on the local system instead of on your external hard
drive. Fix luckybackup to point to a hard drive.