xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable

from [daniel+devel . linux . lkml] [Permanent Link][Original]
To: "Avuton Olrich" <avuton@xxxxxxxxx>
Subject: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
From: daniel+devel.linux.lkml@xxxxxxxxxxx
Date: Mon, 19 Jun 2006 12:35:25 +0200
Cc: "Linux Kernel Mailing List" <linux-kernel@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <3aa654a40606190044q43dca571qdc06ee13d82d979@xxxxxxxxxxxxxx> (Avuton Olrich's message of "Mon, 19 Jun 2006 00:44:58 -0700")
Organization: Flexserv
References: <3aa654a40606190044q43dca571qdc06ee13d82d979@xxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux) 
"Avuton Olrich" <avuton@xxxxxxxxx> writes:

The same here.
after a complete mkfs.xfs under 2.6.17-rc6 it was solved.

Same if i boot 2.6.8 mk.xfs, boot into 2.6.16 the xfs get "shreddered"
a directly boot from .8 to .17-rc6 works. so i think there was a bug in .16
in the transition of the xfs wich got solved somewhere in the .17.rc? time.

> Filesystem "sda1": Corruption of in-memory data detected.  Shutting
> down filesystem: sda1

Daniel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable, Avuton Olrich
Next by Date:  xfs internal error in fs/xfs/xfs_da_btree.c, Martin Murray
Previous by Thread:  XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable, Avuton Olrich
Next by Thread:  Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable, Nathan Scott
Indexes:  [Date] [Thread] [Top] [All Lists]