The corruption can only occur if your HAMMER filesystem became full
or nearly full sometime in the last 45 days or so with a kernel built
sometime in the last 45 days. To check for the corruption you need
an unmounted or completely idle filesystem and then run (using the
latest hammer utility):
:
:The corruption can only occur if your HAMMER filesystem became full
:or nearly full sometime in the last 45 days or so with a kernel built
:sometime in the last 45 days. To check for the corruption you need
:an unmounted or completely idle filesystem and then run (using the
:latest hammer
Hi,
Yah, indeed it does :'(
sudo hammer -f /dev/serno/QM2.s1a checkmap
Volume header records=0 next_tid=00010841bec0
bufoffset=4404
Collecting allocation info from B-Tree: done
BM block=20001000 calc 114688 free, got 1163264
Now what? Is
On Mon, 19 Apr 2010 21:43:49 -0700 (PDT)
Matthew Dillon dil...@apollo.backplane.com wrote:
:Does this show all errors for sure? I had corrunptions on one
:filesystem but no such errors were printed.
It should find any corruption. It won't find partial recoveries
(basically
:Hi,
:
:Yah, indeed it does :'(
:
: sudo hammer -f /dev/serno/QM2.s1a checkmap
:Volume header records=0 next_tid=00010841bec0
:bufoffset=4404
:Collecting allocation info from B-Tree: done
:BM block=20001000 calc 114688 free, got 1163264
:
:Now
On Tue, Apr 20, 2010 at 11:03:55AM -0700, Matthew Dillon wrote:
:Yah, indeed it does :'(
:
: sudo hammer -f /dev/serno/QM2.s1a checkmap
:Volume header records=0 next_tid=00010841bec0
:bufoffset=4404
:Collecting allocation info from B-Tree: done
:BM
A serious HAMMER corruption issue came up soon after the release.
This issue can occur when a HAMMER filesystem becomes full or nearly
full and reblocking occurs while the filesystem is also loaded down
with other write activity. The reblocking activity itself can cause
an
On Mon, 19 Apr 2010 08:55:00 -0700 (PDT)
Matthew Dillon dil...@apollo.backplane.com wrote:
SNIP
The corruption can only occur if your HAMMER filesystem became full
or nearly full sometime in the last 45 days or so with a kernel built
sometime in the last 45 days. To check for
:Does this show all errors for sure? I had corrunptions on one
:filesystem but no such errors were printed.
It should find any corruption. It won't find partial recoveries
(basically directory entries with no corresponding inode). Those
can be rm'd.
