https://www.dragonflydigest.com/2019/10/22/hammer2-emergency-space-mode/ A running description of activity related to DragonFly BSD. Fri, 25 Oct 2019 02:48:50 +0000 hourly 1 https://wordpress.org/?v=6.9.4 https://www.dragonflydigest.com/2019/10/22/hammer2-emergency-space-mode/comment-page-1/#comment-488421 Fri, 25 Oct 2019 02:48:50 +0000 https://www.dragonflydigest.com/?p=23652#comment-488421 Just in case, as I don’t want to leave false information around: The more pessimistic interpretation was based on reading the source comments added, but I don’t know enough about HAMMER2 meta data to know whether it’s always going to differ for contents of older snapshots and current contents. If it does, what I posted is wrong, but if it doesn’t, it’s not. Wherever what’s attached to current files and directories is also part of a snapshot, emergency removal could corrupt the snapshot, according to the info in the commit.

]]> https://www.dragonflydigest.com/2019/10/22/hammer2-emergency-space-mode/comment-page-1/#comment-488414 Wed, 23 Oct 2019 07:37:54 +0000 https://www.dragonflydigest.com/?p=23652#comment-488414 Looking at the details, it isn’t snapshots created in the mode which is the issue (the mode preventing the creation of new data), but rather that old snapshots are likely to be corrupted. Basically, it seems to disable data growth and allow invasive surgery to free up space, copying of old snapshots to other storage beforehand being a good idea.

]]>