From: Eric Sandeen <sandeen@sandeen.net>
To: Oliver Pinter <oliver.pntr@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS errors / BUG / panic, with 2.6.25.7-queue (and older 2.6.25.y)
Date: Sun, 15 Jun 2008 20:11:39 -0500 [thread overview]
Message-ID: <4855BDCB.3030103@sandeen.net> (raw)
In-Reply-To: <6101e8c40806150914k1226611ej52b20b7bb9ffa9d5@mail.gmail.com>
Oliver Pinter wrote:
> sorry, but I did not learn English, is going a little bit slowly in this manner.
That's, ok, it's just useful to know what you were doing when it
panicked. I'm sure you speak english better than I speak you native
language ;)
> yeah, under poweroff (init 0) panics the system
Hm, interesting.
> but now it was him that you say the antecedents apt-get update &
> upgrade and git-update-tree (is is a script, that updated 3 git tree
> (linux-2.6, linux-2.6.25.y and stable-queue)) , that is heavy disc i/o
> with much small files
So, you had a lot of IO just before shutdown?
-Eric
> On 6/15/08, Eric Sandeen <sandeen@sandeen.net> wrote:
>> Oliver Pinter wrote:
>>> this is the debian way of the unmounting the root fs:
>> Ok we're slowly getting to useful information.
>>
>> So you were shutting down the system when the panic happened, correct?
>>
>> -Eric
>>
>>
>
>
next prev parent reply other threads:[~2008-06-16 1:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-14 19:41 XFS errors / BUG / panic, with 2.6.25.7-queue (and older 2.6.25.y) Oliver Pinter
2008-06-15 1:53 ` Eric Sandeen
2008-06-15 12:38 ` Oliver Pinter
2008-06-15 15:58 ` Eric Sandeen
2008-06-15 16:09 ` Oliver Pinter
2008-06-15 16:12 ` Eric Sandeen
2008-06-15 16:14 ` Oliver Pinter
2008-06-15 16:17 ` Oliver Pinter
2008-06-15 16:27 ` Oliver Pinter
2008-06-16 1:11 ` Eric Sandeen [this message]
2008-06-16 4:52 ` Dave Chinner
2008-06-16 10:01 ` Christoph Hellwig
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=4855BDCB.3030103@sandeen.net \
--to=sandeen@sandeen.net \
--cc=oliver.pntr@gmail.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox