On Mon 22-10-12 18:18:10, Fabio Coatti wrote:
> 2012/10/22 Jan Kara :
> > On Mon 22-10-12 18:01:56, Fabio Coatti wrote:
> >> 2012/10/22 Jan Kara :
> >> >> 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
>
2012/10/22 Jan Kara :
> On Mon 22-10-12 18:01:56, Fabio Coatti wrote:
>> 2012/10/22 Jan Kara :
>> >> 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:
>> > Int
On Mon 22-10-12 18:01:56, Fabio Coatti wrote:
> 2012/10/22 Jan Kara :
> >> 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 usin
2012/10/22 Jan Kara :
>> 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 al
On Mon 22-10-12 12:23:03, Fabio Coatti wrote:
> 2012/10/19 Fabio Coatti :
> > 2012/10/19 NeilBrown :
> >> On Fri, 19 Oct 2012 00:08:09 +0200 Jan Kara wrote:
> >>
> >>> On Thu 18-10-12 23:40:25, Paul Bolle wrote:
> >>> > On Thu, 2012-10-18 at 23:23 +0200, Jan Kara wrote:
> >>> > > On Fri 12-10-12 1
2012/10/19 NeilBrown :
> On Fri, 19 Oct 2012 00:08:09 +0200 Jan Kara wrote:
>
>> On Thu 18-10-12 23:40:25, Paul Bolle wrote:
>> > On Thu, 2012-10-18 at 23:23 +0200, Jan Kara wrote:
>> > > On Fri 12-10-12 14:57:55, Fabio Coatti wrote:
>> > > > [13031.051521] [ cut here ]
>>
On Fri, 19 Oct 2012 00:08:09 +0200 Jan Kara wrote:
> On Thu 18-10-12 23:40:25, Paul Bolle wrote:
> > On Thu, 2012-10-18 at 23:23 +0200, Jan Kara wrote:
> > > On Fri 12-10-12 14:57:55, Fabio Coatti wrote:
> > > > [13031.051521] [ cut here ]
> > > > [13031.051576] WARNING: a
On Thu 18-10-12 23:40:25, Paul Bolle wrote:
> On Thu, 2012-10-18 at 23:23 +0200, Jan Kara wrote:
> > On Fri 12-10-12 14:57:55, Fabio Coatti wrote:
> > > [13031.051521] [ cut here ]
> > > [13031.051576] WARNING: at fs/inode.c:280 drop_nlink+0x1b/0x35()
> > > [13031.051624] Ha
On Thu, 2012-10-18 at 23:23 +0200, Jan Kara wrote:
> On Fri 12-10-12 14:57:55, Fabio Coatti wrote:
> > [13031.051521] [ cut here ]
> > [13031.051576] WARNING: at fs/inode.c:280 drop_nlink+0x1b/0x35()
> > [13031.051624] Hardware name: ProLiant BL465c G7
> > [13031.051668] Pid
On Fri 12-10-12 14:57:55, Fabio Coatti wrote:
> Hi all,
> I'm getting this message on a hp g7 server with kernel 3.6.1:
>
> [ 248.026545] [ cut here ]
> [ 248.026723] WARNING: at fs/ext3/inode.c:1754
> ext3_journalled_writepage+0x55/0x1a7()
> [ 248.026920] Hardware name:
Hi all,
I'm getting this message on a hp g7 server with kernel 3.6.1:
[ 248.026545] [ cut here ]
[ 248.026723] WARNING: at fs/ext3/inode.c:1754
ext3_journalled_writepage+0x55/0x1a7()
[ 248.026920] Hardware name: ProLiant BL465c G7
[ 248.027049] Pid: 2266, comm: flush-8:
11 matches
Mail list logo