From: Paul Paquette <paulp@bowes.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: oops during rsync
Date: Thu, 13 Jul 2006 08:19:46 -0400 [thread overview]
Message-ID: <44B63A62.9040408@bowes.com> (raw)
In-Reply-To: <200607130045_MC3-1-C4D4-AC62@compuserve.com>
Chuck Ebbert wrote:
> In-Reply-To: <44B5452B.4070503@bowes.com>
>
>
> On Wed, 12 Jul 2006 14:53:31 -0400, Paul Paquette wrote:
>
>
>> Below is the oops, then the kernel config and system map.
>>
>
>
>> ...
>>
>
>
>> Call Trace:
>> [<c0162b68>] dquot_drop+0x35/0x68
>>
>
> Is that the whole trace? It should be longer and there should be a Code:
> line as well.
>
>
That was what was left in the logs on the disk after a reboot.
--
Paul Paquette
Programmer/Analyst
Bowes Publishers Ltd.
Subsidiary of Sun Media Corporation
A Quebecor Company
paulp@bowes.com
(519) 471-8520 x377
next prev parent reply other threads:[~2006-07-13 12:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 4:43 oops during rsync Chuck Ebbert
2006-07-13 12:19 ` Paul Paquette [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 18:53 Paul Paquette
2006-07-12 19:08 ` Dave Jones
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=44B63A62.9040408@bowes.com \
--to=paulp@bowes.com \
--cc=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
/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