From mboxrd@z Thu Jan 1 00:00:00 1970 Subject: Re: [linux-lvm] strange behavior with 1.0.5 on Linux 2.4.19? From: Gregory Ade In-Reply-To: <20021105152824.E27825@sistina.com> References: <20021004105057.B8575@sistina.com> <1034107599.28928.105.camel@pslgregory> <20021009133650.E23965@sistina.com> <1035782975.3398.128.camel@gopher> <20021028101739.F16452@sistina.com> <1035866273.9074.74.camel@gopher> <20021029101033.A22193@sistina.com> <1035921224.1276.24.camel@gopher> <20021031134804.A491@sistina.com> <1036104859.21418.104.camel@pslgregory> <20021105152824.E27825@sistina.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-F2RyLmtWM2IDC4z6ufh+" Message-Id: <1036727077.7035.50.camel@pslgregory> Mime-Version: 1.0 Sender: linux-lvm-admin@sistina.com Errors-To: linux-lvm-admin@sistina.com Reply-To: linux-lvm@sistina.com List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: Date: Thu Nov 7 21:45:01 2002 List-Id: To: linux-lvm@sistina.com --=-F2RyLmtWM2IDC4z6ufh+ Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2002-11-05 at 06:28, Heinz J . Mauelshagen wrote: > > > If you have a chance to reconfigure the failing system temporarily, > > > running what you did before should reproduce the same problems (segfa= ult > > > on snapshot creation after fresh reboot) in case there's _no_ bug in = the > > > large/high memory support. > > > My assumption is that it will not. > There's no need to physically remove any DIMMs. Just cook up a kernel > without the patches you mentioned to get that elefant going and > without high memory support. Okay, I disabled high memory support (only change from production kernel), rebooted with this test kernel, and tried to create a snapshot: root@burpr(pts/0):~ 26 # lvcreate --snapshot --extents 512 --name tmp_snap /dev/vg00/tmp lvcreate -- INFO: using default snapshot chunk size of 64 KB for "/dev/vg00/tmp_snap" lvcreate -- doing automatic backup of "vg00" lvcreate -- logical volume "/dev/vg00/tmp_snap" successfully created It worked just fine: root@burpr(pts/1):log 28 # lvdisplay /dev/vg00/tmp --- Logical volume --- LV Name /dev/vg00/tmp VG Name vg00 LV Write Access read/write LV snapshot status source of /dev/vg00/tmp_snap [active] LV Status available LV # 2 # open 1 LV Size 2 GB Current LE 512 Allocated LE 512 Allocation next free Read ahead sectors 120 Block device 58:1 So I removed it: root@burpr(pts/1):log 29 # lvremove /dev/vg00/tmp_snap lvremove -- do you really want to remove "/dev/vg00/tmp_snap"? [y/n]: y lvremove -- doing automatic backup of volume group "vg00" lvremove -- logical volume "/dev/vg00/tmp_snap" successfully removed No kernel oops or BUG in the dmesg. Again, the _ONLY DIFFERENCE_ between this test kernel and the production kernel is the high-memory support option. On the test kernel, it is off, and on the production kernel, it is set to 64GB. Hope this helps. --=20 Gregory K. Ade http://bigbrother.net/~gkade OpenPGP Key ID: EAF4844B keyserver: pgpkeys.mit.edu --=-F2RyLmtWM2IDC4z6ufh+ Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQA9yzMkeQUEYOr0hEsRAkBuAJ430I65EScYyAZxAMGhN5PANDen7wCgnid6 CWrV1zly44fmZy1/Yibw214= =XR24 -----END PGP SIGNATURE----- --=-F2RyLmtWM2IDC4z6ufh+--