From: daniel+devel.linux.lkml@flexserv.de
To: "Avuton Olrich" <avuton@gmail.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-xfs@oss.sgi.com
Subject: Re: XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable
Date: Mon, 19 Jun 2006 12:35:25 +0200 [thread overview]
Message-ID: <87slm15t76.fsf@xserver.flexserv.de> (raw)
In-Reply-To: <3aa654a40606190044q43dca571qdc06ee13d82d979@mail.gmail.com> (Avuton Olrich's message of "Mon, 19 Jun 2006 00:44:58 -0700")
"Avuton Olrich" <avuton@gmail.com> 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
next prev parent reply other threads:[~2006-06-19 10:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-19 7:44 XFS crashed twice, once in 2.6.16.20, next in 2.6.17, reproducable Avuton Olrich
2006-06-19 10:35 ` daniel+devel.linux.lkml [this message]
2006-06-20 6:10 ` Nathan Scott
2006-06-20 6:38 ` Avuton Olrich
2006-06-20 6:43 ` Nathan Scott
2006-06-20 6:50 ` Avuton Olrich
2006-06-20 6:52 ` Nathan Scott
2006-06-20 8:20 ` Avuton Olrich
2006-06-20 8:39 ` Duncan Sands
2006-06-22 2:56 ` Nathan Scott
2006-06-25 10:09 ` Duncan Sands
2006-06-25 13:55 ` Duncan Sands
2006-06-20 6:40 ` Avuton Olrich
2006-06-20 8:57 ` Justin Piszcz
2006-06-20 17:01 ` Avuton Olrich
2006-06-20 17:15 ` Justin Piszcz
2006-06-20 17:21 ` Avuton Olrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87slm15t76.fsf@xserver.flexserv.de \
--to=daniel+devel.linux.lkml@flexserv.de \
--cc=avuton@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.