Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*oops\s+when\s+creating\s+an\s+lvm\-snapshot\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*oops\s+when\s+creating\s+an\s+lvm\-snapshot\s*$/: 14 ]

Total 14 documents matching your query.

1. oops when creating an lvm-snapshot (score: 1): Author: erik@xxxxxxxxxxxxxxxxx (Erik Tews); Date: Wed, 14 Aug 2002 19:01:20 +0200; I had a problem with lvm and a current xfs-snapshot. I fetched an xfs-kernel from cvs today, patched it with lvm 1.0.5 and vfs-lock-patch for 2.4.19 and then builded it without quota-support. (becau; /archives/xfs/2002-08/msg00201.html (8,512 bytes)
2. Re: oops when creating an lvm-snapshot (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 14 Aug 2002 12:07:12 -0500; I think this is regression introduced yesterday, we changed some structures around. Try editing fs/xfs/xfs_fsops.c Look for this code around line 580: if (mp->m_rtdev != 0) { xfs_binval(mp->m_rtdev_t; /archives/xfs/2002-08/msg00202.html (8,905 bytes)
3. Re: oops when creating an lvm-snapshot (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Wed, 14 Aug 2002 18:36:31 +0100; There are a few more of those. Having the basically unused m_rtdev beeing an pointer to nothing in some situation was a rather bad design by me. The patch below kills m_rtdev and m_logdev entirely. m; /archives/xfs/2002-08/msg00205.html (16,960 bytes)
4. Re: oops when creating an lvm-snapshot (score: 1): Author: erik@xxxxxxxxxxxxxxxxx (Erik Tews); Date: Thu, 15 Aug 2002 12:49:38 +0200; Ok, I fetched your patch from cvs today. Snapshot seems to work fine, but I cannot mount the snapshot. I did a mount -o nouuid /dev/master/xfssnap /snap and at this moment my kernel oopsed. The backt; /archives/xfs/2002-08/msg00219.html (8,502 bytes)
5. Re: oops when creating an lvm-snapshot (score: 1): Author: erik@xxxxxxxxxxxxxxxxx (Erik Tews); Date: Thu, 15 Aug 2002 13:10:30 +0200; And I found out that the kernel oopses even after a reboot. The message is Unable to handle kernel NULL pointer dereference at virtual address 00000004 If I dd the xfs-snapshot to a file I can run xf; /archives/xfs/2002-08/msg00220.html (9,087 bytes)
6. Re: oops when creating an lvm-snapshot (score: 1): Author: Steve Lord <lord@xxxxxxx>; Date: 15 Aug 2002 09:19:09 -0500; A complete stack backtrace would help here, I do not have LVM setup right now. Details please, details! Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@; /archives/xfs/2002-08/msg00223.html (9,102 bytes)
7. Re: oops when creating an lvm-snapshot (score: 1): Author: erik@xxxxxxxxxxxxxxxxx (Erik Tews); Date: Thu, 15 Aug 2002 16:51:46 +0200; OK, will generate the backtrace tomorrow And yes, it first crashed when I did mount /dev/master/xfs-snapshot /snap; /archives/xfs/2002-08/msg00224.html (9,533 bytes)
8. oops when creating an lvm-snapshot (score: 1): Author:; Date: Wed, 14 Aug 2002 19:01:20 +0200; I had a problem with lvm and a current xfs-snapshot. I fetched an xfs-kernel from cvs today, patched it with lvm 1.0.5 and vfs-lock-patch for 2.4.19 and then builded it without quota-support. (becau; /archives/xfs/2002-08/msg00788.html (8,512 bytes)
9. Re: oops when creating an lvm-snapshot (score: 1): Author:; Date: 14 Aug 2002 12:07:12 -0500; I think this is regression introduced yesterday, we changed some structures around. Try editing fs/xfs/xfs_fsops.c Look for this code around line 580: if (mp->m_rtdev != 0) { xfs_binval(mp->m_rtdev_t; /archives/xfs/2002-08/msg00789.html (8,905 bytes)
10. Re: oops when creating an lvm-snapshot (score: 1): Author:; Date: Wed, 14 Aug 2002 18:36:31 +0100; There are a few more of those. Having the basically unused m_rtdev beeing an pointer to nothing in some situation was a rather bad design by me. The patch below kills m_rtdev and m_logdev entirely. m; /archives/xfs/2002-08/msg00792.html (16,960 bytes)
11. Re: oops when creating an lvm-snapshot (score: 1): Author:; Date: Thu, 15 Aug 2002 12:49:38 +0200; Ok, I fetched your patch from cvs today. Snapshot seems to work fine, but I cannot mount the snapshot. I did a mount -o nouuid /dev/master/xfssnap /snap and at this moment my kernel oopsed. The backt; /archives/xfs/2002-08/msg00806.html (8,502 bytes)
12. Re: oops when creating an lvm-snapshot (score: 1): Author:; Date: Thu, 15 Aug 2002 13:10:30 +0200; And I found out that the kernel oopses even after a reboot. The message is Unable to handle kernel NULL pointer dereference at virtual address 00000004 If I dd the xfs-snapshot to a file I can run xf; /archives/xfs/2002-08/msg00807.html (9,087 bytes)
13. Re: oops when creating an lvm-snapshot (score: 1): Author:; Date: 15 Aug 2002 09:19:09 -0500; A complete stack backtrace would help here, I do not have LVM setup right now. Details please, details! Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@; /archives/xfs/2002-08/msg00810.html (9,102 bytes)
14. Re: oops when creating an lvm-snapshot (score: 1): Author:; Date: Thu, 15 Aug 2002 16:51:46 +0200; OK, will generate the backtrace tomorrow And yes, it first crashed when I did mount /dev/master/xfs-snapshot /snap; /archives/xfs/2002-08/msg00811.html (9,533 bytes)

Current List: 1 - 14
Page: [1]