Bug#363235: linux-image-2.6-k7: rsync OOPSes with "unable to handle kernel paging request at virtual address 40000000"
dann frazier schrieb:
> On Tue, Dec 18, 2007 at 05:42:25PM +0100, David Ayers wrote:
>
>>Now if you're saying there is a strong indication that this really has
>>to do with memory hardware, then I would ask the hoster how much it
>>would cost me to have them run a memtest if the problem reoccurs... but
>>it's not something I'd like to do if it can be avoided.
>
>
> Bad RAM seemed to be the problem here:
> http://www.ussg.iu.edu/hypermail/linux/kernel/0603.0/0502.html
>
Indeed... but that was a Segmentation Fault which occurred at:
EIP is at find_lock_page+0x2d/0x80
as opposed to a "BUG: unable to handle kernel paging request at virtual
address 40000000" at:
EIP is at find_lock_page+0x20/0x77
I would have guessed that one of the following would have been more related:
http://lists.debian.org/debian-kernel/2007/06/msg00136.html
http://kodos.de/paste/index.php?paste=462
Where the first one also happened during rsync and the last one happened
issue during a copy processes via smbd.
The first issue with rsync seemed to have also damaged the file system
(XFS). I'm using ext3 and looking further down my syslog after the
reset I can see:
Dec 18 11:47:01 demo kernel: EXT3-fs: INFO: recovery required on
readonly filesystem.
Dec 18 11:47:01 demo kernel: EXT3-fs: write access will be enabled
during recovery.
Dec 18 11:47:01 demo kernel: kjournald starting. Commit interval 5 seconds
Dec 18 11:47:01 demo kernel: EXT3-fs: hda2: orphan cleanup on readonly fs
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 6406416
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 6422676
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 6422704
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 3899398
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 3899397
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 3899396
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 3899395
Dec 18 11:47:01 demo kernel: ext3_orphan_cleanup: deleting unreferenced
inode 3899394
Dec 18 11:47:01 demo kernel: EXT3-fs: hda2: 8 orphan inodes deleted
Dec 18 11:47:01 demo kernel: EXT3-fs: recovery complete.
Dec 18 11:47:01 demo kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Since the rsync was creating a backup and I've restarted the backup
hopefully resyncing the files of these 8 inodes I think I have a
realistic chance that I didn't lose any data.
Cheers,
David
PS: I will rsync the entire 5GB tree next month again to see if the
problem is reproducible.
Reply to: