Bug #1115
closed
HAMMER:hammer prune-everything's problem
Added by lhmwzy over 16 years ago.
Updated almost 16 years ago.
Description
My file system structure:
/www /www/mirror
When I delete files from /www/mirror and run "hammer prune-everything
/www",it does not free space for /www
Only free space by run "hammer prune-everything /www/mirror".
Is that a problem?
I think "hammer prune-everything /www" should free space for any sub
file system on /www.
You need to do e.g. 'hammer reblock /www'
Sascha
It seems 'hammer reblock /www' doesn't free space.
Following the prune-everything, it should. Can you do:
hammer prune-everything /www
hammer reblock /www
..and after that give us the output of:
df -h
du -hs /www
Sascha
:My file system structure:
:/www /www/mirror
:When I delete files from /www/mirror and run "hammer prune-everything
:/www",it does not free space for /www
:Only free space by run "hammer prune-everything /www/mirror".
:Is that a problem?
:I think "hammer prune-everything /www" should free space for any sub
:file system on /www.
No, the reblocking and pruning commands are pre-PFS only. So you
have to run them both on /www and also on /www/mirror.
-Matt
Matthew Dillon
<dillon@backplane.com>
: No, the reblocking and pruning commands are pre-PFS only. So you
: have to run them both on /www and also on /www/mirror.
Er I meant 'per-PFS' :-). The main mount counts as a PFS (PFS #0),
and any PFS you create with 'hammer pfs-master' or 'hammer pfs-slave'
is a PFS and must be pruned and reblocked separately.
-Matt
Matthew Dillon
<dillon@backplane.com>
OK,this is exactly what I meet.
I create /www/mirror with hammer pfs-master.
Tks.
Also available in: Atom
PDF