| To: | Eric Sandeen <sandeen@xxxxxxx> |
|---|---|
| Subject: | Re: Corruption of in-memory data detected. |
| From: | Jan Derfinak <ja@xxxxxxxxxxxx> |
| Date: | Sat, 10 Sep 2005 00:32:12 +0200 (CEST) |
| Cc: | csc@xxxxxxxxxxx, evilninja <evilninja@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <432207DB.9000800@xxxxxxx> |
| References: | <Pine.LNX.4.58.0509082156530.9425@xxxxxxxxxxxxxxxxxx> <4321CDDD.8010607@xxxxxxx> <Pine.LNX.4.58.0509092130160.8548@xxxxxxxxxxxxxxxxxx> <1126296865.16932.71.camel@xxxxxxxxxxxxxxxxxx> <432207DB.9000800@xxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
On Fri, 9 Sep 2005, Eric Sandeen wrote: > Chris Croswhite wrote: > > This also happens on i386 (ran into the problem last evening). > > > > > One more notice: I tried to use CONFIG_KEXEC on x86_64 and kernel could > > > not > > > recognize XFS superblock. I didn't try it on i386. > > Hm, how do you hit the problem? Kernel: XFS_VERSION_STRING "SGI-XFS CVS-2005-09-07_05:00_UTC" I have / on ext3 and all other partitions on xfs. During boot, kernel mounted / and printed "XFS: bad magic number". I extended line 211 in xfs_mount.c to print sbp->sb_magicnum and it was 0. > I'm not up to speed on KEXEC. Did you do anything other than build with it on > to hit the problem? :) No, I could not boot with kexec. jan -- |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Corruption of in-memory data detected., Eric Sandeen |
|---|---|
| Next by Date: | Re: Corruption of in-memory data detected., evilninja |
| Previous by Thread: | Re: Corruption of in-memory data detected., Eric Sandeen |
| Next by Thread: | Re: Corruption of in-memory data detected., Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |