From: Konstantin Kletschke <lists@ku-gbr.de>
To: Miquel van Smoorenburg <mikevs@xs4all.net>,
Oliver Pinter <oliver.pntr@gmail.com>,
linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
xfs@oss.sgi.com, xfs-masters@oss.sgi.com
Subject: Re: XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c
Date: Mon, 23 Jun 2008 09:58:00 +0200 [thread overview]
Message-ID: <20080623075800.GA2379@anita> (raw)
In-Reply-To: <20080622225355.GD11558@disturbed>
Am 2008-06-23 08:53 +1000 schrieb Dave Chinner:
> > If I am correct, this fix is included in 2.6.26-rc6:
>
> Yes, so if you're seeing it again then there's a different problem.
There seems to be something else too, yes.
> Please provide a pointer to a xfs_metadump image of the filesystem
> and the steps to reproduce the error from the image so we can
> get to the bottom of it...
Well, accidently I formatted the partition. I needed my /var partition
urgently and I tried the following: I tarred the whole /var from a
rescue system (gentoo amd64 live cd version 2007.0, IIRC there is 2.6.19
on it) and did a "rm -fr /var/*" and tried to tar it back.
While this worked for my /home (I also had the error there), tarring
back the files onto /var produced several oopses in dmesg and the
userspace complained about an error in a (directory?) structure not
being accessible/not able to be initialized. Well, I took screenshots of
this but accidently I lost them on my cam and due to running a rescue
system there is no reminisence in a file of this.
I formatted the partition then :-(
I could only try to reproduce it on my home partition... Does anybody
have a clue how this can be done or a suspicion how to trigger this
error?
King Regards, Konsti
--
GPG KeyID EF62FCEF
Fingerprint: 13C9 B16B 9844 EC15 CC2E A080 1E69 3FDA EF62 FCEF
prev parent reply other threads:[~2008-06-23 7:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 10:30 XFS internal error xfs_trans_cancel at line 1163 of file fs/xfs/xfs_trans.c lists
2008-06-12 14:33 ` Oliver Pinter
2008-06-12 22:24 ` [xfs-masters] " Eric Sandeen
2008-06-13 7:15 ` Konstantin Kletschke
2008-06-12 22:27 ` Miquel van Smoorenburg
2008-06-13 3:08 ` Dave Chinner
2008-06-13 7:24 ` Konstantin Kletschke
2008-06-13 15:36 ` [xfs-masters] " Dave Chinner
2008-06-13 11:28 ` Miquel van Smoorenburg
2008-06-16 15:50 ` Miquel van Smoorenburg
2008-06-17 5:31 ` Dave Chinner
2008-06-20 5:27 ` Konstantin Kletschke
2008-06-20 5:45 ` Konstantin Kletschke
2008-06-22 22:53 ` Dave Chinner
2008-06-23 7:58 ` Konstantin Kletschke [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=20080623075800.GA2379@anita \
--to=lists@ku-gbr.de \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikevs@xs4all.net \
--cc=oliver.pntr@gmail.com \
--cc=xfs-masters@oss.sgi.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 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.