On Tue, 1 Jul 2014 10:55:11 +0200, Matteo Croce <technoboy85@gmail.com> wrote:
> 2014-07-01 10:42 GMT+02:00 Darrick J. Wong <darrick.wong@oracle.com>:
> > On Tue, Jul 01, 2014 at 08:26:19AM +0200, David Jander wrote:
> >>
> >> Hi,
> >>
> >> On Mon, 30 Jun 2014 23:30:10 +0200
> >> Matteo Croce <technoboy85@gmail.com> wrote:
> >>
> >> > I was web surfing and using gimp when:
> >> >
> >> > EXT4-fs error (device sda2): ext4_mb_generate_buddy:756: group 199,
> >> > 9414 clusters in bitmap, 9500 in gd; block bitmap corrupt.
> >>
> >> I was about to post a related question to this list. I am also seeing these
> >> kind of errors when using ext4 on latest mainline (I began testing with 3.15
> >> where I saw this and now in 3.16-rc3 it is still there).
> >> It happens almost instantly when power-cycling the system (unclean shutdown).
> >> The next time the system boots, I get these errors.
> >>
> >> AFAICT, you are using a pretty recent kernel. Which version exactly?
> >>
> >> > Aborting journal on device sda2-8.
> >> > EXT4-fs (sda2): Remounting filesystem read-only
> >
> > Matteo, could you please post the full dmesg log somewhere?  I'm interested in
> > what happens before all this happens, because...
> 
It is reasonable to understand what is the root of this issue in disk
driver or issue in JBD. Can you please run fio utility for your disk
( can be found here http://git.kernel.dk/?p=fio.git;a=summary) or simply
install it with your favorite pkg mgr (yum install fio) 
and run verify job for your disk (see attachment)
like follows: # fio disk-verify.fio
####### job:disk-verify.fio #############