From: Eric Sandeen <sandeen@redhat.com>
To: muellejo@aschendorff.de
Cc: linux-ext4@vger.kernel.org
Subject: Re: newsletter: Re: ext4 crashes on nfs server
Date: Thu, 19 Jan 2012 11:18:36 -0600 [thread overview]
Message-ID: <4F18506C.9050601@redhat.com> (raw)
In-Reply-To: <OFBE4B8BA4.837045FD-ONC125798A.005E13C5@aschendorff.de>
On 1/19/12 11:07 AM, muellejo@aschendorff.de wrote:
> Thanks Eric,
>
>> Looks like an oops/panic/BUG - but are you sure you didn't start copying a line or two too late?
>
> Well, there are other interesting information in /var/log/messages about 10 minutes
> I uploaded them here http://vam-emp.aschendorff.de/tmp/
That all looks like a mess. I think you need to go through your logs and find
the first sign of trouble, and start there.
I don't know what is dumping out all that hex...
-Eric
> We also suffered from a huge amount from these log entries
> they are somehow related to disabling ipv6 and vsftp but I
> guess this is not really related to our ext4 crashes.
> After now upgrading vsftp they disappeared, debian has got a bug for that
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590653
>
> Jan 18 20:52:26 ez-nfs-prod-vm1 kernel: [14913.361952] lo: Disabled Privacy Extensions
>
> Thanks
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-01-19 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 13:20 ext4 crashes on nfs server muellejo
2012-01-19 15:25 ` Eric Sandeen
2012-01-19 17:07 ` newsletter: " muellejo
2012-01-19 17:18 ` Eric Sandeen [this message]
2012-01-27 12:27 ` muellejo
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=4F18506C.9050601@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=muellejo@aschendorff.de \
/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.