| To: | Jes Sorensen <jes@xxxxxxx>, Linux Kernel ML <linux-kernel@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx, xfs-masters@xxxxxxxxxxx, stern@xxxxxxxxxxxxxxxxxxx, sekharan@xxxxxxxxxx, akpm@xxxxxxxx, David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | [xfs-masters] Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS) |
| From: | Jes Sorensen <jes@xxxxxxx> |
| Date: | Thu, 13 Apr 2006 16:10:06 +0200 |
| In-reply-to: | <20060413135000.GB6663@xxxxxxxxxxxxxxxxx> |
| References: | <20060413052145.GA31435@xxxxxxxxxxxxxxxxx> <20060413072325.GF2732@xxxxxxxxxxxxxxxxx> <yq0k69tuauh.fsf@xxxxxxxxxxxxxx> <20060413135000.GB6663@xxxxxxxxxxxxxxxxx> |
| Reply-to: | xfs-masters@xxxxxxxxxxx |
| Sender: | xfs-masters-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 1.5 (X11/20060223) |
Herbert Poetzl wrote: > sure, bootup is fine, as it boots on ext2/3 but once > it is up, and I mount the newly created xfs filesystem > the (virtual) machine (QEMU) panics ... > > will provide all the data shortly via separated mail What happens if you run it on real hardware? Would be nice to eliminate QEMU from the equation, in case it doesn't like the funny split. Cheers, Jes |
| Previous by Date: | [xfs-masters] Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS), Herbert Poetzl |
|---|---|
| Next by Date: | [xfs-masters] [Bug 6380] XFS corruption with Linux 2.6.16, bugme-daemon |
| Previous by Thread: | [xfs-masters] Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS), Herbert Poetzl |
| Next by Thread: | [xfs-masters] Re: notifier chain problem? (was Re: 2.6.17-rc1 did break XFS), Herbert Poetzl |
| Indexes: | [Date] [Thread] [Top] [All Lists] |