All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Vladislav Bolkhovitin <vst@vlnb.net>, linux-ext4@vger.kernel.org
Subject: Crash after umount'ing a disconnected disk (Re: extfs reliability)
Date: Wed, 4 Aug 2010 14:03:25 -0400	[thread overview]
Message-ID: <20100804180325.GL9453@thunk.org> (raw)

Ping?

Have you had a chance to check out whether this patch solves the
problem you were complaining with respect to yanking out the last
iSCSI or FC link to a hard drive, and then umounting the disk
afterwards?

If you could try it out, I would really appreciate it.

       	     	    	   	 - Ted


On Thu, Jul 29, 2010 at 02:58:49PM -0400, Ted Ts'o wrote:
> OK, I've looked at your kernel messages, and it looks like the problem
> comes from this:
> 
> 	/* Debugging code just in case the in-memory inode orphan list
> 	 * isn't empty.  The on-disk one can be non-empty if we've
> 	 * detected an error and taken the fs readonly, but the
> 	 * in-memory list had better be clean by this point. */
> 	if (!list_empty(&sbi->s_orphan))
> 		dump_orphan_list(sb, sbi);
> 	J_ASSERT(list_empty(&sbi->s_orphan));   <====
> 
> This is a "should never happen situation", and we crash so we can
> figure out how we got there.  For production kernels, arguably it
> would probably be better to print a message and a WARN_ON(1), and then
> not force a crash from a BUG_ON (which is what J_ASSERT is defined to
> use).
> 
> Looking at your messages and the ext4_delete_inode() warning, I think
> I know what caused it.  Can you try this patch (attached below) and
> see if it fixes things for you?
> 
> > I already reported such issues some time ago, but my reports were
> > not too much welcomed, so I gave up. Anyway, anybody can easily do
> > my tests at any time.
> 
> My apologies.  I've gone through the linux-ext4 mailing list logs, and
> I can't find any mention of this problem from any username @vlnb.net.
> I'm not sure where you reported it, and I'm sorry we dropped your bug
> report.  All I can say is that we do the best that we can, and our
> team is relatively small and short-handed.
> 
> 							- Ted
> 
> From a190d0386e601d58db6d2a6cbf00dc1c17d02136 Mon Sep 17 00:00:00 2001
> From: Theodore Ts'o <tytso@mit.edu>
> Date: Thu, 29 Jul 2010 14:54:48 -0400
> Subject: [PATCH] patch explicitly-drop-inode-from-orphan-list-on-ext4_delete_inode-failure
> 
> ---
>  fs/ext4/inode.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
> index a52d5af..533b607 100644
> --- a/fs/ext4/inode.c
> +++ b/fs/ext4/inode.c
> @@ -221,6 +221,7 @@ void ext4_delete_inode(struct inode *inode)
>  				     "couldn't extend journal (err %d)", err);
>  		stop_handle:
>  			ext4_journal_stop(handle);
> +			ext4_orphan_del(NULL, inode);
>  			goto no_delete;
>  		}
>  	}
> -- 
> 1.7.0.4
> 

             reply	other threads:[~2010-08-04 18:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04 18:03 Ted Ts'o [this message]
2010-08-04 18:24 ` Crash after umount'ing a disconnected disk (Re: extfs reliability) Vladislav Bolkhovitin
2010-08-05 19:29 ` Vladislav Bolkhovitin
2010-08-05 21:17   ` Ted Ts'o
2010-08-06 13:23     ` Vladislav Bolkhovitin
2010-08-06 18:10       ` Ted Ts'o
2010-08-09 18:45         ` Crash after umount'ing a disconnected disk and JBD: recovery failed " Vladislav Bolkhovitin
2010-08-09 19:32           ` Ted Ts'o
2010-08-13 19:04             ` Vladislav Bolkhovitin

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=20100804180325.GL9453@thunk.org \
    --to=tytso@mit.edu \
    --cc=linux-ext4@vger.kernel.org \
    --cc=vst@vlnb.net \
    /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.