Cameron Simpson wrote:
Yes, but it's easier to watch it go down after each backup.
Assuming nothing else is consuming space on this partition.
There are more backups on there. :) And I just needed one of them.
du -ks *
not
du -ks .
Eh?
du -hs *
23M daily.0123M daily
On 15:43 22 Jun 2003, Ashley M. Kirchner <[EMAIL PROTECTED]> wrote:
| 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
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 direc
On 14:19 22 Jun 2003, Ashley M. Kirchner <[EMAIL PROTECTED]> wrote:
| Cameron Simpson wrote:
| >How sure are you? Rsync on its own doesn't do that - you need to have
| >a separate pass that makes a link tree and then rsync that. Is that
| >your setup?
|
|Oh yeah, daily.01 gets linked to daily.0
Cameron Simpson wrote:
How sure are you? Rsync on its own doesn't do that - you need to have
a separate pass that makes a link tree and then rsync that. Is that
your setup?
Oh yeah, daily.01 gets linked to daily.02 by running a 'cp -al' on
them. Then Rsync runs on daily.01.
A "df -k ." on yo
On 02:07 22 Jun 2003, Ashley M. Kirchner <[EMAIL PROTECTED]> wrote:
|I'm using rsync with hard links to keep backups of my servers. This
| process creates a daily structure that looks like this:
|
|backup/daily.01
| /daily.02
| /daily.03
| etc., etc.
|
|No
I'm using rsync with hard links to keep backups of my servers. This
process creates a daily structure that looks like this:
backup/daily.01
/daily.02
/daily.03
etc., etc.
Now I know that only the first one contains actual files, while the
rest are all hard li
