LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Gaudenz Steinlin <gaudenz@soziologie.ch> To: xfs-masters@oss.sgi.com Cc: xfs@oss.sgi.com, johannes@sipsolutions.net, linux-kernel@vger.kernel.org Subject: filesystem corruption on xfs after 2.6.25-rc1 (bisected, powerpc related?) Date: Mon, 25 Feb 2008 12:23:10 +0100 [thread overview] Message-ID: <20080225112310.GA5516@soziologie.ch> (raw) Hi Since upgrading to 2.6.25-rc1 I see filesystem corruption on my XFS filesystem. I can reproduce this by doing "git reset --hard v2.6.25-rc1" on a git checkout which is on some other revision. Git outputs strange error messages (like file xxx is a directory when xxx really is a file) and sometimes the filesystem "hangs" (I can no longer do any operations on it even from another shell). If I reboot with a working kernel and check the filesystem xfs_check reports many errors. I also see the problem when doing other (not related to git) operations on the filesystem. Git reset is just the easiest way to reproduce it. I was able to track this corruption down to commit a69b176df246d59626e6a9c640b44c0921fa4566 ([XFS] Use the generic bitops rather than implementing them ourselves.) using git bisect. Reverting edd319dc527733e61eec5bdc9ce20c94634b6482 ([XFS] Fix xfs_lowbit64) to avoid merge conflicts and the faulty commit on top of 2.6.25-rc3 fixes the problem. My filesystem is on an LVM2 logical volume and my computer is a PowerBook G4 (model 5,8). I'm using GCC 4.2.3. My problem is similar to the problem Johannes Berg reported in: http://oss.sgi.com/archives/xfs/2008-02/msg00244.html AFAIK Johannes also uses a PowerBook. Maybe this is an endianness issue. Gaudenz -- Ever tried. Ever failed. No matter. Try again. Fail again. Fail better. ~ Samuel Beckett ~
next reply other threads:[~2008-02-25 11:56 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-25 11:23 Gaudenz Steinlin [this message] 2008-02-25 11:34 ` filesystem corruption on xfs after 2.6.25-rc1 (bisected, powerpc related?) Johannes Berg 2008-02-25 18:15 ` [xfs-masters] " Eric Sandeen 2008-02-25 23:42 ` Rafael J. Wysocki 2008-02-25 23:48 ` Eric Sandeen 2008-02-25 23:52 ` Rafael J. Wysocki 2008-02-25 23:57 ` [xfs-masters] " Christoph Hellwig 2008-02-26 0:13 ` Rafael J. Wysocki 2008-02-26 7:34 ` Gaudenz Steinlin 2008-02-26 11:44 ` Gaudenz Steinlin 2008-02-26 18:11 ` Johannes Berg 2008-02-28 14:40 ` Eric Sandeen 2008-02-26 20:05 ` Eric Sandeen 2008-02-26 20:59 ` Mark Goodwin
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=20080225112310.GA5516@soziologie.ch \ --to=gaudenz@soziologie.ch \ --cc=johannes@sipsolutions.net \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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).