From: Eddie Atherton <stunnel@attglobal.net>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error xfs_trans_cancel at line 1164 of file fs/xfs/xfs_trans.c
Date: Sun, 24 May 2009 21:06:43 -0700 [thread overview]
Message-ID: <4A1A1953.6030009@attglobal.net> (raw)
In-Reply-To: <20090525005132.GR16929@discord.disaster>
[-- Attachment #1.1: Type: text/plain, Size: 862 bytes --]
Dave Chinner wrote:
> On Tue, May 19, 2009 at 11:58:35PM -0700, Eddie Atherton wrote:
>
>> I'm trying to install a clean Slackware 12.2 (2.6.27.7) under ESXi, and
>> can almost guarantee getting this error immediately after formatting the
>> root partition. It's happened 4 out of the 5 times I've tried, so far.
>>
>> The sequence of commands, after digging through the install scripts,
>> that lead to this failure are just:
>>
>> mkfs.xfs
>> mount
>> mkdir
>>
>
> That's bizarre. Can you provide a xfs_metadump image of the fs after
> the shutdown has occurred?
>
I can try, but it's kinda difficult, as this happens in a VM, where I
don't have a filesystem to capture the data to, or any "communication"
to the "outside world" to transfer it out. But, hey, that's what
challenges are all about.
Cheers,
Eddie
> Cheers,
>
> Dave.
>
[-- Attachment #1.2: Type: text/html, Size: 1370 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-05-25 4:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 6:58 XFS internal error xfs_trans_cancel at line 1164 of file fs/xfs/xfs_trans.c Eddie Atherton
2009-05-20 15:19 ` Eric Sandeen
2009-05-20 16:51 ` Eddie Atherton
2009-05-25 0:51 ` Dave Chinner
2009-05-25 4:06 ` Eddie Atherton [this message]
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=4A1A1953.6030009@attglobal.net \
--to=stunnel@attglobal.net \
--cc=david@fromorbit.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox