From: Sylvain Rochet <gradator-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
To: Jan Kara <jack-AlSwsSmVLrQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Al Viro <viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
Sylvain Rochet <gradator-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
Subject: Re: 2.6.28.9: EXT3/NFS inodes corruption
Date: Thu, 20 Aug 2009 19:19:53 +0200 [thread overview]
Message-ID: <20090820171952.GA15133@gradator.net> (raw)
In-Reply-To: <20090812223453.GC10729-pwKtmJkCtMINMLpHRKhSow@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
Hi!,
On Thu, Aug 13, 2009 at 12:34:53AM +0200, Jan Kara wrote:
> Hello,
>
> On Thu 06-08-09 15:15:56, Sylvain Rochet wrote:
> > > I have one idea what could cause your filesystem corruption, although
> > > it's a wild guess... Please try attached oneliner.
> >
> > Running since yesterday.
>
> Any news after a week of running? How often did the corruption happen
> previously?
Sorry for the late answer, I was lurking at HAR ;-)
So, everything is fine, but the problem happened only one time on this
server, so we cannot conclude anything after a few weeks. However,
I now have physical access back, so we will switch back to the former
server where the problem happened quite frequently, then we will see!
By the way, syslogd is happy, eating about 350 MiB of kernel logs a day ;)
Sylvain
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2009-08-20 17:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090420162017.GA28079@gradator.net>
[not found] ` <20090716172749.GC3740@atrey.karlin.mff.cuni.cz>
[not found] ` <20090725151751.GA6419@gradator.net>
2009-07-27 15:42 ` 2.6.28.9: EXT3/NFS inodes corruption Jan Kara
2009-07-28 11:27 ` Sylvain Rochet
[not found] ` <20090728112715.GA8442-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
2009-07-28 13:52 ` Jan Kara
2009-07-28 16:41 ` Sylvain Rochet
2009-07-28 21:12 ` J. Bruce Fields
2009-08-04 10:50 ` Sylvain Rochet
2009-07-29 12:58 ` Jan Kara
2009-08-04 11:02 ` Sylvain Rochet
[not found] ` <20090728164142.GA13662-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
2009-08-03 22:29 ` Jan Kara
2009-08-04 11:15 ` Sylvain Rochet
[not found] ` <20090804111505.GA6433-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
2009-08-04 22:56 ` Jan Kara
[not found] ` <20090804225619.GB11097-pwKtmJkCtMINMLpHRKhSow@public.gmane.org>
2009-08-06 13:15 ` Sylvain Rochet
[not found] ` <20090806131555.GA23359-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
2009-08-06 17:05 ` J. Bruce Fields
2009-08-12 22:34 ` Jan Kara
[not found] ` <20090812223453.GC10729-pwKtmJkCtMINMLpHRKhSow@public.gmane.org>
2009-08-20 17:19 ` Sylvain Rochet [this message]
[not found] ` <20090820171952.GA15133-XWGZPxRNpGHk1uMJSBkQmQ@public.gmane.org>
2009-08-21 0:00 ` Simon Kirby
2009-08-21 10:51 ` Sylvain Rochet
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=20090820171952.GA15133@gradator.net \
--to=gradator-xwgzpxrnpghk1umjsbkqmq@public.gmane.org \
--cc=jack-AlSwsSmVLrQ@public.gmane.org \
--cc=linux-ext4-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=viro-RmSDqhL/yNMiFSDQTTA3OLVCufUGDwFn@public.gmane.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;
as well as URLs for NNTP newsgroup(s).