| To: | csc@xxxxxxxxxxx |
|---|---|
| Subject: | Re: Corruption of in-memory data detected. |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Fri, 09 Sep 2005 17:08:27 -0500 |
| Cc: | Jan Derfinak <ja@xxxxxxxxxxxx>, evilninja <evilninja@xxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1126296865.16932.71.camel@xxxxxxxxxxxxxxxxxx> |
| References: | <Pine.LNX.4.58.0509082156530.9425@xxxxxxxxxxxxxxxxxx> <4321CDDD.8010607@xxxxxxx> <Pine.LNX.4.58.0509092130160.8548@xxxxxxxxxxxxxxxxxx> <1126296865.16932.71.camel@xxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0 (X11/20041206) |
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? [root@lite ~]# zcat /proc/config.gz | grep KEXEC CONFIG_KEXEC=y [root@lite ~]# mount | grep xfs /dev/sda1 on /mnt/sda1 type xfs (rw) [root@lite ~]# dmesg | grep -i xfsSGI XFS with ACLs, security attributes, realtime, large block numbers, dmapi support, no debug enabled SGI XFS Quota Management subsystem XFS mounting filesystem sda1 Ending clean XFS mount for filesystem: sda1I'm not up to speed on KEXEC. Did you do anything other than build with it on to hit the problem? :) -Eric |
| <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., Jan Derfinak |
| Previous by Thread: | Re: Corruption of in-memory data detected., Chris Croswhite |
| Next by Thread: | Re: Corruption of in-memory data detected., Jan Derfinak |
| Indexes: | [Date] [Thread] [Top] [All Lists] |