<div dir="ltr">Hello Justin,<div><br></div><div>Thanks for the work around.</div><div>I'll give it a shot and will get back with my findings. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Nov 22, 2014 at 10:38 PM, Justin Sherrill <span dir="ltr"><<a href="mailto:justin@shiningsilence.com" target="_blank">justin@shiningsilence.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>From man 8 hammer </div><div> prune softlink-dir</div><div> Prune the file system based on previously created snapshot</div><div> softlinks. Pruning is the act of deleting file system history.</div><div> The prune command will delete file system history such that the</div><div> file system state is retained for the given snapshots, and all</div><div> history after the latest snapshot. By setting the per PFS</div><div> parameter prune-min, history is guaranteed to be saved at least</div><div> this time interval. All other history is deleted.</div><div><br></div><div>If you set prune-min to 1 day, you are guaranteeing that at least 1 day of history is saved.</div><div><br></div><div>Mounting nohistory means it does not create new historic information, but it does not remove any existing data.</div><div><br></div><div>Also, df reports the overall space used for a Hammer volume every time. That 63G reported for /Backup5/vm8 is the overall space used for data, not the space of that mounted point. Hammer is only storing the changes to data, not a copy of all the data itself from that point in time, so it's a much smaller portion of the data.</div><span class=""><div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">Backup5 </span><span style="font-family:arial,sans-serif;font-size:13px"> 929G 63G 866G 7% /Backup5</span><br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">/Backup5/pfs/@@-1:00001 </span><span style="font-family:arial,sans-serif;font-size:13px"> 929G 63G 866G 7% /Backup5/vms8</span><br></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></span><div><span style="font-family:arial,sans-serif;font-size:13px">Here's my suggestion:</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">- Tell Hammer to stop taking snapshots in the config file, and to run cleanup steps for as long as needed. Note that the period of 1 minute means it won't start any of the cleanup processes within 1 minute of doing it previously. Normally that's set to a day, since cleanup is done daily.</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">(cd /Backup5; hammer viconfig)</span></div><div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><div><font face="arial, sans-serif">snapshots 0d 0d</font></div><div><font face="arial, sans-serif">prune 1m 0m</font></div><div><font face="arial, sans-serif">reblock 1m 0m</font></div><div><font face="arial, sans-serif">recopy 1m 0m</font></div><div><font face="arial, sans-serif">rebalance 1m 0m</font></div></div><div><br></div><div><span style="font-family:arial,sans-serif;font-size:13px">- Use 'hammer snapls' and 'hammer snaprm' to remove any remaining snapshots.</span><br></div><div><br></div><div>- prune-everything.</div><div><br></div><div>Note that I haven't tried this myself.</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 21, 2014 at 12:56 AM, Rohit Menon <span dir="ltr"><<a href="mailto:rohit.forum33@gmail.com" target="_blank">rohit.forum33@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hello Matt,<br><br></div>This was what I did to prune all snapshot data.<br></div>However this part of history stays.<br><br></div>This is my prune output <br><br>dfly-bkpsrv1# hammer prune-everything /Backup5<br>Prune /Backup5/: EVERYTHING<br>Prune /Backup5/: objspace 8000000000000000:0000 7fffffffffffffff:ffff pfs_id 0<br>Prune /Backup5/: prune_min is 1d/00:00:00<br>Prune /Backup5/ succeeded<br>Pruned 0/2065540 records (0 directory entries) and 0 bytes<br><br></div>I modified the prune_min to 1 day since I could see that it wasnt exactly clearing history when set to default.<br></div>The history data still stays <br>==============================================<br>dfly-bkpsrv1# cd vms8/<br>dfly-bkpsrv1# ll<br>total 0<br>dfly-bkpsrv1# <br>=========================================================<br>dfly-bkpsrv1# cd /Backup5/@@0x0000000108329000<br>dfly-bkpsrv1# ll<br>total 0<br>drwxr-xr-x 1 root wheel 0 Nov 19 10:16 pfs<br>drwxr-xr-x 1 root wheel 0 Nov 18 09:24 vms8<br>dfly-bkpsrv1# cd vms8<br>dfly-bkpsrv1# ls -l<br>total 0<br>drwxr-xr-x 1 root wheel 0 Nov 18 13:05 containers<br>drwxr-xr-x 1 root wheel 0 Nov 18 14:29 env<br>drwx------ 1 root wheel 0 Nov 18 13:05 lost+found<br>drwxr-xr-x 1 root wheel 0 Nov 18 14:29 volumes<br>dfly-bkpsrv1# <br>=================================================<br></div>And it is also using up space.<br><br><br><br><div><div><div>Backup5 929G 63G 866G 7% /Backup5<br>/Backup5/pfs/@@-1:00001 929G 63G 866G 7% /Backup5/vms8<br></div></div></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 21, 2014 at 10:59 AM, Matthew Dillon <span dir="ltr"><<a href="mailto:dillon@backplane.com" target="_blank">dillon@backplane.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>Rohit, there is a kitchen sink command to remove all history called 'prune-everything'. Try running that on the target mount. 'hammer prune-everything <blah>'.<br><br>-Matt</div><div><div><div><br>On Nov 20, 2014, at 8:11 PM, Rohit Menon <<a href="mailto:rohit.forum33@gmail.com" target="_blank">rohit.forum33@gmail.com</a>> wrote:<br><br></div><div><div dir="ltr"><div><div>Hello Justin,<br><br></div>That makes things a bit more clear now.<br></div>Since its a read-only filesystem how am I supposed to do that<br><div class="gmail_quote">Also I tried mounting the filesystem nohistory the data is still shows used up.<br></div><div class="gmail_quote">So does this mean I cannot remove this history.<br></div><div class="gmail_quote"><br>On Fri, Nov 21, 2014 at 6:20 AM, Justin Sherrill <span dir="ltr"><<a href="mailto:justin@shiningsilence.com" target="_blank">justin@shiningsilence.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">What you are looking at is file history. Snapshots are moments in time of the entire volume. File history is a record of every change synced to disk. From hammer(5):<div><br></div><div>If you've removed snapshots and pruned, it should have removed a great deal of the data. File history since the last snapshot is preserved, though. If you don't want any history kept, mount the Hammer volume nohistory. (see mount_hammer(8) )</div><div><br></div><div>It will always be read-only because it's history; it already happened. If you want to modify the files, you will need to copy them out and then modify them on the "now" version of the filesystem.</div><div><br></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 20, 2014 at 7:28 AM, Rohit Menon <span dir="ltr"><<a href="mailto:rohit.forum33@gmail.com" target="_blank">rohit.forum33@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div>Hello Antonio,<br><br></div>I have removed all the snapshots of the volume.<br></div>This has been done as documented that is hammer snapls and then prune-everything.<br></div>I have noticed a peculiar behaviour though.<br></div>Im able to generate a transaction Id using hammer synctid<br></div>When I cd to the directory that is /Backup5/@@0x0000000108329000<br></div>Im able to see the data but cannot remove it as it is a read-only filesystem.<br></div>I tried to null mount this and remove it to no avail.<br></div>Is there something Im still missing.<br><div><div><div><div><div><br></div></div></div></div></div></div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Nov 19, 2014 at 5:17 PM, Antonio Huete Jiménez <span dir="ltr"><<a href="mailto:tuxillo@quantumachine.net" target="_blank">tuxillo@quantumachine.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Rohit,<br>
<br>
There must be a snapshot referencing those files and that is the reason why they keep using the space.<br>
Check hammer(8) manpage on how to operate snapshots.<br>
<br>
Best regards,<br>
Antonio Huete<div><div><br>
<br>
Quoting Rohit Menon <<a href="mailto:rohit.forum33@gmail.com" target="_blank">rohit.forum33@gmail.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
Im a newbie to BSD as a whole.<br>
Currently my company has a backup solution implemented in dragonfly BSD<br>
with hammer.<br>
My question is simple, is there a specific way to remove a file/folder in<br>
hammer.<br>
<br>
The situation is like:<br>
<br>
I moved 65G data to one of my directoies /Backup under a specifc directory.<br>
When I removed it the the files and folders have been removed but the<br>
occupied space remains.<br>
I have done hammer cleanup and prune but to no avail.<br>
<br>
<br>
Can you please guide me on where Im going wrong.<br>
</blockquote>
<br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><div class="gmail_extra"><br></div></div>
</div></div></div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>