[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121022161040.GC9438@quack.suse.cz>
Date: Mon, 22 Oct 2012 18:10:40 +0200
From: Jan Kara <jack@...e.cz>
To: Fabio Coatti <fabio.coatti@...il.com>
Cc: Jan Kara <jack@...e.cz>, NeilBrown <neilb@...e.de>,
"Myklebust, Trond" <Trond.Myklebust@...app.com>,
Paul Bolle <pebolle@...cali.nl>, linux-kernel@...r.kernel.org,
Jeff Layton <jlayton@...hat.com>
Subject: Re: ext3 issue on 3.6.1
On Mon 22-10-12 18:01:56, Fabio Coatti wrote:
> 2012/10/22 Jan Kara <jack@...e.cz>:
> >> Uhu, my fault, I was sure to have answered to your request, sorry.
> >> So yes, we have an ext3 R/O partition mounted on that machine. The
> >> 3.6.3, with patch applied, dmesg is here:
> > Interesting. You seem to be using data=journal on R/O partition, don't
> > you? Can you also attach /proc/mounts?
> >
> > Also please try running a kernel with the attached patch and report the
> > warning. Thanks!
>
> Do you want to try the kernel without touching the mount
> configuration, right? (I mean, without (say) mounting ext2 the ext3 ro
> partition, right?)
Yes, leave things as they are now...
> right now I can't access the machine, but I recall that the partition
> is mounted rw, something is wrote onto it and then changed to r/o and
> among the options there is data=ordered.
/proc/mounts should show us whether data=ordered is in use. Actually the
warning is in function which is called only in data=journal mode so that's
why I think you are using it...
Honza
--
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists