Cameron Simpson wrote:

No, I meant df. Because that will tell you how much space is really being
used up _without_ having to run a du over the tree (which can lie unless
it sees every link).

Eh, df only shows me the total size on the partition/drive table. Not the size of each individual directory. Like on the current server:

df -k .
Filesystem           1k-blocks      Used Available Use% Mounted on
/dev/hda1              2063504   1042948    915736  54% /

Well, "du -ks" if you want to be portable (and succinct).

No, this only shows me the contents of that parent directory, not individual ones below it. See, this is what I wanted (spanned across to save on message length):

du -h -max-depth=1 .
2.1G ./daily.01   928M ./daily.08   334M ./daily.15   402M ./daily.22
1.6G ./daily.02   820M ./daily.09   962M ./daily.16   318M ./daily.23
1.5G ./daily.03   804M ./daily.10   823M ./daily.17   245M ./daily.24
1.4G ./daily.04   616M ./daily.11   732M ./daily.18   190M ./daily.25
1.3G ./daily.05   512M ./daily.12   642M ./daily.19   166M ./daily.26
1.2G ./daily.06   406M ./daily.13   551M ./daily.20   151M ./daily.27
1.1G ./daily.07   296M ./daily.14   2.8G ./daily.21   120M ./daily.28
23G  .

...sizes for each individual directory, as well as a total for all (23G). A 'du -ks' (or -hs) only tells me that 23G, and nothing else.

I presume you removed it with --exclude, yes? Otherwise you'll be copying it
and _then_ removing it - wasteful.

Eh no, not that kind of remove. I removed the current log file, compressed it and restarted the process. So, as far as Rsync is concerned, it's still there, and will still be backed up, but it's much smaller now. And eventually that size will trickle down through the other daily and reclaim the space used up. I'm not worried about it (anymore.) Yes, I'm aware it will now have to remove the current ones in the backup tree, but I don't care about that part. The end result is, I will eventually reclaim that space, so it's all good. Considering how fast the backup runs, I'm not worried about t he time it takes.

It takes a directory like yours with lots of backups
and removes the oldest until a certain amount of free space is present.

See, normally I wouldn't have this problem. The 11 servers I've been backing up since last year are fitting nicely on a single 120G drive (with a 28 day loop like you've seen above). It's just that this particular server started getting heavy use for one of it's applications and I totally forgot that I needed to rotate its log file. Lesson learned.

Thanks again!

--
H| I haven't lost my mind; it's backed up on tape somewhere.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
IT Director / SysAdmin / WebSmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.






--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to