On Monday 16 August 2004 19:01, viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:snip
On Mon, Aug 16, 2004 at 06:52:50PM -0400, Gene Heskett wrote:
Well, I am seing some dups, but they are so volatile that no twoThat's OK. Keep in mind that you have a *lot* of these guys and
runs will report the same allocations as dups, and its never more
than 2 using /proc/fs/ext3 | sort | uniq -c | sort -nr |grep -v '
1 '
Consecutive runs will show anywhere from 3 to 10 or 12 dups, but
never is an address repeated between runs.
How is this to be interpreted?
your cat(1) makes a lot of read(2) calls. So what you see is
<starting to read>
<see inode #n that is about to be evicted>
<read some more>
<inode #n gets evicted, quite possibly - due to memory pressure from
cat(1) or sort(1)>
<read more>
<somebody wants the same inode again>
<read more>
<see the inode #n we'd just had read from disk again>
So few duplicates are all right.
I hope so. I've got a real hoodoozy here, being out of memory (well,
maybe 30 megs left) when my nightly run of rsync started, everything
came to a grinding halt. I couldn't even get to the screen the tail -f on the log was running in, but after walking away for 10 minutes. I can once again. However, things seem to be partially functional so I'm going to see if I can do some cut-n-paste from the log screen to here, but I probably can't send it as sendmail was one of the items the OOM killer killed. According to top, I'm about 250 megs into the swap, very suddenly. No swap was in use at 23:55 local.
I cannot start any new shells, as before. Is there any usable dna in this sample?
Reboot time I guess :(((