From: Carsten Menke <bootsy52@gmx.net>
To: Russell Cattelan <cattelan@thebarn.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: XFS: xfs_trans_cancel Filesystem shutdown
Date: Sat, 10 Jan 2009 18:56:21 +0100 [thread overview]
Message-ID: <4968E145.3050807@gmx.net> (raw)
In-Reply-To: <49678756.10303@thebarn.com>
Russell Cattelan wrote:
>
> cc the xfs list.
>
> Since you have wiped the file system it is going to be hard to get to
> the bottom of th issue.
> It looks like you hit two different issues here, one is a shutdown and
> one look like a deadlock?
>
>
> In the future it would be helpful to xfs_metadump the file system and
> then file a bug and attach the metadump image.
>
Yes, I know, I have seen this after I created the new filesystem while further
searching the net for possible causes of this, that a xfs_metadump is most of
the time needed to debug this. But as this is a production system the system had
to go online again as soon as possible, so I just decided
to share the information I've got afterwards. The next time I will do the
xfs_metadump (but then, I hope also that I won't be hit by the problem once again).
Regards
Carsten
--
"There are two major products that came out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence." --Jeremy S. Anderson
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Carsten Menke <bootsy52@gmx.net>
To: Russell Cattelan <cattelan@thebarn.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: XFS: xfs_trans_cancel Filesystem shutdown
Date: Sat, 10 Jan 2009 18:56:21 +0100 [thread overview]
Message-ID: <4968E145.3050807@gmx.net> (raw)
In-Reply-To: <49678756.10303@thebarn.com>
Russell Cattelan wrote:
>
> cc the xfs list.
>
> Since you have wiped the file system it is going to be hard to get to
> the bottom of th issue.
> It looks like you hit two different issues here, one is a shutdown and
> one look like a deadlock?
>
>
> In the future it would be helpful to xfs_metadump the file system and
> then file a bug and attach the metadump image.
>
Yes, I know, I have seen this after I created the new filesystem while further
searching the net for possible causes of this, that a xfs_metadump is most of
the time needed to debug this. But as this is a production system the system had
to go online again as soon as possible, so I just decided
to share the information I've got afterwards. The next time I will do the
xfs_metadump (but then, I hope also that I won't be hit by the problem once again).
Regards
Carsten
--
"There are two major products that came out of Berkeley: LSD and UNIX.
We don't believe this to be a coincidence." --Jeremy S. Anderson
next prev parent reply other threads:[~2009-01-10 17:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 20:05 XFS: xfs_trans_cancel Filesystem shutdown Carsten Menke
2009-01-09 17:20 ` Russell Cattelan
2009-01-09 17:20 ` Russell Cattelan
2009-01-10 17:56 ` Carsten Menke [this message]
2009-01-10 17:56 ` Carsten Menke
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=4968E145.3050807@gmx.net \
--to=bootsy52@gmx.net \
--cc=cattelan@thebarn.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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.