<div dir="ltr"><div><span style="font-size:14px">(resending as I forgot to send to users@ again..)</span></div><div><span style="font-size:14px"><br></span></div><div><span style="font-size:14px">You might be seeing what I've mentioned in the previous reply.</span><br></div><div><div style="font-size:14px">If that's the case it's probably not a bug, and you see this in older versions too.</div><div style="font-size:14px"><span class="im"><div><br></div><div>> Note that there seems to be a bug in hammer where a valid filesystem would still show ^B in hammer show output. I usually run some test scripts (that contain there 3 commands) before I commit something, but I see ^B in hammer show every once in a while. It could be that the way hammer show tests the filesystem is missing something and results in showing errors that aren't really errors. This occurred at least back in DragonFly 4.0 era in 2014, and it still does on 4.4. It has been on my todo list for a long time.</div><div><br></div></span><div>If you have redirected that hammer show output to a file, you can copy-paste that part (where it showed ^B), or put the whole output to somewhere else.</div></div><div style="font-size:14px">(If you haven't you may still be able to reproduce it as long as that particular btree nodes have not been changed (e.g. splitted) by whatever filesystem operations you have on your system)</div></div><div style="font-size:14px"><br></div><div style=""><span style="font-size:14px">btw, as you may know, hammer show output prints the name of directory entries (i.e. file name), so be careful if it's not appropriate to send that.</span><br></div><div style="font-size:14px"><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-02-21 1:06 GMT+09:00 PeerCorps Trust Fund <span dir="ltr"><<a href="mailto:ipc@peercorpstrust.org" target="_blank">ipc@peercorpstrust.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">So after a recent run of hammer show, I get the following:<br>
<br>
HAMMER zone statistics<br>
zone # blocks items used[B] used[%]<br>
zone 0 0 0 0 0<br>
zone 1 0 0 0 0<br>
zone 2 0 0 0 0<br>
zone 3 0 0 0 0<br>
zone 4 0 0 0 0<br>
zone 5 0 0 0 0<br>
zone 6 0 0 0 0<br>
zone 7 0 0 0 0<br>
zone 8 201 383556 1571045376 93.1757<br>
zone 9 2 50127 4809376 28.6661<br>
zone 10 122556 16105131 1027866722304 99.9798<br>
zone 11 1 24 119312 1.42231<br>
zone 12 0 0 0 0<br>
zone 13 0 0 0 0<br>
zone 14 0 0 0 0<br>
zone 15 0 0 0 0<br>
----------------------------------------------------------------------<br>
total 122760 16538838 1029442696368 99.9667<br>
54 bad nodes<br>
1895 bad elms<br>
<br>
Does this output mean that I should be restoring the above disk from backup or something else is going on here?<br>
<br>
Mike<br>
<span class="im HOEnZb"><br>
<br>
On 01/22/2016 05:57 PM, Tomohiro Kusumi wrote:<br>
</span><div class="HOEnZb"><div class="h5">> If you are to redirect the hammer show output to a file, it's better to<br>
> write to a file on different filesystem (e.g. ufs or another hammer).<br>
><br>
> It's possible that hammer show never ends because what hammer show does is<br>
> run through all ondisk btree nodes. Writing a file is adding nodes into the<br>
> btree of that filesystem.<br>
><br>
><br>
> 2016-01-23 0:44 GMT+09:00 Tomohiro Kusumi <<a href="mailto:kusumi.tomohiro@gmail.com">kusumi.tomohiro@gmail.com</a>>:<br>
><br>
>> (resending as i forgot to send to users@...)<br>
>><br>
>> # hammer -v -f ${DEV} blockmap<br>
>> # hammer -v -f ${DEV} checkmap<br>
>> # hammer -v -f ${DEV} show<br>
>><br>
>> These three do some validation from different point of view.<br>
>> If the last two lines of each output says 0 error, then no error was found<br>
>> at least by what these 3 commands test for.<br>
>><br>
>> Note that there seems to be a bug in hammer where a valid filesystem would<br>
>> still show ^B in hammer show output. I usually run some test scripts (that<br>
>> contain there 3 commands) before I commit something, but I see ^B in hammer<br>
>> show every once in a while. It could be that the way hammer show tests the<br>
>> filesystem is missing something and results in showing errors that aren't<br>
>> really errors. This occurred at least back in DragonFly 4.0 era in 2014,<br>
>> and it still does on 4.4. It has been on my todo list for a long time.<br>
>><br>
>><br>
>> 2016-01-22 23:59 GMT+09:00 PeerCorps Trust Fund <<a href="mailto:ipc@peercorpstrust.org">ipc@peercorpstrust.org</a>>:<br>
>><br>
>>> Hi All,<br>
>>><br>
>>> In ZFS, the command "zpool status" gives a succinct overview of the<br>
>>> status of mounted file systems. In particular, whether there might be<br>
>>> checksum errors on files or other data structures.<br>
>>><br>
>>> NAME STATE READ WRITE CKSUM<br>
>>> tank ONLINE 0 0 0<br>
>>> ada0p2 ONLINE 0 0 0<br>
>>><br>
>>> In HAMMER the "show" command provides an extremely detailed output of all<br>
>>> data structures and CRC verifications.<br>
>>><br>
>>> I've used the command:<br>
>>><br>
>>> hammer -f /dev/serno/disk-serial-number show |grep B------<br>
>>><br>
>>> On a mounted disk and the output was clean (nothing) after running for<br>
>>> some time with noted disk activity. Does this mean that all CRCs are valid?<br>
>>> Are there other commands in addition to "show" that allow for validation<br>
>>> and examination of data structures on HAMMER volumes?<br>
>>><br>
>>> --<br>
>>> Mike<br>
>>><br>
</div></div></blockquote></div><br></div>