linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylvain Rochet <gradator@gradator.net>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
	linux-nfs@vger.kernel.org
Subject: Re: 2.6.28.9: EXT3/NFS inodes corruption
Date: Tue, 4 Aug 2009 13:15:05 +0200	[thread overview]
Message-ID: <20090804111505.GA6433@gradator.net> (raw)
In-Reply-To: <20090803222901.GB23162@duck.suse.cz>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

Hi,


On Tue, Aug 04, 2009 at 12:29:01AM +0200, Jan Kara wrote:
> 
>   OK, I've found some time and written the debugging patch. Hopefully it
> will tell us more. It should output messages to the kernel log if it
> finds something suspicious - like:
> No dentry for unlinked inode...
> Dentry ... for unlinked inode ... has no parent
> Found directory entry ... for unlinked inode
> 
>   When you see such messages in the log, send them to me please. Also
> attach the System.map file so that I can translate the address where
> i_nlink was dropped - for that ext3 should be compiled into the kernel
> (should not be a module). Thanks a lot for testing.

Patch applied.

And there is already a lot of output.

http://edony.tuxfamily.org/~grad/bazooka/System.map-2.6.30.4
http://edony.tuxfamily.org/~grad/bazooka/config-2.6.30.4
http://edony.tuxfamily.org/~grad/bazooka/kern.log


Sylvain

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2009-08-04 11:15 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 [this message]
     [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
     [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=20090804111505.GA6433@gradator.net \
    --to=gradator@gradator.net \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).