Corey Wright wrote:
i was curious if vhashify cleaned up after itself (delete orphaned
instances of files in hash directory), and it appears it doesn't. these
commands should do the job. well, technically this just lists files with a
hardlink count of 1 and prints the total size in bytes of all listed files
on the last line (so you know how much space you are saving).
find /etc/vservers/.defaults/vdirbase/.hash/ -type f -printf "%n %s %p\n" |
grep '^1[[:space:]]' | awk '{ sum += $2; print $3 } END { print sum }'
to delete those listed files, add to the end:
| while read FILE; do rm -f ${FILE}; done
does anybody see any problem with my logic?
Corey,
Did you hear anything on this? I ran the query on a 12+ guest system (
all FC5 ) and it ran for well over a couple of minutes before I got
tired of watching the output. This leads me to think I've got lots of
orphans. I'd like to get rid of them ( Save the inodes! ) but want to
understand what I'm doing first. Rather not fubar a live system.
I'm not sure I fully understand how vhashify works. Where are the
actual files located. Are the entries in
/etc/vservers/.defaults/vdirbase/.hash/
links to the actual files and then each guest links to these -- links?
Rod
--
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
