On Wed, Jun 24, 2015 at 06:38:42PM -0700, Marc MERLIN wrote:
> Known already fixed problem, or not?
> 
> [680279.909435] kernel BUG at fs/btrfs/extent_io.c:4548!
> [680279.926208] invalid opcode: 0000 [#1] SMP

After reboot, I'm now seeing this if that helps:
[  272.826942] BTRFS info (device dm-1): bad tree block level 137
[  272.958006] BTRFS: read error corrected: ino 1 off 226779136 (dev 
/dev/mapper/dshelf1 sector 459312)
[  274.349430] BTRFS (device dm-1): parent transid verify failed on 229019648 
wanted 99011 found 36
[  274.479700] BTRFS: read error corrected: ino 1 off 229019648 (dev 
/dev/mapper/dshelf1 sector 463688)
[  311.040191] BTRFS (device dm-1): parent transid verify failed on 229048320 
wanted 99011 found 36
[  311.192380] BTRFS: read error corrected: ino 1 off 229048320 (dev 
/dev/mapper/dshelf1 sector 463744)
[  311.228687] BTRFS (device dm-1): parent transid verify failed on 229052416 
wanted 99011 found 36
[  311.258980] BTRFS: read error corrected: ino 1 off 229052416 (dev 
/dev/mapper/dshelf1 sector 463752)
[  312.416949] BTRFS (device dm-1): parent transid verify failed on 229064704 
wanted 99011 found 36
[  312.502828] BTRFS: read error corrected: ino 1 off 229064704 (dev 
/dev/mapper/dshelf1 sector 463776)
[  313.464054] BTRFS (device dm-1): parent transid verify failed on 229072896 
wanted 99011 found 36
[  313.568913] BTRFS: read error corrected: ino 1 off 229072896 (dev 
/dev/mapper/dshelf1 sector 463792)
[  314.216027] BTRFS (device dm-1): parent transid verify failed on 229076992 
wanted 99011 found 36
[  314.301930] BTRFS: read error corrected: ino 1 off 229076992 (dev 
/dev/mapper/dshelf1 sector 463800)

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/  
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to